I see, this explains it, thank you. org.apache.xalan.xslt.Process is probably using an interpreter internally, whereas I will need the compiler. In fact, the plan is to precompile and cache the xslt object to speed up the transformations.
I am happy thought that XSLTC can use Java classes, which I will use in a more complex logic. Mukul Gandhi wrote: > > On Fri, Mar 13, 2009 at 8:41 PM, Bohdan <boh...@clarusmt.com> wrote: >> Very surprised that it works for you, because it should not. >> I found out that xalan:component and xalan:script extensions for XSLTC >> actually are not supported: >> http://xml.apache.org/xalan-j/extensions_xsltc.html (Constraints >> section). > > I tested with Xalan processor from command line (using > org.apache.xalan.xslt.Process) and the example posted on Xalan site > worked fine. > > as you pointed, XSLTC presently doesn't support this feature. > > > -- > Regards, > Mukul Gandhi > > -- View this message in context: http://www.nabble.com/Xalan-J-extensions-not-working.-Is-this-correct-behavior--tp22482719p22499900.html Sent from the Xalan - J - Users mailing list archive at Nabble.com.
