Try without Camel and do the XSLT from regular Java code.
I doubt Camel have anything to do with it as its just asking the XSLT stuff to do its works.
And I assume you have tried googling to see if you can find others with similar issue?
Thanks for the reply. I guess, camel itself can't fix this issue. This is however certainly something which many of the developers will be looking for while using XSLT. Yes, I did google and could not find a solution for it and was just looking for some workaround. I think we will go with our own XSLT code in java as you suggested.
If you come up with a solution. Then please let us know, maybe there is something we can improved in Camel to let it work out of the box.