Re: Avoid multiRef in SOAP response (make it simple)
Perfect!I used the flag "-u LITERAL" when generating the WSDL and it works.On 4/11/06, Anne Thomas Manes < [EMAIL PROTECTED]> wrote:Don't use SOAP encoding. Use document/literal with the "wrapped" convention instead. (You'll get better performance, too.)AnneOn 4/10/06, Daniel Destro <[EMAIL PROTECTED]> wrote: Hi all, I was wondering why Axis 1.3 generates a very complicated and verbose SOAP response, including all this multiRef tags. For my service, that has a method that returns a data structre (object), it generates the following SOAP response: http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd=" http://www.w3.org/2001/XMLSchema " xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance "> http://schemas.xmlsoap.org/soap/encoding/ " xmlns:ns1="urn:MyService"> soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/ " xsi:type="ns2:MyMethodResult" xmlns:soapenc=" http://schemas.xmlsoap.org/soap/encoding/ " xmlns:ns2="urn:MyService"> 0 POSTAL Insteadm I would like something similar to: http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd=" http://www.w3.org/2001/XMLSchema " xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance "> http://schemas.xmlsoap.org/soap/encoding/ " xmlns:ns1="urn:MyService"> 0 POSTAL Thas is WAY MUCH MORE SIMPLE. Is there any way to make it more simple? More straight forward and avoid this more complex SOAP? Thanks Daniel
Re: Avoid multiRef in SOAP response (make it simple)
Don't use SOAP encoding. Use document/literal with the "wrapped" convention instead.(You'll get better performance, too.)AnneOn 4/10/06, Daniel Destro <[EMAIL PROTECTED]> wrote: Hi all, I was wondering why Axis 1.3 generates a very complicated and verbose SOAP response, including all this multiRef tags. For my service, that has a method that returns a data structre (object), it generates the following SOAP response: http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd=" http://www.w3.org/2001/XMLSchema " xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance "> http://schemas.xmlsoap.org/soap/encoding/ " xmlns:ns1="urn:MyService"> soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/ " xsi:type="ns2:MyMethodResult" xmlns:soapenc=" http://schemas.xmlsoap.org/soap/encoding/ " xmlns:ns2="urn:MyService"> 0 POSTAL Insteadm I would like something similar to: http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd=" http://www.w3.org/2001/XMLSchema " xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance "> http://schemas.xmlsoap.org/soap/encoding/ " xmlns:ns1="urn:MyService"> 0 POSTAL Thas is WAY MUCH MORE SIMPLE. Is there any way to make it more simple? More straight forward and avoid this more complex SOAP? Thanks Daniel
Avoid multiRef in SOAP response (make it simple)
Hi all, I was wondering why Axis 1.3 generates a very complicated and verbose SOAP response, including all this multiRef tags. For my service, that has a method that returns a data structre (object), it generates the following SOAP response: http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema " xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance "> http://schemas.xmlsoap.org/soap/encoding/ " xmlns:ns1="urn:MyService"> soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns2:MyMethodResult" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/ " xmlns:ns2="urn:MyService"> 0 POSTAL Insteadm I would like something similar to: http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema " xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance "> http://schemas.xmlsoap.org/soap/encoding/ " xmlns:ns1="urn:MyService"> 0 POSTAL Thas is WAY MUCH MORE SIMPLE. Is there any way to make it more simple? More straight forward and avoid this more complex SOAP? Thanks Daniel
