Saxon

You may be better off asking this one on StackOverflow. There are relatively few Saxon users who actively monitor this forum, and here at Saxonica we're not able to deal with product integration questions unless it happens to be one of the products we use ourselves (which Camel isn't). The expertise for "how to use Saxon with X" tends to come from the X user community.

When a third product X is tested and released to run with a particular Saxon version, it may or may not be possible to run it with a different Saxon version. Sometimes, as you suggest, simply putting a different Saxon JAR on the classpath is all that's needed. But sometimes the other application has explicit dependencies on a specific Saxon version or edition.

Judging from the information at https://stackoverflow.com/questions/34599874/using-saxon-pe-with-apache-camel-error-pre-loading-saxon-classes, Camel digs a little deeper into Saxon interfaces than some applications and is therefore more exposed to the kind of details that change between releases. That exchange was written 3 years ago; I don't know if the situation has changed since.

Thanks for your quick reply. I have posted my question in stackoverflow and just gave a shot here. Maybe there are some saxon users, who had the similar problem.