OK, thanks for the explanation Zoran, that makes sense and the error disappeared from the log after switching from TRACE to WARN.
One more note regarding this though - ".. tries to setup a security feature of Xerces ... and it is only triggered if Xerces is present on the classpath". I don't have Xerces in the classpath and I did not see any "if" in XmlConverter.createDocumentBuilderFactory() so it seems that it always tries to load that SecurityManager class.. or did I miss something again? Cheers, Alex -- View this message in context: http://camel.465427.n5.nabble.com/Classloader-error-org-apache-xerces-util-SecurityManager-not-found-tp5805263p5805325.html Sent from the Camel - Users mailing list archive at Nabble.com.
