This content has been marked as final. Show 2 replies
Fun, i hate selling technology to directors, isnt that there job to learn whats new?!
But, adurkin here is what you need to do. It doesnt matter what you pass to and from the service, its a matter of making sure your objects match between flex and .net. Also make sure the service you are using in flex is set to handle OBJECTS by setting the result format to object for each of the functions you have hanging off your service.
<mx:WebService id="WS" wsdl=" http://localhost:49753/Test_Application/App_Common/Services/ProductSearch.asmx?WSDL"
<mx:operation name="MyFunctionName" resultFormat="object">
Let me know if this helps, if it doesnt ill send over an example leave me your email.
Thanks for your input on this Ryan. I've sort of gotten a work around. What I was planning was a business object containing an ArrayCollection of other objects (this is what I was trying to send initially). Anyway, if I send the main aggregate object the call to the service works fine. I may have to revisit this topic if (hopefully!) I get the go ahead to use flex but for now my prototype is doing the right thing.
Thanks again for your help - the resultFormat advice is definitely relevant in this area.