SOAP WebService and PopupRenderer conflicts in Flex viewer 2.x

Question

Hi, I have run into this issue for a while and never got it resolved even after I called ESRI support. In Flex viewer 2.x, if you have a SOAP web service declaration like this: , the popup won't work, it returns error message below: ArgumentError: Error #2004: One of the parameters is invalid. at ObjectOutput/writeObject() at mx.collections::ArrayList/writeExternal() at mx.collections::ArrayCollection/writeExternal() at flash.utils::ByteArray/writeObject() at mx.utils::ObjectUtil$/copy() at com.esri.ags.webmap::PopUpRenderer/commitProperties() at mx.core::UIComponent/validateProperties() at mx.managers::LayoutManager/validateProperties() at mx.managers::LayoutManager/doPhasedInstantiation() at mx.managers::LayoutManager/doPhasedInstantiationCallback() For example, put the declaration code in LocateWidget, if you open locate widget first, then use another widget having popup such as SearchWidget, whenever you click the search result record, it shows the error. However, if you first use a SearchWidget before the LocateWidget (PopupRenderer instantiated first), then everything works fine. ESRI logged this as a defect. I am wondering if anyone here ran into the same issue or if you have any thoughts on this. Thank you for the help. Jinhu

FaizanTayyab · Answer

I had everything working fine but within the last one hour i am starting to have the same error message with webservices as well. In a normal Flex application the webservice works fine and i am able to access al the data but it is in the flex viewer that clicking on a returned feature give the error message you mentioned.

Fixed it!!  I had established a session with the webservice in the viewercontainer. By removing the session establishing code from the viewercontainer to the widget itself solved the problem.  Still not sure why the problem occurred in first place.

FaizanTayyab · Answer

I had everything working fine but within the last one hour i am starting to have the same error message with webservices as well. In a normal Flex application the webservice works fine and i am able to access al the data but it is in the flex viewer that clicking on a returned feature give the error message you mentioned.