Unless you use a namespace manager, it is up to the serializer to resolve
whether it uses prefixes or inline default namespace markup. The two are
equivalent, and to be XML compliant, a parser must be albe to treat both as
if they were the same.
Some of the pretty basic WS tools and hand-coded XML crackers attached to
port listeners have problems because they try to treat XML as if it were a
string. I wouldn't worry about the on-the wire format.
--------------------
>From: "Anirudh" <anirudh.chandrakant@gmail.com>
>Newsgroups: microsoft.public.dotnet.framework.aspnet.webservices
[quoted text clipped - 9 lines]
>Content-Type: text/plain; charset="iso-8859-1"
>X-Trace: posting.google.com 1107878903 31115 127.0.0.1 (8 Feb 2005
16:08:23 GMT)
>X-Complaints-To: groups-abuse@google.com
>NNTP-Posting-Date: Tue, 8 Feb 2005 16:08:23 +0000 (UTC)
[quoted text clipped - 4 lines]
> posting-account=eRjlSA0AAADte3ZUkFlDNKEd6cdZlzrd
>Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED02.phx.gbl!tornado.fastwebnet.it!tiscali!new
sfeed1.ip.tiscali.net!proxad.net!216.239.36.134.MISMATCH!postnews.google.com
!o13g2000cwo.googlegroups.com!not-for-mail
>Xref: cpmsftngxa10.phx.gbl
microsoft.public.dotnet.framework.aspnet.webservices:28017
>X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webservices
>
[quoted text clipped - 3 lines]
>for 'xyz'). Thanks again.
>-Anirudh