It's called JavaScript Soap Client and is located at:
http://www.codeplex.com/JavaScriptSoapClient/Release/ProjectReleases.asp x?ReleaseId=1775 -----Original Message----- From: Daniel Kulp [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 19, 2007 9:43 AM To: [email protected] Cc: Vespa, Anthony J Subject: Re: Issue with Java first functions and Arguement Sequence If the other frontend is doing that, it is doing it wrong and is a bug in that frontend. Is there any way that frontend can be fixed to generate proper messages that match the wsdl/schema? What toolkit is it? I kind of hate putting major hacks in place to workaround very serious flaws in other toolkits, but if there isn't any other way.... Dan On Wednesday 19 December 2007, Vespa, Anthony J wrote: > I'm having an issue and can't quite find an answer to my query in the > mailing list archives. I am doing Java first development and using > AEGIS Binding am having an issue. I had written to the list before > about it but am looking for further suggestions. > > The front end client is forming the soap message using a hashmap and > my concern is that there is the chance that parameters will come in a > different sequence than that specified in my WSDL. IF this occurs, > at best I get wrong results, at worst I get a SoapFault and tons of > exceptions. I am flumoxed by this and would like to find a workaround > as I can't always depend on the various front ends to be constructing > things in the same order. > > Is there any way to force 'by name' parameter resolution? > > I have several functions; some taking primitives, some taking objects. > This is a sample of my WSDL. > > The segment of my WSDL looks like > > <xsd:element name="getMessages" type="tns:getMessages" /> > <xsd:complexType name="getMessages"> > <xsd:sequence> > <xsd:element minOccurs="0" name="messageBoardId" type="xsd:long" /> > <xsd:element minOccurs="0" name="qualifier" type="xsd:string" /> > <xsd:element minOccurs="0" name="omitMessageText" type="xsd:boolean" > /> </xsd:sequence> > </xsd:complexType> > > And SEI is... > > @WebResult(name = "getMessagesResult") > @WebMethod > public wsResponse<wsMessage> getMessages { > @WebParam(name = "messageBoardId")Long messageBoardId, > @WebParam(name = "qualifier")String qualifier, > @WebParam(name = "omitMessageText")Boolean > omitMessageText); > > Thanks very much! > > Tony -- J. Daniel Kulp Principal Engineer, IONA [EMAIL PROTECTED] http://www.dankulp.com/blog
