cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joerg Heinicke <joerg.heini...@gmx.de>
Subject Re: XSLTC problem with IBM WebSphere
Date Tue, 10 Jun 2003 20:11:40 GMT
What about the cocoon.xconf? I have added it a few days ago to the 
Cocoon 2.0 CVS, so that XSLTC is available by default (while Xalan is 
still the default processor).

Joerg

Michael Vennera wrote:
> I running some pretty large XSLT transformations
> through Cocoon and want to use XSLTC for the
> performance boost. No problem getting it to work in
> Tomcat. I dropped the xsltc.jar from the Xalan distro
> in WEB-INF/lib and added the following to the sitemap:
> 
>     <map:transformer name="xsltc"
> logger="sitemap.transformer.xslt"
> src="org.apache.cocoon.transformation.TraxTransformer"
> pool-max="32" pool-min="16" pool-grow="4">
>      
> <use-request-parameters>false</use-request-parameters>
>      
> <use-browser-capabilities-db>false</use-browser-capabilities-db>
>      
> <xslt-processor-role>org.apache.cocoon.components.xslt.XSLTProcessor/XSLTC</xslt-processor-role>
>     </map:transformer>
> 
> I then used transformers with type="xsltc" and it
> worked like a charm.
> 
> When I moved my Cocoon app to WebSphere 4.0, XSLTC
> wouldn't work. I keep getting a message that the
> processor can't find the hint for xsltc...
> 
> Any suggestions or ideas?


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org


Mime
View raw message