[ http://issues.apache.org/jira/browse/XALANJ-1087?page=all ]
Brian Minchau updated XALANJ-1087:
----------------------------------
Version: 2.4
(was: Latest Development Code)
> XSLTC: TemplatesHandlerImpl.setLocator() incorrectly retrieves System Id
> ------------------------------------------------------------------------
>
> Key: XALANJ-1087
> URL: http://issues.apache.org/jira/browse/XALANJ-1087
> Project: XalanJ2
> Type: Bug
> Components: XSLTC
> Versions: 2.4
> Environment: Operating System: Other
> Platform: Other
> Reporter: Erik Bruchez
> Assignee: Xalan Developers Mailing List
>
> The System ID is retrieved from the Locator object right when
> setDocumentLocator() is called on TemplatesHandlerImpl:
> setSystemId(locator.getSystemId());
> This is a problem for example when the source of the sax events is a
> DOMSource.
> In that case, a TreeWalker walks the DOM and generates sax events. The issue
> is
> that org.apache.xml.utils.TreeWalker sets the Locator on the ContentHandler
> before setting the System ID on the Locator (which I think is ok behavior). At
> that point, TemplatesHandlerImpl has already consumed a null System ID. This
> means that if one uses an identity transformation to create a Templates using
> a
> DOMSource and a TemplatesHandler, the latter won't have the right System ID
> set.
> This sounds easy enough to fix. The regular Xalan implementation does not have
> this bug.
--
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]
