Hi Vineet,
If you create an issue and add the changes as a patch (attachment) the
1 or 2 classes that would be useful to help identify the areas and so
we do not forget about this.
Thanks,
Paul.
On Sep 24, 2009, at 8:38 AM, Vineet Sinha wrote:
> We have deployed an app built using Jersey and deployed on GAE (we
> ported a Ruby/Rails apps to Java/Jersey+JPA). Issues that we have
> found with regards to it interacting with Jersey:
>
> I added a set of 8 Java classes in the class path before the Jersey
> jars and it works fine. These 8 classes are basically null
> implementations of the Jaxb and the naming dependency. Of the 8
> classes, only 1 or 2 were needed to get Jersey working - I brought
> the rest of the changes to remove the onload exceptions that were
> being logged otherwise as it could potentially hide bugs in our
> apps. These changes were made to work with v1.1.1 - I have not
> tested them with v1.1.2 though it is likely that it will work.
>
> I haven't had the time to dig into the details for the best places
> to make the changes - which is why I haven't posted details here
> regarding them, but I can send the changes out to anyone. Just e-
> mail me.
>
> The only capability that we tried which doesn't work on the GAE
> servers is the @PerSession annotation. This is likely because of the
> way that GAE writes session information to their cache.
>
> Vineet
>
>
> On Thu, Sep 24, 2009 at 1:31 AM, Charlie Knudsen <charlie.knudsen_at_gmail.com
> > wrote:
> On Wed, Sep 23, 2009 at 11:19 AM, Erdinc Yilmazel
> <erdinc_at_yilmazel.com> wrote:
> > 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
> ...
>
> This is great to hear. Is there any further code, documentation, or
> guidance that you would recommend that might help out with this
> effort? I found the post at:
> http://lqd.hybird.org/journal/?p=123
>
> but from the comments it looks like that is not working with newer
> Jersey releases. That said if others are having success with minor
> hacks getting things I think I will give it a shot. I was going to
> dive in previously but was put off by the fact that the code failed
> when deployed but worked fine locally.
>
> Thanks,
>
> Charlie
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>
>