hi,
maybe this is related:
i tried to clone a DOM representation of a stylesheet (Node.cloneNode())
and this throws a namespace error. i experience this
behaviour with 1.3.1, while the 1.2 tree works fine.
(24.03.2001 15:45:49) HttpServer: org.w3c.dom.DOMException: DOM003 Namespace
error
at org.apache.xerces.dom.AttrNSImpl.<init>(AttrNSImpl.java:136)
at
org.apache.xerces.dom.DocumentImpl.createAttributeNS(DocumentImpl.java:1325)
at
org.apache.xerces.dom.DocumentImpl.importNode(DocumentImpl.java:935)
at
org.apache.xerces.dom.DocumentImpl.importNode(DocumentImpl.java:902)
at
org.apache.xerces.dom.DocumentImpl.cloneNode(DocumentImpl.java:345)
parsing of the stylesheet works fine (otherwise i wouldn't have a dom object
;-)
bye
christian
> -----Urspr�ngliche Nachricht-----
> Von: Arnaud Le Hors [mailto:[EMAIL PROTECTED]
> Gesendet: Montag, 26. M�rz 2001 22:51
> An: [EMAIL PROTECTED]
> Betreff: Re: Why does the importNode method raise namespace exception?
>
>
> jtao wrote:
> >
> > Hi,
> >
> > I used to use Xerces1.0.3. It worked just fine. When I
> moved to Xerces
> > 1.3.0, the importNode method
> > raised a namespace exception when the imported node has namespace.
> > Internally, the importNode call
> > createElementNS, and this method raises the exception. Why?
>
> How about: because there is a bug? ;-)
> The good news is that it's already been reported and fixed. Just grab
> the new version: 1.3.1.
> --
> Arnaud Le Hors - IBM Cupertino, XML Strategy Group
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
