After enumerating all the ways that don't work, I think I have this
figured out.
(I'm trying to wrap Saxon's TransformerFactoryImpl so that I can
configure it with our own Java function implementations as Saxon
Integrated Extension Function classes.)
XSLTProcessor *must* be defined Avalon-style.
Wow, you Haka-Smart guy :) No need for a Saxon commercial licence anymore
with Saxon-HE :)
That was what we missed with new Saxon-HE :) Thanks! Good Job!
With C3 (Cocoon 3.0) you can use Java-only code with no cocoon-sitemap
config dependency :)
Such a little thing and I get a big smile on my
On Tue, Dec 10, 2019 at 11:21:09PM +0100, gelo1234 wrote:
> I don't think this is the proper way to do this and if it's possible at
> all. Extension functions are only available in commercial releases of Saxon
> (PE and EE).
> I'm afraid they are not available in open-source Saxon-HE. We were
Hi Mark,
I don't think this is the proper way to do this and if it's possible at
all. Extension functions are only available in commercial releases of Saxon
(PE and EE).
I'm afraid they are not available in open-source Saxon-HE. We were trying
to use Saxon-HE with Cocoon 3.0 and
On Tue, Dec 10, 2019 at 12:10:41AM +0100, gelo1234 wrote:
> Mark,
>
> Why do you need a Custom XSLT Processor other than Saxon actually?? Saxon
> should do the right thing. Why wrapping it inside any "upper-level"
> Transformer? It's getting kinda weird. You can always add a new Java class
> to
Mark,
Why do you need a Custom XSLT Processor other than Saxon actually?? Saxon
should do the right thing. Why wrapping it inside any "upper-level"
Transformer? It's getting kinda weird. You can always add a new Java class
to standard Cocoon Processors/Transformers.
On Thu, Dec 05, 2019 at 04:13:08PM +0100, Javier Puerto wrote:
> I recommend you to use the Spring configuration. I never had this
> requirement before but by the error message and the configuration fragment
> that you have sent the NPE is caused because you are not passing an
> instance of
Hi Mark,
Also make sure, you have that class:
org.dspace.saxon.ConfigurableTransformerFactory available on the CLASSPATH
(-> WEB-INF/lib/*.jar)
And a proper version/config for Saxon HE. Here is the guide:
https://stackoverflow.com/questions/22483436/using-saxon9-for-xslt-with-apache-cocoon-2-2
Hi Mark,
I recommend you to use the Spring configuration. I never had this
requirement before but by the error message and the configuration fragment
that you have sent the NPE is caused because you are not passing an
instance of "org.dspace.saxon.ConfigurableTransformerFactory", you are
passing
Hi Mark,
I never could get 2.2 working
However, I'm using 2.12 every day, all over the world - mostly with Saxon
for XSLT 2.0
All I can advise, use 2.12...
Best regards
Warrell
On Wed, 4 Dec 2019, 9:46 pm Mark H. Wood, wrote:
> I'm using Cocoon 2.2. I need to pass a custom XSLT
10 matches
Mail list logo
