Comments on: Hacking Jersey/JAX-RS to run RESTful web services on Google AppEngine/Java

By: Nicolas

Nicolas — Sat, 05 Dec 2009 09:29:57 +0000

Restlet DOES provide Jax-rs functionnalities with an extension:
http://wiki.restlet.org/docs_2.0/13-restlet/28-restlet/57-restlet.html

By: lqd

lqd — Fri, 27 Nov 2009 09:54:26 +0000

I don’t think so, however Paul Sandoz recently said they would look at it for the next release, so it shouldn’t be too long.

By: Andy

Andy — Fri, 20 Nov 2009 12:43:04 +0000

Has anyone got Jersey 1.1.4 and GAE 1.2.6 (latest versions as of writing) to work together?

Ideally I would like a JAX-RS implementation to not load any providers/modules for XML and JSON as I want to drop in providers that get around App Engine’s restrictions.

Restlet seems to work fine. But it appears to not implement all parts of the JAX-RS specification (eg. all @Context type injections).

By: lqd

lqd — Mon, 29 Jun 2009 08:17:16 +0000

I was using 1.2.0.

At first i thought 1.2.1 wouldn’t be so different. But I’ve actually run into an almost unsurmountable amount of weird exceptions with Jersey 1.1.0-ea and sdk 1.2.1. We shouldn’t have to do this, at this point it doesn’t seem GAE’s VM is really usable with real world libs and frameworks, without heavy work on our part.

By: Nicolas

Nicolas — Sun, 28 Jun 2009 20:17:52 +0000

Hi,
It looks like taking time for the first connection.

Uncaught exception from servlet
com.google.apphosting.runtime.HardDeadlineExceededError
(…)

But after 2-3 minuts, it’s ok. I have a lot of javadoc files in the webapp and it’s possible that everything is parsed at the first connection to look for @Path classes.

By: Iqbal Yusuf

Iqbal Yusuf — Tue, 23 Jun 2009 02:03:04 +0000

Hi,

Which appengine SDK version your container work with? I’m trying 1.2.1 and having problem.

Jun 23, 2009 1:07:37 AM org.hybird.appengine.jersey.container.WebApplicationImpl processRootResources
SEVERE: The ResourceConfig instance does not contain any root resource classes.
Jun 23, 2009 1:07:37 AM com.google.apphosting.utils.jetty.JettyLogger warn
WARNING: failed Jersey Web Application
javax.servlet.ServletException: com.sun.jersey.api.container.ContainerException: The ResourceConfig instance does not contain any root resource classes.

By: Lemao

Lemao — Mon, 08 Jun 2009 01:51:54 +0000

First of all, thanks for the patch.

Unfortunately I am still getting errors when deploying to my appengine account.

(I am using your patch with Jersey 1.0.2)

This is the exception I am seeing. Any ideas?

thanks,

com.sun.jersey.core.spi.component.ProviderFactory _getComponentProvider: The provider class, class com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App, could not be instantiated
java.lang.SecurityException: Unable to get members for class com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$App
at com.google.apphosting.runtime.security.shared.intercept.java.lang.Class_$10.run(Class_.java:357)
at com.google.apphosting.runtime.security.shared.intercept.java.lang.Class_$10.run(Class_.java:347)
at java.security.AccessController.doPrivileged(Native Method)
at com.google.apphosting.runtime.security.shared.intercept.java.lang.Class_.getMembers(Class_.java:347)
at com.google.apphosting.runtime.security.shared.intercept.java.lang.Class_.getMethods(Class_.java:170)
at com.sun.jersey.core.reflection.MethodList.(MethodList.java:57)
at com.sun.jersey.core.spi.component.ComponentConstructor.getPostConstructMethod(ComponentConstructor.java:124)
at com.sun.jersey.core.spi.component.ComponentConstructor.(ComponentConstructor.java:118)
at com.sun.jersey.core.spi.component.ProviderFactory.getInstance(ProviderFactory.java:205)
at com.sun.jersey.core.spi.component.ProviderFactory._getComponentProvider(ProviderFactory.java:133)
at com.sun.jersey.core.spi.component.ProviderFactory.getComponentProvider(ProviderFactory.java:126)
at com.sun.jersey.core.spi.component.ProviderServices.getComponent(ProviderServices.java:168)
at com.sun.jersey.core.spi.component.ProviderServices.getProvidersAndServices(ProviderServices.java:120)
at com.sun.jersey.core.spi.factory.MessageBodyFactory.getProviderMap(MessageBodyFactory.java:136)
at com.sun.jersey.core.spi.factory.MessageBodyFactory.initReaders(MessageBodyFactory.java:110)
at com.sun.jersey.core.spi.factory.MessageBodyFactory.init(MessageBodyFactory.java:105)
at org.hybird.appengine.jersey.container.WebApplicationImpl.initiate(WebApplicationImpl.java:463)
at org.hybird.appengine.jersey.container.WebApplicationImpl.initiate(WebApplicationImpl.java:320)
at org.hybird.appengine.jersey.container.WebComponent.initiate(WebComponent.java:424)
at org.hybird.appengine.jersey.container.WebComponent.load(WebComponent.java:435)
at org.hybird.appengine.jersey.container.WebComponent.init(WebComponent.java:168)
at org.hybird.appengine.jersey.container.ServletContainer.init(ServletContainer.java:198)

By: lqd

lqd — Fri, 29 May 2009 11:10:56 +0000

Thanks for the comment Bruce, that’s nice to hear !

I’ve updated the article to specifiy it’s a modified Jersey 1.0.2. I’ll look at updating it for 1.1.0-ea as soon as i can.

By: Bruce

Bruce — Thu, 28 May 2009 14:40:05 +0000

Thanks for posting this article. I needed to deploy a simple RESTful web service example for my team to view (http://brucerestfulwsexample.appspot.com/) on Google AppEngine/Java.

Initially, I had a problem using your jersey-appengine-container_0.1.jar with my project. Apparently, your jar doesn’t work with the 1.1.0-ea version of the Jersey jars that I was using. I had to replace that version with 1.0.2 Jersey jar files and then your jersey-appengine-container_0.1.jar worked fine.

Bruce

By: lqd

lqd — Thu, 21 May 2009 07:27:10 +0000

No, not yet, i’ll see if i can do anything about that. But most likely it’s because of the classes that are unavailable in AppEngine.