The last time I checked, Jersey was working on appengine with small
modifications on classes that use the naming API. However the JAXB support
was not working. If you want to use other XML and/or JSON serializers and
deserializers that are supported by Appengine, but not Jersey, then you
might want to write your own MessageBodyWriter and MessageBodyReader classes
for those libraries. It is not so hard to do so.
If JSON is your choice of transport, then I highly recommend the GSON
library on
http://code.google.com/p/google-gson.
Erdinc
On Wed, Sep 23, 2009 at 4:02 PM, Paul Sandoz <Paul.Sandoz_at_sun.com> wrote:
>
> On Sep 18, 2009, at 6:46 AM, Mark Petrovic wrote:
>
> I noticed an intense thread on the subject of Jersey on GAE back in April:
>>
>>
>> https://jersey.dev.java.net/servlets/SearchList?list=users&searchText=app+engine&defaultField=subject&Search=Search
>>
>> Are people using Jersey on GAE to good effect these days, or are there
>> still issues?
>>
>
> The issues still remain in the releases and SNAPSHOTs.
>
>
> If there are issues, would those with experience be kind enough to chime
>> in with a comment or two?
>>
>>
> The issues are related to subset of the JDK classes (white list) that are
> supported by the GAE container.
>
> Jersey currently has a hard coded dependency on the Java naming API. I have
> not had the time to work around this.
>
> It looks like the white list has grown to include the StAX API but not the
> JAXB API. I ask a q. at JavaOne about the white list in relation to XML APIs
> and the response i got was it is primarily related to security. The
> implementation of the API is carefully audited for security issues.
>
> I am not sure why the Java naming API is not included.
>
> Paul.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>
>