[ 
https://issues.apache.org/jira/browse/XALANJ-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17756633#comment-17756633
 ] 

Joe Kesselman commented on XALANJ-2422:
---------------------------------------

*WARNING:* TreeWalker exists in both org.apache.xml.serializer and 
org.apache.xml.utils, with some divergence, This was originally done to avoid 
cross-dependency between the serializer and utils. We should think about 
reconciling those.

It appears this user was looking at the .utils version. The logic does diverge 
a bit in this function. I'm too fuzzy to reconcile them right now but wanted to 
record this much.

> TreeWalker set systemId to dummy.xsl always (patch merge issue with 
> XALANJ-1985)
> --------------------------------------------------------------------------------
>
>                 Key: XALANJ-2422
>                 URL: https://issues.apache.org/jira/browse/XALANJ-2422
>             Project: XalanJ2
>          Issue Type: Bug
>          Components: Xalan
>    Affects Versions: 2.7.1, 2.7
>            Reporter: Brian McDonald
>            Priority: Blocker
>         Attachments: TreeWalker.patch
>
>
> If you take a look at the merge of the TreeWalker.patch 
> (org/apache/xml/serializer/TreeWalker.java) between versions 338117 and 
> 338053 (for XALANJ-1985), the constructor has some remnant code at the end 
> which breaks it's intended functionality.
> This chunk should be removed (sorry for not attaching a patch):
>       // Set the document locator  
>                 if (m_contentHandler != null)
>                         m_contentHandler.setDocumentLocator(m_locator);
>                 try {
>                    // Bug see Bugzilla  26741
>                   m_locator.setSystemId(System.getProperty("user.dir") + 
> File.separator + "dummy.xsl");
>                 } 
>                 catch (SecurityException se){// user.dir not accessible from 
> applet
> You can see that the constructor before this chunk already sets the document 
> locator on the content handler and if the system id is null, sets the dummy 
> value. Problem is that this extra chunk is setting the system id no matter 
> what, which breaks all attempts to load relative files, with no workaround 
> possible. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org

Reply via email to