Jersey JAX-RS support in WAS 6.1 - Websphere

This is a discussion on Jersey JAX-RS support in WAS 6.1 - Websphere ; Does WebSphere v6.1.0.x support JAX-RS? With or without the feature pack for WebServices? I have an application deployed to WAS v6.1.0.25 w/o the feature pack for webservices bundled with Jersey (implementation of JAX-RS) that gives the following error: Servlet Error]-[Jersey ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Jersey JAX-RS support in WAS 6.1

  1. Jersey JAX-RS support in WAS 6.1

    Does WebSphere v6.1.0.x support JAX-RS? With or without the feature
    pack for WebServices? I have an application deployed to WAS v6.1.0.25
    w/o the feature pack for webservices bundled with Jersey (implementation
    of JAX-RS) that gives the following error:

    Servlet Error]-[Jersey Web Application]:
    com.sun.jersey.api.container.ContainerException: The ResourceConfig
    instance does not contain any root resource classes. at
    com.sun.jersey.impl.application.WebApplicationImpl .processRootResources(WebApplicationImpl.java:767)
    at
    com.sun.jersey.impl.application.WebApplicationImpl .initiate(WebApplicationImpl.java:668)
    at
    com.sun.jersey.impl.application.WebApplicationImpl .initiate(WebApplicationImpl.java:485)
    at
    com.sun.jersey.spi.container.servlet.ServletContai ner.initiate(ServletContainer.java:559)
    at
    com.sun.jersey.spi.container.servlet.ServletContai ner.load(ServletContainer.java:483)
    at
    com.sun.jersey.spi.container.servlet.ServletContai ner.init(ServletContainer.java:165)
    at
    com.ibm.ws.webcontainer.servlet.ServletWrapper.ini t(ServletWrapper.java:227)
    at
    com.ibm.ws.wswebcontainer.servlet.ServletWrapper.i nit(ServletWrapper.java:320)
    at
    com.ibm.ws.webcontainer.servlet.ServletWrapper.han dleRequest(ServletWrapper.java:435)
    at
    com.ibm.ws.wswebcontainer.servlet.ServletWrapper.h andleRequest(ServletWrapper.java:481)
    at com.ibm.ws.webcontainer.webapp.WebApp.handleReques t(WebApp.java:3507)
    at
    com.ibm.ws.webcontainer.webapp.WebGroup.handleRequ est(WebGroup.java:269)
    at
    com.ibm.ws.webcontainer.WebContainer.handleRequest (WebContainer.java:815)
    at
    com.ibm.ws.wswebcontainer.WebContainer.handleReque st(WebContainer.java:1466)
    at
    com.ibm.ws.webcontainer.channel.WCChannelLink.read y(WCChannelLink.java:122)
    at
    com.ibm.ws.http.channel.inbound.impl.HttpInboundLi nk.handleDiscrimination(HttpInboundLink.java:458)
    at
    com.ibm.ws.http.channel.inbound.impl.HttpInboundLi nk.handleNewInformation(HttpInboundLink.java:387)
    at
    com.ibm.ws.http.channel.inbound.impl.HttpInboundLi nk.ready(HttpInboundLink.java:267)
    at
    com.ibm.ws.tcp.channel.impl.NewConnectionInitialRe adCallback.sendToDiscriminators(NewConnectionIniti alReadCallback.java:214)
    at
    com.ibm.ws.tcp.channel.impl.NewConnectionInitialRe adCallback.complete(NewConnectionInitialReadCallba ck.java:113)
    at
    com.ibm.ws.tcp.channel.impl.AioReadCompletionListe ner.futureCompleted(AioReadCompletionListener.java :165)
    at
    com.ibm.io.async.AbstractAsyncFuture.invokeCallbac k(AbstractAsyncFuture.java:217)
    at
    com.ibm.io.async.AsyncChannelFuture.fireCompletion Actions(AsyncChannelFuture.java:161)
    at com.ibm.io.async.AsyncFuture.completed(AsyncFuture .java:136) at
    com.ibm.io.async.ResultHandler.complete(ResultHand ler.java:196) at
    com.ibm.io.async.ResultHandler.runEventProcessingL oop(ResultHandler.java:751)
    at com.ibm.io.async.ResultHandler$2.run(ResultHandler .java:881) at
    com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.j ava:149

    This app runs successfully in Tomcat. Any insight is appreciated.

    cheers
    -- Dan

  2. Re: Jersey JAX-RS support in WAS 6.1

    Dan,

    Try the trick mentioned here as it could be Jersey problem with scanning the WAR under WAS:
    http://markmail.org/message/gmk4td7ziyxprotd

    thanks,
    dims

    On 07/10/2009 12:46 AM, Dan O'Neill wrote:
    > Does WebSphere v6.1.0.x support JAX-RS? With or without the feature
    > pack for WebServices? I have an application deployed to WAS v6.1.0.25
    > w/o the feature pack for webservices bundled with Jersey (implementation
    > of JAX-RS) that gives the following error:
    >
    > Servlet Error]-[Jersey Web Application]:
    > com.sun.jersey.api.container.ContainerException: The ResourceConfig
    > instance does not contain any root resource classes. at
    > com.sun.jersey.impl.application.WebApplicationImpl .processRootResources(WebApplicationImpl.java:767)
    > at
    > com.sun.jersey.impl.application.WebApplicationImpl .initiate(WebApplicationImpl.java:668)
    > at
    > com.sun.jersey.impl.application.WebApplicationImpl .initiate(WebApplicationImpl.java:485)
    > at
    > com.sun.jersey.spi.container.servlet.ServletContai ner.initiate(ServletContainer.java:559)
    > at
    > com.sun.jersey.spi.container.servlet.ServletContai ner.load(ServletContainer.java:483)
    > at
    > com.sun.jersey.spi.container.servlet.ServletContai ner.init(ServletContainer.java:165)
    > at
    > com.ibm.ws.webcontainer.servlet.ServletWrapper.ini t(ServletWrapper.java:227)
    > at
    > com.ibm.ws.wswebcontainer.servlet.ServletWrapper.i nit(ServletWrapper.java:320)
    > at
    > com.ibm.ws.webcontainer.servlet.ServletWrapper.han dleRequest(ServletWrapper.java:435)
    > at
    > com.ibm.ws.wswebcontainer.servlet.ServletWrapper.h andleRequest(ServletWrapper.java:481)
    > at com.ibm.ws.webcontainer.webapp.WebApp.handleReques t(WebApp.java:3507)
    > at
    > com.ibm.ws.webcontainer.webapp.WebGroup.handleRequ est(WebGroup.java:269)
    > at
    > com.ibm.ws.webcontainer.WebContainer.handleRequest (WebContainer.java:815) at
    > com.ibm.ws.wswebcontainer.WebContainer.handleReque st(WebContainer.java:1466)
    > at
    > com.ibm.ws.webcontainer.channel.WCChannelLink.read y(WCChannelLink.java:122)
    > at
    > com.ibm.ws.http.channel.inbound.impl.HttpInboundLi nk.handleDiscrimination(HttpInboundLink.java:458)
    > at
    > com.ibm.ws.http.channel.inbound.impl.HttpInboundLi nk.handleNewInformation(HttpInboundLink.java:387)
    > at
    > com.ibm.ws.http.channel.inbound.impl.HttpInboundLi nk.ready(HttpInboundLink.java:267)
    > at
    > com.ibm.ws.tcp.channel.impl.NewConnectionInitialRe adCallback.sendToDiscriminators(NewConnectionIniti alReadCallback.java:214)
    > at
    > com.ibm.ws.tcp.channel.impl.NewConnectionInitialRe adCallback.complete(NewConnectionInitialReadCallba ck.java:113)
    > at
    > com.ibm.ws.tcp.channel.impl.AioReadCompletionListe ner.futureCompleted(AioReadCompletionListener.java :165)
    > at
    > com.ibm.io.async.AbstractAsyncFuture.invokeCallbac k(AbstractAsyncFuture.java:217)
    > at
    > com.ibm.io.async.AsyncChannelFuture.fireCompletion Actions(AsyncChannelFuture.java:161)
    > at com.ibm.io.async.AsyncFuture.completed(AsyncFuture .java:136) at
    > com.ibm.io.async.ResultHandler.complete(ResultHand ler.java:196) at
    > com.ibm.io.async.ResultHandler.runEventProcessingL oop(ResultHandler.java:751)
    > at com.ibm.io.async.ResultHandler$2.run(ResultHandler .java:881) at
    > com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.j ava:149
    >
    > This app runs successfully in Tomcat. Any insight is appreciated.
    >
    > cheers
    > -- Dan



+ Reply to Thread