Major Description
The mechanism for XML parsing (feature file, kar feature detector, etc) is sensitive to the thread class loader, which forces the application to switch the thread class loader before calling those services.
How to reproduce: Call the kar service from a REST endpoint.
I created this Jira after a discussion on the mailing list with Guillaume:
You're right, I think the current setup on 4.1 is not optimal and a bit too sensitive to the thread context class loader.
Can you simply remove the xalan and xerces jars from the lib/endorsed folder and the corresponding export packages in etc/config.properties ?
If you want to use xalan and xerces, deploy them as bundles instead.
Also, please raise a JIRA so that we can fix that.