On Sunday 14 October 2007, Benson Margulies wrote: > Oh, how embarassing. Somehow, we were able to talk to Aegis just fine > with Javascript written completely ignorantly of elementForm.
Right. JAXB is very strict about the elementForm. Aegis isn't quite so strict. Actually, the other difference you may run into is if you use Aegis+Simple frontend, the default IS qualified. If you use the JAX-WS frontend, the default is unqualified. Dan > > > -----Original Message----- > > From: Benson Margulies > > Sent: Sunday, October 14, 2007 8:42 AM > > To: '[email protected]' > > Subject: RE: Too soap-y for my own good > > > > This message works. > > > > <soapenv:Envelope > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> > > <soapenv:Body> > > <btft:echo > > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > > xmlns:btft="uri:com.basistech.ws.fortest"> > > <input>Bloop</input> > > <throwPlease>false</throwPlease> > > </btft:echo> > > </soapenv:Body> > > </soapenv:Envelope> > > > > This one fails. Could it be that having more namespace qualifiers is > > bad? > > > <SOAP-ENV:Envelope > > xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"; > > xmlns:tns="uri:com.basistech.ws.fortest" > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > > xmlns:btft="uri:com.basistech.ws.fortest" > > xmlns:xs="http://www.w3.org/2001/XMLSchema";> > > <SOAP-ENV:Body> > > <btft:echo><btft:input>Echo This</btft:input> > > <btft:throwPlease>false</btft:throwPlease> > > </btft:echo></SOAP-ENV:Body></SOAP-ENV:Envelope> -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
