Hi Frank, thanks for your quick replied.
I had already read that post but it didn't work for me.
I have eventually managed to fix the problem. This is my solution.
- I am using Camel without Spring, just using camel-config.xml file instead.
Camel is started by a listener in the web.xml file
- In order to fix the jaxb issue, I have created the file
META-INF/services/javax.xml.bind.JAXBContext, its content is just
"com.sun.xml.bind.v2.ContextFactory".
- I have created the file
META-INF/services/com.sun.xml.ws.spi.db.BindingContextFactory, its content
is just "com.sun.xml.ws.db.glassfish.JAXBRIContextFactory".
- I have added this in my weblogic.xml file (my application is a WAR file):
<container-descriptor>
<prefer-web-inf-classes>false</prefer-web-inf-classes>
<prefer-application-resources>
<resource-name>META-INF/services/com.sun.xml.ws.spi.db.BindingContextFactory</resource-name>
<resource-name>META-INF/services/javax.xml.bind.JAXBContext</resource-name>
</prefer-application-resources>
</container-descriptor>
This configuration overrides the default Weblogic jaxb provider. This way is
working for me. I hope it could help.
By the way, I am trying to use this configuration but using Spring
(camel-spring). Now I am getting an occasional NullPointerException when
parsing the applicationContext. I am using Camel 2.11 and JDK7.
Does Camel 2.11 support JDK7?
Thanks a lot.
Jose
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Weblogic-12c-tp5733473p5733515.html
Sent from the Camel - Users mailing list archive at Nabble.com.
