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

Bengt Rodehav commented on CAMEL-5798:
--------------------------------------

OK, yes I guess that is another way of making it work. However, I haven't seen 
this documented anywhere. Generally I think it is a bad approach to require 
configuring the container to make it work since it makes it very hard to put a 
lot of different things in the container - they sometimes need incompatible 
tweaks.

I remember that I've had a discussing about this with Guillaume Nodet sometime 
back. I think he recommended to be restrictive about opening up JVM packages 
(via jre.properties) and instead install bundles who export those packages. I 
agree with that approach for a couple of reasons:

* Like I said, when you start tweaking the jre.properties you easily end up in 
situations where you can't have two different features co-existing.
* I prefer having the possibility to use a pure Karaf installation and instead 
use the supported "feature" system to add features. It means I don't have 
customize the container which is worth quite a lot to me.
* Tweaking the jre.properties requires more knowledge and more documentation. 
It's a less simple approach.

Both ways work of course. Like I said I will go for 2.11 when it's released so 
I'm fine. Meanwhile I use my own feature that does exactly what 2.11 will do. I 
just don't see the reason to use a different (more complicated) approach for 
2.10.x since it makes life harder for those who use camel-saxon on that branch.
                
> camel-saxon does not work on pure Karaf 2.3.0
> ---------------------------------------------
>
>                 Key: CAMEL-5798
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5798
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-saxon
>    Affects Versions: 2.10.2
>            Reporter: Bengt Rodehav
>         Attachments: saxon-problem.zip
>
>
> This has been discussed on the mailing list:
> http://camel.465427.n5.nabble.com/Saxon-and-saxon9he-td5722663.html
> It seems like the camel-saxon feature only has been tested on Servicemix and 
> not on a pure Karaf installation. Servicemix comes with a pre-installed 
> XmlResolver while Karaf doesn't and it seems like camel-saxon requires an 
> XmlResolver. It should therefore be added to the camel-saxon feature.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to