Hi Gopinath,
> Now, the question is, is it mandatory to have every element
> bound to
> namespace in SOAP?
Mandatory according to who/what? If someone wants to conform to a
specification, they follow what is detailed there.
> IMO, it should be,
As I said earlier, you should probably take this up on the list whose
purpose is defining the XML Protocol.
> since the applications can
> understand only namespaces specific to them and not elements in unknown
> namespaces.
?
Thanks,
-Matt
> -----Original Message-----
> From: Gopinath M.R. [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 31, 2001 12:08 PM
> To: Matthew J. Duftler
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Why do we need encoding-style?
>
>
> Hi matt,
> Thanks for your kind reply. I haven't followed any progress in XP
> specification. I will study something available in w3c before posting
> it there :) Since XP is still under revision and we are not using in
> any application, there is no issue as of now.
> SOAP is a recommendatation, the encoding style is used in current
> applications and only one encoding style defined in SOAP spec is used.
> I guess the question remains valid and is not clear for SOAP.
>
> I have similar doubt in SOAP specification about the xml namespace
> specified in examples(I think it is BUG in spec example). I had mailed
> it to soap-user mailing list but no one replied :(. Since you were
> involved in development of soap toolkit, if you can clear my doubt, I
> will be thankful.
>
> Here I am sending a copy of the mail body [You can search the mail in
> list on 5th May 2001, subject is "Namespaces missing for few elements of
> SOAP spec example !!!!" [You can test it by parsing the SOAP request
> document using SAX parser and printing the namespace of each element].
>
> The elements in the received SOAP response[2] does not have
> namespace
> binding for 'return'. If you use SAX Parser and parse below document,
> you will not get namespace for element 'return'. Ideally this should
> have been in some standard namespace URI of apache soap toolkit (an
> encoding URI), since this is specific to RPC invoke in apache soap.
>
> Most importantly, the same BUG is there in SOAP spec example
> [1], few
> elements are not bound to any namespace (Element 'Price' is not bound to
> any namespace). It should have been 'm:Price'.
>
> [1] SOAP request (as specified in SOAP specification example 2)
> ------------------------------------------------------------------
>
> <SOAP-ENV:Envelope
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
> SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
> <SOAP-ENV:Body>
> <m:GetLastTradePriceResponse xmlns:m="Some-URI">
> <Price>34.5</Price>
> </m:GetLastTradePriceResponse>
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
>
>
> [2] : SOAP response sent by server using apache SOAP toolkit
> ------------------------------------------------------------
> <SOAP-ENV:Envelope
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance";
> xmlns:xsd="http://www.w3.org/1999/XMLSchema";>
> <SOAP-ENV:Body>
> <ns1:getQuoteResponse xmlns:ns1="urn:StockQuoteService"
> SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";>
> <return xsi:type="xsd:float">138.25</return>
> </ns1:getQuoteResponse>
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
>
> Now, the question is, is it mandatory to have every element
> bound to
> namespace in SOAP? IMO, it should be, since the applications can
> understand only namespaces specific to them and not elements in unknown
> namespaces. For example, if I send SOAP request containing UDDI
> namespace elements and with few Elements (defined in UDDI schema) not
> bound to UDDI namespace, UDDI registry can't understand them and may
> throw error to user.
>
>
> Regards,
> Gopinath.M.R.
> Sr.Product Engineer,
> Aztec software, INDIA
> URL : http://www.aztec.soft.net
>
>
>
>
> "Matthew J. Duftler" wrote:
> >
> > Hi Gopinath,
> >
> > This question is probably best suited for something like the
> xml-dist-app
> > mailing list available from the XML Protocol Working Group's page at:
> > http://www.w3.org/2000/xp/Group/
> >
> > Thanks,
> > -Matt
> >
> > > -----Original Message-----
> > > From: Gopinath M.R. [mailto:[EMAIL PROTECTED]]
> > > Sent: Thursday, May 31, 2001 3:02 AM
> > > To: [EMAIL PROTECTED]
> > > Cc: 'Gaurav '; Nicolas Fonrose
> > > Subject: Re: Why do we need encoding-style?
> > >
> > >
> > > Hi,
> > > Even I had the doubt regarding why do we need encoding
> style? The
> > > encoding style is used on the server side to serialize and deserialize
> > > XML to corresponding programming language (java,c++, etc) instances.
> > > But the main question is why should client be aware of this?
> If server
> > > is using an encoding style "my_cpp_encoding" and java client knows how
> > > to serialize and deserialize its data to XML (probably using encoding
> > > style "my_java_encoding"), then specifying "my_cpp_encoding"
> in the SOAP
> > > request looks stupid from client's point of view, isn't it? IMHO
> > > encoding style is *to do with implementation on server side*
> (and should
> > > not be part of request/response data) and client should not
> be asked to
> > > send that info.
> > > Let's say I have a java application which provides SOAP
> > > interface and
> > > has mapping of xml elements to java classes (either
> implicitly like XML
> > > Java databinding or stored somewhere on server side in some
> .properties
> > > file), then a VB client need not send any encoding stuff right?
> > >
> > > Any comments???
> > >
> > > regards,
> > > Gopinath .M.R.
> > > Sr.Product Engineer,
> > > Aztec software
> > >
> > > Nicolas Fonrose wrote:
> > > >
> > > >
> > > > XML is just a meta-language, not a language. You can't
> > > > serializable anything in "XML". You have to choose what
> > > > is called an "XML application" or "XML language" or "XML encoding"
> > > > to serialiaze your data.
> > > >
> > > > There are numerous languages you can choose from to do this and
> > > > this is what the "encoding-style" is for. It tells the receiver
> > > > of the SOAP message what encoding was used.
> > > >
> > > > SOAP comes with a default SOAP-encoding but you can use any other
> > > > encoding (a custom one for example).
> > > >
> > > > Nicolas
> > > >
> > > > -----Message d'origine-----
> > > > De: Gaurav
> > > > A: [EMAIL PROTECTED]
> > > > Date: 30/05/01 14:52
> > > > Objet: Why do we need encoding-style?
> > > >
> > > > Hi all,
> > > >
> > > > What exactly is meant by "encoding-style" attribute in SOAP
> message. I
> > > > read that "encoding-style" value informs the server of the encoding
> > > > style used to encode -- i.e., serialize -- the method. But
> dont we use
> > > > XML to serialize the method in SOAP?? So why would we use an
> > > > encoding-style attribute? Does anybody have any example which shows
> > > > utility of this attribute in a practical scenario?
> > > >
> > > > Thnaks and regards,
> > > > Gaurav
> > > >
> > > >
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, email: [EMAIL PROTECTED]
> > >
> > > _________________________________________________________
> > > Do You Yahoo!?
> > > Get your free @yahoo.com address at http://mail.yahoo.com
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, email: [EMAIL PROTECTED]
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
