[ 
http://issues.apache.org/jira/browse/XALANJ-1546?page=comments#action_12317433 
] 

Mark Hobson commented on XALANJ-1546:
-------------------------------------

Reconstructed Carlo's fix as a proper CVS patch in the hope that someone will 
apply this before 2.7 is released..?

> XSLTC: top-level xsl:variable with document() breaks
> ----------------------------------------------------
>
>          Key: XALANJ-1546
>          URL: http://issues.apache.org/jira/browse/XALANJ-1546
>      Project: XalanJ2
>         Type: Bug
>   Components: XSLTC
>     Versions: 2.5
>  Environment: Operating System: Linux
> Platform: Other
>     Reporter: Jeff Turner
>     Assignee: Xalan Developers Mailing List
>  Attachments: DocumentTest.java, XALANJ-1546.patch, document.xml, other.xml, 
> stylesheet.xsl, xalan-bug20381-usecase.zip, 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.
-
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]

Reply via email to