[ http://issues.apache.org/jira/browse/XALANJ-1127?page=all ]
Brian Minchau updated XALANJ-1127:
----------------------------------
Version: 2.4
(was: Latest Development Code)
> DOMSource requires namespace declarations?
> ------------------------------------------
>
> Key: XALANJ-1127
> URL: http://issues.apache.org/jira/browse/XALANJ-1127
> Project: XalanJ2
> Type: Bug
> Components: DTM
> Versions: 2.4
> Environment: Operating System: Other
> Platform: Other
> Reporter: Joe Kesselman
> Assignee: Xalan Developers Mailing List
>
> A user reports that trying to process a hand-generated DOM2 tree is failing
> unless he generates explicit namespace declaration attributes. That wouldn't
> surprise me, but In Theory it shouldn't be necessary; we ought to be able to
> recognize the namespace and prefix fields of the DOM nodes as implying a
> declaration (just as DOM serialization to XML syntax would).
> Doing this in DOM2DTM is possible but a bit ugly; it's basically the same
> issue
> as the implied declaration for xml: which we're now synthesizing as an
> "imperfect" DOM node.
> However, there are some complications here. In particular, it's possible for
> the
> implied declarations on an element and on one of its attributes to conflict.
> The
> DOM Level 3 WD has a proposal for a namespace normalization process which
> deals
> with this -- but it reserves the right to change prefixes when necessary to
> reconcile this, and it's really unclear that Xalan ought to do so.
> So the proper answer may, in fact, be to say that the DOM must be
> namespace-normalized before submitting it to Xalan... or to do what fixup we
> can, and throw an error if we hit a conflict we can't work around.
> (IBMers: See forums.software.xml discussion, today, for context.)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
