What data types are your returning in your SOAP Response from the .NET web service? There definitely are complex object types that java/.net support that Flex/AS do not. Karl Cynergy
________________________________ From: flexcoders@yahoogroups.com on behalf of ben.clinkinbeard Sent: Tue 2/27/2007 8:29 AM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: WS call sucessful with resultFormat="e4x", fails otherwise Anyone? --- In flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> , "ben.clinkinbeard" <[EMAIL PROTECTED]> wrote: > > Hello, we are seeing some weird behavior when calling an RPC encoded > .NET web service. Unless we set resultFormat to e4x, we receive the > following error: > > fault: [FaultEvent fault=[RPC Fault faultString="Error #1009: Cannot > access a property or method of a null object reference." > faultCode="DecodingError" faultDetail="null"] > messageId="BCCBBAB0-1457-00EA-5329-FE83F9158923" type="fault" > bubbles=false cancelable=true eventPhase=2] > > ServiceCapture shows that the call does return successfully, and the > response contains data. A faultCode of "DecodingError" leads me to > believe Flex is having trouble deserializing the response into > objects, but I am not sure why that would be. Are there certain SOAP > structures Flex is known to have problems with? > > Thanks, > Ben >
