We also had this problem. Our initial work-around was to use a single complex object to hold all parameters for an operation.
Then once Beta1 came out, we've gone to using RemoteObjects and this has worked for us. best of luck, Thunder --- In flexcoders@yahoogroups.com, "Tobias Patton" <[EMAIL PROTECTED]> wrote: > > Hi Tim; > > Thanks for your reply. I'm not sure that we're experiencing exactly the > same problem. As far as I know, our web server (ASP .NET) does not rely > on the order of parameters in the SOAP envelope. > > The problem for us is that the values passed to the server are being > placed in the wrong SOAP parameters. > > For example, here is the incorrect SOAP envelope that results in a web > service fault: > > <SOAP-ENV:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema";><SOAP-ENV:Body><CreateView > xmlns="http://www.kodak.com/WPE/Galiano/";><ns0:SessionId > xmlns:ns0="http://www.kodak.com/WPE/Galiano/";></ns0:SessionId><ns0:Query > xmlns:ns0="http://www.kodak.com/WPE/Galiano/";>AB4AB4A8-28C8-A580-B12B-FF > FFFFFF48A3</ns0:Query></CreateView></SOAP-ENV:Body></SOAP-ENV:Envelope> > > And here is the correct envelope (no code changes -- just a different > run of the application ): > > <SOAP-ENV:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";><SOAP-ENV:Bod > y><CreateView xmlns="http://www.kodak.com/WPE/Galiano/";><ns0:Query > xmlns:ns0="http://www.kodak.com/WPE/Galiano/";></ns0:Query><ns0:SessionId > xmlns:ns0="http://www.kodak.com/WPE/Galiano/";>8C428366-587C-D759-DD7B-FF > FFFFFF6CF8</ns0:SessionId></CreateView></SOAP-ENV:Body></SOAP-ENV:Envelo > pe> > > Look at the <Query> and <SessionId> parameters. In the first example, > <SessionID> is blank, and <Query> contains a UID. In the second example, > <SessionID> contains a UID, and <Query> is blank. > > While it's true that the order of the parameters has been swapped, it's > the fact that the values for the parameters were not also swapped that > is causing the trouble. > > I suppose I could change the web-service prototype to take a single, > complex object, but I'd rather not have to alter the server > implementation to fix what seems to be a bug in the client framework. > > Is there a different way of defining the parameters and values for a > SOAP web service invocation? Ideally, I would create a dictionary with > SessionID and Query attributes, set the value of those attributes and > attach it to the web service call. I don't see anything in the > WebServices APIs that would let me do that though. > > Tobias. > > > -----Original Message----- > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On > Behalf Of Tim Sawyer > Sent: Monday, March 27, 2006 9:32 AM > To: flexcoders@yahoogroups.com > Subject: Re: [flexcoders] Flex 2: WebServervice call sometimes swaps > parameters > > Yep, we have that too. We were told that doc/lit support was a bit > flaky in > Flex 2. We solved it by changing our webservice (we use jibx-soap to a > Java > back end) to be unordered. > > Search for the mail below for full details of the problem. > > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On > Behalf Of p_b_kennedy > Sent: Thursday, February 02, 2006 5:33 AM > To: flexcoders@yahoogroups.com > Subject: [flexcoders] Flex 2 - Problem with order of webservice > parameters > > Tim. > > On Monday 27 Mar 2006 18:15, Tobias Patton wrote: > > Hello list; > > > > > > > > My application invokes a .NET web service that takes two string > > parameters (SessionID and Query). On occasion, I get an error. When I > > look at the RPC debug information, the SOAP envelope shows that the > > values for two parameters have been swapped (ie. SessionID gets the > > value intended for Query and vice-versa). > > > > > > > > The truly weird thing is that this only happens sometimes. If I get > the > > error, the very next run of the application may or may not show it, > with > > no code changes. This sounds like the kind of bug that would result > from > > a race-condition, but I don't see how that could be the case in > mapping > > function parameters to SOAP parameters. > > > > > > > > I think I remember seeing this problem posted to the list before, but > > can't find it in the archives. > > > > > > > > Can anyone help? > > > > Thanks. > > Tobias. > > > > > > > > Creo Inc., a subsidiary of Kodak > > > > Tobias Patton | Software Developer | Tel: +1.604.451.2700 ext: 5148 | > > mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> | > > http://www.creo.com <http://www.creo.com> > > > -- > Flexcoders Mailing List > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Search Archives: > http://www.mail-archive.com/flexcoders%40yahoogroups.com > Yahoo! Groups Links > -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
