Hi, I am trying to use Camel with Weblogic 12c but I am getting lots of
problems. First, I tried to use Camel with Spring but I got a name collision
error. In this forum there is a post that suggest to insert a
jaxb.properties file into Camel libraries, which I don't think it is a
proper solution.
Then I have tried to use Camel without Spring, just using a camel-config.xml
file and Camel servlet (as explained in the Camel examples) but I am still
getting this error:
*java.lang.RuntimeException: Error loading routes from resource:
classpath:/camel-config.xml*
at
org.apache.camel.component.servletlistener.CamelServletContextListener.extractRoutes(CamelServletContextListener.java:389)
at
org.apache.camel.component.servletlistener.CamelServletContextListener.contextInitialized(CamelServletContextListener.java:108)
at
weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:582)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at
weblogic.servlet.provider.WlsSubjectHandle.run(WlsSubjectHandle.java:57)
at
weblogic.servlet.internal.EventsManager.executeContextListener(EventsManager.java:233)
at
weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:190)
at
weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:175)
at
weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1730)
at
weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2740)
at
weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1704)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:781)
at
weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:213)
at
weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:208)
at
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:35)
at
weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:70)
at
weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:212)
at
weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java:111)
at
weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:124)
at
weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:213)
at
weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:208)
at
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:35)
at
weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:70)
at
weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:24)
at
weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:729)
at
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:35)
at
weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:258)
at
weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:48)
at
weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:165)
at
weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at
weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:582)
at
weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:148)
at
weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:114)
at
weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:335)
at
weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at
weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at
weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at
weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at
weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: javax.xml.bind.JAXBException: Provider
org.eclipse.persistence.jaxb.JAXBContextFactory could not be instantiated:
javax.xml.bind.JAXBException:
Exception Description: The property or field outputs was specified in
propOrder but is not a valid property.
- with linked exception:
[Exception [EclipseLink-50012] (Eclipse Persistence Services -
2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.JAXBException
Exception Description: The property or field outputs was specified in
propOrder but is not a valid property.]
- with linked exception:
*[javax.xml.bind.JAXBException:
Exception Description: The property or field outputs was specified in
propOrder but is not a valid property.*
After I few days trying to get Camel+Weblogic 12 working without success I
wonder if Camel supports Weblogic 12c.
Please help.
Thank you very much.
Jose
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Weblogic-12c-tp5733473.html
Sent from the Camel - Users mailing list archive at Nabble.com.
