RESTful app on Google App Engine Java?

Question

I would like to create a RESTful application in the Google App Engine. I would like to provide XML and JSON services. I experimented briefly with Restlet, Resteasy, and Jersey. I have not had much success with any of them, except for some simple examples in Restlet.

Could you share your impressions with creating a Restful web-application in Google App Engine using Java or give an idea of ​​the above mentioned tools in GAE?

Thank!

Edit (2009-07-25):

I decided to use Restlet. It seems to work flawlessly. Please post any other opinions / opinions you may have. What problems have you encountered? Have you successfully used Jersey / Restlet / Resteasy on GAE / J? If so, we want to hear about it!

Answer 1

I am pleased to announce that the Restlet M3 runs FREE on AppEngine 1.2.2. I followed the First Steps and First Resource tutorials http://restlet.com/technical-resources/restlet-framework/guide .

So, it seems to me that Restlet is the answer to your GAE / J Restful apps.

Answer 2

I use jersey on gae. Here is a link for those interested in customizing: (I am using the GAE SDK v1.4.0):

http://tugdualgrall.blogspot.com/2010/02/create-and-deploy-jax-rs-rest-service.html

Answer 3

I will also begin to study this, but have not yet begun. I found this structure, which says that it should work, but, as I said, have not tried it yet.

http://wiki.restlet.org/docs_1.2/13-restlet/275-restlet/252-restlet.html

If you earn or receive one of the above recommendations, update everyone, as I am sure that there is interest in this.

Answer 4

I use Restlet with Guice in Google AppEngine. IMHO they are perfectly combined. See my recent blog post for more details: http://haraldpehl.blogspot.com/2009/11/google-appengine-restlet.html

Answer 5

Ok, I would really advise you to take a look at the play framework

Watch the video on the main page

It has a gae module

With siena as orm for processing gae datastore

Of all the java structures I've seen so far, I think it has an easier learning curve,

• great documentation ,

• a tutorial to develop a complete application

• a very active and helpful community,

• free in beer as well as in speech

• highly scalable because of this box-free design

• friendly relations

• configured using modules and plugin approaches

more, taking this into account for a college course, it’s very easy to crack the code, I could handle a couple of tickets and new functions without any experience with java, just a couple of years of developing web applications with php

other benefits

• it’s very easy to start, there is no complicated setup, just download and unzip the file and you are ready

• Excellent development experience, just fix the code and click "Update", "Play automatic compilation" on the go when working in development mode.

• quick and easy

• fullstack, you don’t need to integrate bulky frameworks to make it work.

• Big error report, no more endless tracing of the error stack, just shows you the error line

• no xml configuration anywhere

• excellent tdd support with integrated selenium test

I think the main advantage as a learning tool is that it can look into the source code without feeling lost, and community support ... The documentation is very understandable and you can learn a lot just by looking in the source code ...

Answer 6

Since these valiant old solutions were fixed together, Google apparently provided an Eclipse plug-in for creating a starter project that creates an App Engine application, Android APK and web application, all talking to each other over an interface defined by a single set of annotated object declarations .

I have not tried this myself, but look before you try any more heterogeneous examples described in previous posts above:

https://developers.google.com/eclipse/docs/appengine_connected_android

This Google video is also quite informative:

http://www.youtube.com/watch?v=NU_wNR_UUn4

Answer 7

For what it's worth, there was quite a bit of discussion on Jersey user lists on how to get Jersey to work on GAE. This is a tedious job due to GAE limitations (missing whitelisted classes, which I hope have been resolved over time), but apparently you can get it to work. Therefore, although it is not so simple, it may be your best choice; especially since many of the problems encountered are the same for all frameworks (introduced by GAE).

Answer 8

I recently put together a project template with Jersey, Guice, and AppEngine on GitHub. It was developed using SimpleDS, but it can be modified to easily work with Objectify / JDO. The project is in real time here .

This should be a good starting point for new projects.

Answer 9

Here is a very good Restlet / Android / GAE / Objectify tutorial with a simple application example. Sorry, this is in French, but you can just copy / paste the code or use Google Traduction.

I followed him and had a working Android / GAE server communicating together after 2 hours. This is a good base to run or test Restlet.

http://www.tutos-android.com/webservice-rest-android-appengine-restlet-objectify

Luck

Answer 10

The two most cumbersome actions of the GAE REST API to work, whether Java or .py, are graphics and how not to display personal information. My little gae rest feed forked is another project . I'm sure Java will succeed in being stuck because of Java solutions and giving more features (advantages) as well as longer (slower) time to succeed (disadvantage), while python projects open up less ways to succeed (unprofitable) and less development time (profitable rapid development) to succeed.