Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Date: Tue, 13 Dec 2011 22:43:30 +0000 (UTC)
From: "Simone Tripodi (Commented) (JIRA)" <jira@apache.org>
To: dev@cocoon.apache.org
Message-ID: 
 <174212043.7892.1323816210711.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1382592389.21444.1322558500305.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (COCOON3-82) Allow Saxon to be used as a XSLT
 transformer
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Simone Tripodi commented on COCOON3-82:
---------------------------------------

Having Saxon working in C3 would indeed awesome - I am not sure, due to Saxon license, any Saxon-based code can be included in Cocoon.

Can you provide a patch to show the integration works? I made tests with XSLT-C just using the SPI pattern, by adding in the classpath {{META-INF/services/javax.xml.transform.TransformerFactory}} file containing the XSLT-C {{org.apache.xalan.xsltc.trax.TransformerFactoryImpl}} factory - it should work with Saxon as well, but it would be wonderful having the proof :)
                
> Allow Saxon to be used as a XSLT transformer
> --------------------------------------------
>
>                 Key: COCOON3-82
>                 URL: https://issues.apache.org/jira/browse/COCOON3-82
>             Project: Cocoon 3
>          Issue Type: Improvement
>          Components: cocoon-sax
>    Affects Versions: 3.0.0-beta-1
>            Reporter: Huib Verweij
>
> In order to use XSLT 2.0 features (and beyond) in a XSLT transform I need to be able to use Saxon as a transformer. In C2.2 this could be done.
> There is a way of defining the transformer to be used in the system settings:  -Djavax.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryImpl. This might work, I am not sure, but then the choice of XSLT processor is gone - but that is perhaps not important?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira