Return-Path: 
 <axis-user-return-18129-apmail-ws-axis-user-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-user-archive@www.apache.org
Received: (qmail 35551 invoked from network); 2 Sep 2003 14:03:32 -0000
Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 2 Sep 2003 14:03:32 -0000
Received: (qmail 67736 invoked by uid 500); 2 Sep 2003 14:02:40 -0000
Delivered-To: apmail-ws-axis-user-archive@ws.apache.org
Received: (qmail 67732 invoked by uid 500); 2 Sep 2003 14:02:40 -0000
Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
list-help: <mailto:axis-user-help@ws.apache.org>
list-unsubscribe: <mailto:axis-user-unsubscribe@ws.apache.org>
list-post: <mailto:axis-user@xml.apache.org>
Delivered-To: mailing list axis-user@ws.apache.org
Received: (qmail 67699 invoked from network); 2 Sep 2003 14:02:39 -0000
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: xmlns=" " in the doc\literal SOAP message
Date: Tue, 2 Sep 2003 09:02:34 -0500
Message-ID: <3F2E62790250AF4485864348F7E9F6B0D77009@stingray.tnow.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: xmlns=" " in the doc\literal SOAP message
Thread-Index: AcNxWkmsrxPQ7EWESeyNoBoNkdyC0wAABdMA
From: "Cory Wilkerson" <cwilkerson@travelnow.com>
To: <axis-user@ws.apache.org>
X-OriginalArrivalTime: 02 Sep 2003 14:02:34.0890 (UTC)
 FILETIME=[DC0646A0:01C3715A]
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Anne,

When you say "local" elements -- do you mean local to the parent element =
as defined in the schema?  In the following example, would bar and baz =
be considered local elements? =20

<schema targetName=3D"http://www.foo.com"/>
	<complexType name=3D"foo>
		<sequence>
			<element name=3D"bar" type=3D"xsd:string"/>
			<element name=3D"baz" type=3D"xsd:string"/>
		</sequence>
	<complexType>
</schema>

I would think when this was serialized to the wire you'd see something =
like:

<foo xmlns=3D"http://www.foo.com">
	<bar>cory</bar>
	<baz>anne</baz>
</foo>

After all, don't bar and baz technically belong to the foo.com =
namespace? =20

Thanks for any input,
Cory WIlkerson


-----Original Message-----
From: Anne Thomas Manes [mailto:anne@manes.net]
Sent: Tuesday, September 02, 2003 8:40 AM
To: axis-user@ws.apache.org
Subject: Re: xmlns=3D" " in the doc\literal SOAP message


Dimuthu,

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=20
(xmlns=3D"blah" as opposed to xmlns:foo=3D"blah"), which then applies to =
all=20
subelements of the <query> element, unless it is overridden by another=20
default namespace definition. If the <description> and <ItemId> elements =

are local elements to <query>, then they should not be namespace =
qualified,=20
and in that case, you should specify an empty default namspace =
definition=20
in each of these subelements to override the active default namespace.

Now, if the <description> and <ItemId> are global elements, then this=20
message would be in error.

So whether or not this message is correct depends on the schema =
definition=20
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=20
>as below.........
>
><query xmlns=3D"urn:HistorySriLanka">
>    <description xmlns=3D"">Wood carving of an Elephant</description>
>    <ItemId xmlns=3D"">ER234</ItemId>
></query>
>
>Has anybody else has come across a situation like this? Is it ok for =
empty=20
>xmlns=3D"" tags to go in the wire? Any help is greatly appreciated.
>
>Thank you,
>Dimuthu
>
>
>Do you Yahoo!?
><http://us.rd.yahoo.com/evt=3D10469/*http://sitebuilder.yahoo.com>Yahoo!=
=20
>SiteBuilder - Free, easy-to-use web site design software