-
Bug
-
Resolution: Done
-
Critical
-
None
-
1.2
-
None
-
Weblogic 12.2.x
Magnolia 5.6.4
-
-
Empty show more show less
-
Saigon 139, Saigon 140, Saigon 141
-
5
REST modules currently use resteasy-jaxrs-3.0.19.Final library which in turn uses jboss-jaxrs-api_2.0_spec.
Weblogic 12.1.3 uses internally jersey-bundle-1.9 and jsr311-api-1.1.1.
The problem is that both libraries are having a conflict which prevents magnolia's war to deploy:
<Servlet: "Jersey" failed to preload on startup in Web application: "test-stk-webapp-1.0-SNAPSHOT.war". com.sun.jersey.spi.inject.Errors$ErrorMessagesException at com.sun.jersey.spi.inject.Errors.processErrorMessages(Errors.java:170) at com.sun.jersey.spi.inject.Errors.postProcess(Errors.java:136) at com.sun.jersey.spi.inject.Errors.processWithErrors(Errors.java:199) at com.sun.jersey.server.impl.application.WebApplicationImpl.initiate(WebApplicationImpl.java:795) at com.sun.jersey.server.impl.application.WebApplicationImpl.initiate(WebApplicationImpl.java:790)
On previous versions of the REST modules (in Magnolia 5.4.x), resteasy-jaxrs-3.0.4.Final was being used which didn't have any dependency with jboss-jaxrs-api_2.0_spec and didn't have any conflicts deploying on Weblogic.
Full log of the deploy issue attached
- clones
-
MGNLREST-82 Can't install modules because of conflict on Weblogic with Jersey library
- Closed
- depends upon
-
MGNLWLS-17 Weblogic module is no longer compatible with Magnolia 5.6
- Closed
- is related to
-
MGNLWLS-20 Can't run endpoint and render page at the first time in weblogic server
- Accepted