Looking further at the spec w3.org/TR/SOAP/#_Ref4777957007 - The rules for
serialization:
4. A Compound Value is encoded as a sequence of elements, each
accessor represented by an embedded element whose name corresponds to the
name of the accessor. Accessors whose names are local to their containing
types have unqualified element names; all others have qualified names (see
also section 5.4).
According to this rule Axis SHOULD not (or maybe MUST not??) prefix "name"
nor "version"
Is this a bug?
Sylvain.
-----Original Message-----
From: St-Germain, Sylvain [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 29, 2002 11:06 AM
To: Axis Dev (E-mail)
Subject: namespace prefixing question...
Hi all,
I am a bit confused, until recently (early April, end of March) Axis was
serializing types without "namespace-prefixing" the child nodes of a
type-qualified node.
For example the following chunk was valid:
<objects xsi:type="SOAP-ENC:Array" SOAP-ENC:arrayType="ns1:baseClass[1]">
<item xsi:type="ns1:folder">
<name xsi:nil="true"/>
<version xsi:nil="true"/>
</item>
</objects>
The "name" and "version" elements were not namespace qualified, this has now
been changed in Axis, the same chunk is not carried over as:
<objects xsi:type="SOAP-ENC:Array" SOAP-ENC:arrayType="ns1:baseClass[1]">
<item xsi:type="ns1:folder">
<ns1:name xsi:nil="true"/>
<ns1:version xsi:nil="true"/>
</item>
</objects>
...where the child of item are now prefixed. Is the old one still valid in
SOAP term? Should everything be namespace qualified? Anybody can tell me
where the rule is defined? Any information much appreciated.
Thanks.
--
Sylvain
This message may contain privileged and/or confidential information. If you
have received this e-mail in error or are not the intended recipient, you
may not use, copy, disseminate or distribute it; do not open any
attachments, delete it immediately from your system and notify the sender
promptly by e-mail that you have done so. Thank you.
This message may contain privileged and/or confidential information. If you
have received this e-mail in error or are not the intended recipient, you
may not use, copy, disseminate or distribute it; do not open any
attachments, delete it immediately from your system and notify the sender
promptly by e-mail that you have done so. Thank you.
