Yes. It's okay for empty namespace definitions to go across the wire. In fact, it some cases it might be required.
In your SOAP request, the <query> element defines a default namespace (xmlns="blah" as opposed to xmlns:foo="blah"), which then applies to all subelements of the <query> element, unless it is overridden by another default namespace definition. If the <description> and <ItemId> elements are local elements to <query>, then they should not be namespace qualified, and in that case, you should specify an empty default namspace definition in each of these subelements to override the active default namespace.
Now, if the <description> and <ItemId> are global elements, then this message would be in error.
So whether or not this message is correct depends on the schema definition for the message.
Anne
At 02:20 AM 9/1/2003 -0700, you wrote:
Hi all,
I'm trying to write a doc\literal web service and my soap message appears as below.........
<query xmlns="urn:HistorySriLanka"> <description xmlns="">Wood carving of an Elephant</description> <ItemId xmlns="">ER234</ItemId> </query>
Has anybody else has come across a situation like this? Is it ok for empty xmlns="" tags to go in the wire? Any help is greatly appreciated.
Thank you, Dimuthu
Do you Yahoo!?
<http://us.rd.yahoo.com/evt=10469/*http://sitebuilder.yahoo.com>Yahoo! SiteBuilder - Free, easy-to-use web site design software
