Deploying a Jersey application on Weblogic 12.1.3

Question

I am having difficulty deploying a Jersey application to Weblogic 12, I have spent a lot of time battling with it and am still struggling. I have followed various suggestions on various sites (including this one), but I am still having issues. I don't know if I am fundamentally misunderstanding something basic, so I am hoping someone can help me.

Here is what I have so far:

I have created a new maven project. Here is my POM:



4.0.0

uk.co.omnicomengineering
jersey-weblogic
war
0.0.1-SNAPSHOT
jersey-weblogic


    jersey-weblogic
    
        
            org.apache.maven.plugins
            maven-compiler-plugin
            2.5.1
            true
            
                1.7
                1.7
            
        
    



    
        org.glassfish.jersey.containers
        jersey-container-servlet
        2.19
    
    
        javax.ws.rs
        javax.ws.rs-api
        2.0.1
        provided
    



    UTF-8

I have also deployed the jax-rs to Weblogic as in https://docs.oracle.com/middleware/1213/wls/RESTF/use-jersey20-ri.htm#RESTF299 and added the following weblogic.xml to my WEB-INF directory:




   jax-rs
   2.0
   false

Now, when I try to deploy the application, I get the following error:

<06-Jul-2015 11:19:45 o'clock BST>    (ApplicationHandler.java:329)
at org.glassfish.jersey.servlet.WebComponent.(WebComponent.java:339)
at org.glassfish.jersey.servlet.ServletContainer.init(ServletContainer.java:170)
Truncated. see log file for complete stacktrace
> 
<06-Jul-2015 11:19:45 o'clock BST>    (ApplicationHandler.java:329)
at org.glassfish.jersey.servlet.WebComponent.(WebComponent.java:339)
at org.glassfish.jersey.servlet.ServletContainer.init(ServletContainer.java:170)
Truncated. see log file for complete stacktrace
> 
<06-Jul-2015 11:19:45 o'clock BST>     
<06-Jul-2015 11:19:45 o'clock BST>     
<06-Jul-2015 11:19:45 o'clock BST>    (ApplicationHandler.java:329)
at org.glassfish.jersey.servlet.WebComponent.(WebComponent.java:339)
at org.glassfish.jersey.servlet.ServletContainer.init(ServletContainer.java:170)
Truncated. see log file for complete stacktrace

I am not really sure what is going wrong; am I using the wrong dependencies in my POM?

Any help that anyone could give would be gratefully received, I have spend a lot of time battling with Weblogic and Jersey!

--EDIT --

I have added the following to my weblogic.xml (following http://www.widecodes.com/CxVkWWgPUj/using-jersey-2x-web-service-on-weblogic-1211.html which seems to be a similar issue):




   jax-rs
   2.0
   false




    com.sun.jersey.*
    org.glassfish.jersey.*
    org.glassfish.hk2.*
    org.jvnet.hk2.*
    jersey.repackaged.org.objectweb.asm.*

    com.sun.research.ws.wadl.*
    com.sun.ws.rs.ext.*

    org.codehaus.jackson.*
    com.fasterxml.jackson.*

    org.codehaus.jettison.*

    javax.ws.rs.*

    org.objectweb.asm.*

    antlr.*

Now, when I deploy I get the following error:

<08-Jul-2015 14:16:25 o'clock BST>     
<08-Jul-2015 14:16:26 o'clock BST>     
<08-Jul-2015 14:16:26 o'clock BST>     
<08-Jul-2015 14:16:26 o'clock BST>     
<08-Jul-2015 14:16:26 o'clock BST>

pete · Accepted Answer

Since you were trying to deploy jersey as a shared library in WLS initially, I am assuming you were not supplying the jersey jar files with your EAR file, or at least that was not the intent.

I suspect the initial problem was that you might have deployed an older version of jax-rs from the deployable library. What you want to see in your deployments is jax-rs(2.0,2.5.1) - spec 2.0, implementation 2.5.1 - deployed as a shared library.
you should not put in the weblogic.xml unless you want the packages you specified "must always be loaded from the application" (ref Oracle doc here) - i.e. wls would look for these packages provided from your EAR - which I suspect is not what you want to do. You would only do this if you want to supply your own version of the jersey files - typically later more up to date version than what WLS provides.

I suggest you back out your changes you made on the weblogic.xml, you redeploy the jax-rs shared library, and make sure you did not accidentally included any of the jersey jar files in your EAR. I am not a maven user, so I'm not sure what you have on the POM file would automatically include these dependent files in your EAR file. You do not want this if you want to use the WLS versions of jersey.

Also, not sure if this would make a difference, but on my version of weblogic.xml, I included the implementation-version to match that of the shared library.

  
    jax-rs  
    2.0
    2.5.1  
    false

Good luck. These deployment issues can be tricky to maddening.

Deploying a Jersey application on Weblogic 12.1.3

Answers (2)

Related Questions