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

Mike Moulton commented on XALANJ-1546:
--------------------------------------

Will this issue be addressed prior to the release of 2.7.1? It's been in Jira 
for a while and requires my agency to maintain a separate version of xalan 
containing this fix. Seems the patch is quite simple so hoping it can become 
official with 2.7.1.

> XSLTC: top-level xsl:variable with document() breaks
> ----------------------------------------------------
>
>                 Key: XALANJ-1546
>                 URL: https://issues.apache.org/jira/browse/XALANJ-1546
>             Project: XalanJ2
>          Issue Type: Bug
>          Components: XSLTC
>    Affects Versions: 2.5
>         Environment: Operating System: Linux
> Platform: Other
>            Reporter: Jeff Turner
>         Assigned To: Xalan Developers Mailing List
>         Attachments: document.xml, DocumentTest.java, other.xml, 
> stylesheet.xsl, xalan-bug20381-usecase.zip, XALANJ-1546.patch, xsltcbug2.tgz
>
>
> Hi,
> Seems that XSLTC doesn't like using document() in a top-level element:
> <xsl:variable name="config" select="document('skinconf.xml')"/>
> This has the effect of *importing* skinconf.xml nodes. If I then have a
> copy-across rule:
>   <xsl:template match="node()|@*" priority="-1">
>     <xsl:copy>
>       <xsl:apply-templates select="@*"/>
>       <xsl:apply-templates/>
>     </xsl:copy>
>   </xsl:template>
> Then skinconf.xml element bodies appear in the output.
> This bug does not show when using regular Xalan, nor does it show up when 
> using
> XSLTC from the command-line. It seems to have something to do with the
> document() function.
> Attached is a sample subsitemap which demonstrates the bug. It can be unpacked
> directly into build/webapp/. A script for testing command-line XSLTC is also
> provided.
> --Jeff

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to