The following issue has been updated:

    Updater: Brian Minchau (mailto:[EMAIL PROTECTED])
       Date: Sat, 4 Sep 2004 6:01 PM
    Changes:
             assignee changed from Xalan Developers Mailing List
             description changed from Redirect extension support is incompatible 
between 2 variants of Xalan. 

Namespace xmlns:redirect="http://xml.apache.org/xalan/redirect"; is not 
supported by interpretive Xalan. It is however required by XSLTC. This 
prevents us from using the same stylesheets for both variants of Xalan 
(interpretive and XSLTC). 

TransformerFactory.newTemplates() fails on stylesheet using 
xmlns:redirect="http://xml.apache.org/xalan/redirect"; namespace. This is when 
org.apache.xalan.processor.TransformerFactoryImpl is used as transformer. All 
is fine for XSLTC ("org.apache.xalan.xsltc.trax.TransformerFactoryImpl").

Example stylesheet (taken from http://xml.apache.org/xalan-
j/extensions_xsltc.html#redirect_ext). This stylesheet will cause failure 
during TransformerFactory.newTemplates() call.

<xsl:stylesheet 
   xmlns:xsl="http://www.w3.org/1999/XSL/Transform";
   xmlns:xsltc="http://xml.apache.org/xalan/xsltc";
   xmlns:redirect="http://xml.apache.org/xalan/redirect";
   extension-element-prefixes="xsltc redirect"
   version="1.0">
   <xsl:template match="/">
     <xsl:text>This goes to standard output</xsl:text>
     <xsltc:output file="blob.xml">
       <xsl:text>This ends up in the file 'blob.xml'</xsl:text>
     </xsltc:output>
     <redirect:write file="blob2.xml">
       <xsl:text>This ends up in the file 'blob2.xml'</xsl:text>
     </redirect:write>
   </xsl:template>
</xsl:stylesheet> to Redirect extension support is incompatible between 2 variants of 
Xalan. 

Namespace xmlns:redirect="http://xml.apache.org/xalan/redirect"; is not 
supported by interpretive Xalan. It is however required by XSLTC. This 
prevents us from using the same stylesheets for both variants of Xalan 
(interpretive and XSLTC). 

TransformerFactory.newTemplates() fails on stylesheet using 
xmlns:redirect="http://xml.apache.org/xalan/redirect"; namespace. This is when 
org.apache.xalan.processor.TransformerFactoryImpl is used as transformer. All 
is fine for XSLTC ("org.apache.xalan.xsltc.trax.TransformerFactoryImpl").

Example stylesheet (taken from http://xml.apache.org/xalan-
j/extensions_xsltc.html#redirect_ext). This stylesheet will cause failure 
during TransformerFactory.newTemplates() call.

<xsl:stylesheet 
   xmlns:xsl="http://www.w3.org/1999/XSL/Transform";
   xmlns:xsltc="http://xml.apache.org/xalan/xsltc";
   xmlns:redirect="http://xml.apache.org/xalan/redirect";
   extension-element-prefixes="xsltc redirect"
   version="1.0">
   <xsl:template match="/">
     <xsl:text>This goes to standard output</xsl:text>
     <xsltc:output file="blob.xml">
       <xsl:text>This ends up in the file 'blob.xml'</xsl:text>
     </xsltc:output>
     <redirect:write file="blob2.xml">
       <xsl:text>This ends up in the file 'blob2.xml'</xsl:text>
     </redirect:write>
   </xsl:template>
</xsl:stylesheet>
             environment changed from Operating System: Other
Platform: PC to Operating System: Other
Platform: PC
             priority changed to Blocker
             Component changed to Xalan extensions
             Component changed from Xalan
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/XALANJ-1927?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/XALANJ-1927

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XALANJ-1927
    Summary: Inconsistent support of redirect extension by Xalan and Xalan-XSLTC
       Type: Bug

     Status: Unassigned
   Priority: Blocker

    Project: XalanJ2
 Components: 
             Xalan extensions
   Versions:
             2.6

   Assignee: 
   Reporter: Barys Dubauski

    Created: Thu, 19 Aug 2004 9:38 PM
    Updated: Sat, 4 Sep 2004 6:01 PM
Environment: Operating System: Other
Platform: PC

Description:
Redirect extension support is incompatible between 2 variants of Xalan. 

Namespace xmlns:redirect="http://xml.apache.org/xalan/redirect"; is not 
supported by interpretive Xalan. It is however required by XSLTC. This 
prevents us from using the same stylesheets for both variants of Xalan 
(interpretive and XSLTC). 

TransformerFactory.newTemplates() fails on stylesheet using 
xmlns:redirect="http://xml.apache.org/xalan/redirect"; namespace. This is when 
org.apache.xalan.processor.TransformerFactoryImpl is used as transformer. All 
is fine for XSLTC ("org.apache.xalan.xsltc.trax.TransformerFactoryImpl").

Example stylesheet (taken from http://xml.apache.org/xalan-
j/extensions_xsltc.html#redirect_ext). This stylesheet will cause failure 
during TransformerFactory.newTemplates() call.

<xsl:stylesheet 
   xmlns:xsl="http://www.w3.org/1999/XSL/Transform";
   xmlns:xsltc="http://xml.apache.org/xalan/xsltc";
   xmlns:redirect="http://xml.apache.org/xalan/redirect";
   extension-element-prefixes="xsltc redirect"
   version="1.0">
   <xsl:template match="/">
     <xsl:text>This goes to standard output</xsl:text>
     <xsltc:output file="blob.xml">
       <xsl:text>This ends up in the file 'blob.xml'</xsl:text>
     </xsltc:output>
     <redirect:write file="blob2.xml">
       <xsl:text>This ends up in the file 'blob2.xml'</xsl:text>
     </redirect:write>
   </xsl:template>
</xsl:stylesheet>


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

Reply via email to