Re: how to specify encodingStyle ?
See the WS-I Basic Profile section 3.1.6:http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html#SOAP_encodingStyle_Attribute 3.1.6 SOAP encodingStyle Attribute The soap:encodingStyle attribute is used to indicate the use of a particular scheme in the encoding of data into XML. However, this introduces complexity, as this function can also be served by the use of XML Namespaces. As a result, the Profile prefers the use of literal, non-encoded XML. R1005 An ENVELOPE MUST NOT contain soap:encodingStyle attributes on any of the elements whose namespace name is "http://schemas.xmlsoap.org/soap/envelope/". R1006 An ENVELOPE MUST NOT contain soap:encodingStyle attributes on any element that is a child of soap:Body. R1007 An ENVELOPE described in an rpc-literal binding MUST NOT contain soap:encodingStyle attribute on any element that is a grandchild of soap:Body. On 5/2/06, Raymond Domingo <[EMAIL PROTECTED]> wrote: Thank you for responding.I did read something about this:http://www-128.ibm.com/developerworks/webservices/library/ws-tip-j2eenet1/ But I couldn't confirm it by reading the specs on ws.apache.org/axis anyreferences to specs related to this would be appreciated.best regards,raymond On Mon, 1 May 2006 20:25:20 -0500, Anne Thomas Manes wrote> "literal" means there is no encoding style. It is inappropriate to specify> one.>> Anne>> On 5/1/06, Raymond Domingo < [EMAIL PROTECTED]> wrote:> >> > Hello,> >> > Is there really no way to enable encodingStyle when using rpc literal ?> >> > In the request I recieve from some (soap) client there is an > > encodingStyle,> > but the response from my axis server has no encodintStyle. I suspect this> > is> > the cause why my clients to throw an exception.> >> > client request: > > > > http://schemas.xmlsoap.org/soap/envelope/ "> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> > xmlns:xsd="http://www.w3.org/2001/XMLSchema ">> > > > > > SOAP-ENV:encodingStyle=" http://xml.apache.org/xml-soap/literalxml">> > > > > >> >> > server response:> > http://schemas.xmlsoap.org/soap/envelope/> > "> > xmlns:xsd="http://www.w3.org/2001/XMLSchema "> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">> > > > > > > >> > Any hints please ?> >> > thnx> > raymond domingo> >
Re: how to specify encodingStyle ?
Thank you for responding. I did read something about this: http://www-128.ibm.com/developerworks/webservices/library/ws-tip-j2eenet1/ But I couldn't confirm it by reading the specs on ws.apache.org/axis any references to specs related to this would be appreciated. best regards, raymond On Mon, 1 May 2006 20:25:20 -0500, Anne Thomas Manes wrote > "literal" means there is no encoding style. It is inappropriate to specify > one. > > Anne > > On 5/1/06, Raymond Domingo <[EMAIL PROTECTED]> wrote: > > > > Hello, > > > > Is there really no way to enable encodingStyle when using rpc literal ? > > > > In the request I recieve from some (soap) client there is an > > encodingStyle, > > but the response from my axis server has no encodintStyle. I suspect this > > is > > the cause why my clients to throw an exception. > > > > client request: > > > > http://schemas.xmlsoap.org/soap/envelope/"; > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > > xmlns:xsd="http://www.w3.org/2001/XMLSchema";> > > > > > SOAP-ENV:encodingStyle="http://xml.apache.org/xml-soap/literalxml";> > > > > > > > > > > server response: > > http://schemas.xmlsoap.org/soap/envelope/ > > " > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > > > > > > > > > > Any hints please ? > > > > thnx > > raymond domingo > >
Re: how to specify encodingStyle ?
"literal" means there is no encoding style. It is inappropriate to specify one.AnneOn 5/1/06, Raymond Domingo < [EMAIL PROTECTED]> wrote:Hello,Is there really no way to enable encodingStyle when using rpc literal ? In the request I recieve from some (soap) client there is an encodingStyle,but the response from my axis server has no encodintStyle. I suspect this isthe cause why my clients to throw an exception. client request:http://schemas.xmlsoap.org/soap/envelope/"xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance"xmlns:xsd="http://www.w3.org/2001/XMLSchema"> SOAP-ENV:encodingStyle="http://xml.apache.org/xml-soap/literalxml"> server response:http://schemas.xmlsoap.org/soap/envelope/"xmlns:xsd=" http://www.w3.org/2001/XMLSchema"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Any hints please ?thnxraymond domingo
how to specify encodingStyle ?
Hello, Is there really no way to enable encodingStyle when using rpc literal ? In the request I recieve from some (soap) client there is an encodingStyle, but the response from my axis server has no encodintStyle. I suspect this is the cause why my clients to throw an exception. client request: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> http://xml.apache.org/xml-soap/literalxml";> server response: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> Any hints please ? thnx raymond domingo
how to specify encodingStyle ?
Hello, Is there really no way to enable encodingStyle when using rpc literal ? In the request I recieve from some (soap) client there is an encodingStyle, but the response from my axis server has no encodintStyle. I suspect this is the cause why my clients to throw an exception. client request: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> http://xml.apache.org/xml-soap/literalxml";> server response: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> Any hints please ? thnx raymond domingo
