axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Daniels" <gdani...@macromedia.com>
Subject Re: Axis breaks XML infoset
Date Thu, 01 Nov 2001 19:07:24 GMT

Hi, Ryo!

I'm not sure, but isn't defining a document with:

createElementNS("urn:Test", "foo")

and then not putting in any namespace prefix mapping information kind of bad
form?  If you take the resultant element and add an attribute to it thusly:

element.setAttributeNS(Constants.NS_URI_XMLNS, "xmlns:prefix", "urn:Test");

You should then see

<prefix:foo xmlns:prefix="urn:Test"/>

on both the request and the response.

--Glen

----- Original Message -----
From: "Ryo Neyama" <neyama@trl.ibm.co.jp>
To: <axis-dev@xml.apache.org>
Sent: Wednesday, October 31, 2001 9:31 PM
Subject: Re: Axis breaks XML infoset


> Hello Glen,
>
> I tried a recent nightly build.
> The Client.java received the following response:
>     <ns3:foo xmlns:ns3="urn:Test"/>
> Thank you very much for the information.
>
> However, the problem has not been solved completely yet because <foo> is
> renamed to <ns3:foo>. A namespace prefix is a part of XML infoset.
>     http://www.w3.org/TR/xml-infoset/#infoitem.element
>
> Do you have any suggestion on this?
>
> Best regards,
>     Ryo Neyama @ IBM Research, Tokyo Research Laboratory
>     Internet Technology
>     neyama@trl.ibm.co.jp
>
> ----- Original Message -----
> From: "Glen Daniels" <gdaniels@macromedia.com>
> To: <axis-dev@xml.apache.org>
> Sent: Wednesday, October 31, 2001 9:42 PM
> Subject: Re: Axis breaks XML infoset
>
>
> > Hi Ryo!
> >
> > Are you using a recent nightly build?  I believe these issues may have
> been
> > resolved.
> >
> > --Glen
> >
> > ----- Original Message -----
> > From: "Ryo Neyama" <neyama@trl.ibm.co.jp>
> > To: <axis-dev@xml.apache.org>
> > Sent: Wednesday, October 31, 2001 12:15 AM
> > Subject: Axis breaks XML infoset
> >
> >
> > > Hello,
> > >
> > > I am struggling with a problem that Axis does not generate well-formed
> XML
> > > documents.
> > >
> > > The program attached illustrates the problem. -- Here, Client.java
> creates
> > a
> > > DOM element with createElementNS("urn:Test", "foo") and sends it as a
> > > SOAPBodyElement to Server.java.  And then, the Server.java sends the
> > > Document object to the Client.java as it is.
> > >
> > > Theoretically, XML infoset (http://www.w3.org/TR/xml-infoset/) of the
> > target
> > > XML document must be kept along the message path. However, it is not
in
> > > Axis.
> > >
> > > In case of Axis 1.0 alpha-2, the Client.java receives the following
XML
> > > document from the Server.java:
> > >     <ns3:ns3:foo xmlns:ns3="urn:Test" xmlns:ns3="urn:Test"/>
> > >
> > > First of all, this is not an well-formed XML document.
> > >     1. The attributes "xmlns:ns3" occurs twice.
> > >     2. "ns3:ns3:" is not allowed by XML Namespaces.
> > > Even if we resolve these problems, renaming the namespace prefixes is
> > still
> > > not allowed by XML infoset. Specifically, the original XML document is
> > > qualified by the default namespace. On the otherhand, the received XML
> > > document is qualified by the namespace associated with the namespace
> > prefix
> > > "ns3". This is illegal in XML infoset.
> > >
> > > This is a serious bug when we are handling a "vanilla" XML documents
> > because
> > > we are sensitive in how the XML documents are represented literally.
> > >
> > > I hope I have any comments.
> > >
> > > Best regards,
> > >     Ryo Neyama @ IBM Research, Tokyo Research Laboratory
> > >     Internet Technology
> > >     neyama@trl.ibm.co.jp
> > >
> > >
> > >
> >
> >
>


Mime
View raw message