[XALANJ-1042] TransformerIdentityImpl inlining external DTDs

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.4
• Component/s: transformation, Xalan-interpretive
• Environment: Operating System: Other; Platform: Other
• Bugzilla Id: 9542
• Assignee: Unassigned
• Reporter: Joe Kesselman
• Created: 31/May/02 22:06
• Updated: 16/Feb/11 23:01

Description

Apparently we're losing the boundaries separating the internal and external
subsets, with the result that the default/null TrAX transformation is copying
the latter into the former.

Note: Offline discussion suggests that our habit of calling
TransformerIdentityImpl the "default identity transformation" may be a bit
misleading. Current evidence is that, per the TrAX spec, this unnamed
transformation should be doing as complete a copy from source to result as is
possible, including data and details not representable in the XPath data model.
This means there are places where this really should be doing something
different from the so-called identity stylesheet. (The DOCTYPE is a good example
of this; an XSLT 1.0 stylesheet discards it and creates a new one based on
valuse in <xsl:output>.) We should confirm this and check our documentation to
be sure folks understand the distinction, and should probably write some
testcases specifically for this case.

See also Bug 1121, Bug 1831, Bug 5779 for other TransformerIdentityImpl
concerns we may want address while reviewing this one.

(This replaces a previous bug report, which had some misinformation. My
apologies.)