[
https://issues.apache.org/jira/browse/CAMEL-10815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luca Burgazzoli updated CAMEL-10815:
------------------------------------
Fix Version/s: (was: 2.20.0)
3.0.0
> Create a saxon-xslt component
> -----------------------------
>
> Key: CAMEL-10815
> URL: https://issues.apache.org/jira/browse/CAMEL-10815
> Project: Camel
> Issue Type: New Feature
> Components: camel-saxon
> Reporter: Luca Burgazzoli
> Priority: Minor
> Fix For: 3.0.0, Future
>
>
> I've recently been working on camel-saxon and camel-xslt to enable
> saxon specific stuffs in camel-xslt and this required some little
> reflection hacks which could make it harder to detect potential api
> breaks when updating saxon and could be problematic for java 9 if
> saxon does not properly configure the modules system so we should create a
> saxon-xslt component (to be done after 2.19) which inherit from xslt
> component and adds saxon specifc stuffs without reflection hacks.
> So with component:
> - xslt --> you can still use saxon but can't confiugre saxon specific features
> - saxon-xslt --> same as xslt but you can configure/use saxon specific
> features
> It also ensures that users are not in doubt if they use saxon or not. Usually
> Saxon offers more advanced features that you dont have from the JDK.
> And maybe we can add something so users can install the commercial saxon and
> unlock xslt 3.0 functionality or what else is exclusive in their commercial
> product.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
