Hi Jose, as I stated in this thread: http://camel.465427.n5.nabble.com/Spring-Camel-Context-initialization-error-in-weblogic-12c-td5733202.html <http://camel.465427.n5.nabble.com/Spring-Camel-Context-initialization-error-in-weblogic-12c-td5733202.html> the error concerning JAXB is a classloading issue in weblogic 12c and could be solved by changing the classloading policy.
However it's not sure that this is the only issue. All I can say is that I have camel up and running on weblogic 12c. It's not been that easy as one would expect but finally it works. By the way why do you think it's not a proper solution to patch a jar with information that's needed by weblogic to work correctly? Frank -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Weblogic-12c-tp5733473p5733477.html Sent from the Camel - Users mailing list archive at Nabble.com.
