The SOAP spec says a little bit about this, e.g. see the 1.2 working draft at http://www.w3.org/TR/2001/WD-soap12-part0-20011217/#L3374. WSDL (see 1.1 at http://www.w3.org/TR/wsdl#_soap-b) also provides a means to specify encoding. Apache SOAP supports "standard" SOAP encoding, denoted by the http://schemas.xmlsoap.org/soap/encoding/ URI, as well as XMI encoding http://www.ibm.com/namespaces/xmi and literal XML http://xml.apache.org/xml-soap/literalxml. The address book example's GetAllListings method returns the listings using literal XML. Basically, using literal XML the sender of a message sends some XML fragment which the receiver must interpret. It's very useful if you already have data in XML format. With Apache SOAP, just read the XML into a DOM and specify an element of the DOM as a parameter.
I do not know whether the XMI encoding will find widespread use, but since .NET does both SOAP (aka rpc/encoded) and literal XML (document/literal), I think both of those will be quite popular. Scott Nichol ----- Original Message ----- From: "soap vamsi" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, May 14, 2002 9:05 AM Subject: soap encoding? > Can any one tell the significance of the encodingStyle attribute > where we give the > valuehttp://schemas.xmlsoap.org/soap/encoding/. > From all that i know this url must contain an xml doc that > contains the rules to marshall the soap request the soap xml. > Though I stated the above i am still not able to concieve what > that means when it is brought to the level of reality. > > For Ex. > In the wsdl file i define a type as > <xsd:complexType name="phone"> > <xsd:all> > <xsd:element name="areaCode" type="xsd:int"/> > <xsd:element name="exchange" type="xsd:string"/> > <xsd:element name="number" type="xsd:string"/> > </xsd:all> > </xsd:complexType> > > assuming that phone is the only part of my input message , in the > binding i specify > <input> > <soap:body use="encoded" > namespace="urn:AddressFetcher" > > encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/> > </input> > > for the message. > What is the significance of this encoding when i have already > expressed my input type as XML. > > I have made an earnest effort the articulate my issue.Pl lemme > know if it is still not clear > thanx in advance > vamsi > _________________________________________________________ > Click below to visit monsterindia.com and review jobs in India or > Abroad > http://monsterindia.rediff.com/jobs > >
