Hi Kalle, I have tapestry-security 0.6.0 working successfully in GAE with tapestry5.4 beta 22. My problem was due to an oversight in my code which was quasi-impossible to isolate from just looking at GAE logs. Finally broke down and got the app running locally in a debugger today and fixed my problem. Thanks for your kind offer of help. Apologies for the false alarm.
On Sun, Sep 14, 2014 at 9:37 PM, Kalle Korhonen <kalle.o.korho...@gmail.com> wrote: > Do you have a stack trace? And you are sure you are just not deploying a > servlet api with you war? In the simplest (to correct) case we are using > some 3.0 features but off-hand I don't remember any and they are relatively > easily to code around. 3.0 api is already 5 years old but it might be worth > supporting it. Another possibility, and I seem to recall a related issue > was reported on Shiro lists, is that you can't spawn threads in GAE which > is why scheduledExecutors and things like that are not white listed. If you > can isolate the problem further and dig up the reason for the failure, I'll > be happy to assist getting tapestry-security running on GAE. > > Kalle > > On Sun, Sep 14, 2014 at 3:28 PM, Jon Williams <williams.jonat...@gmail.com > > wrote: > >> Hi Kalle, (& y'all) >> >> I see your tapestry-security 0.6.0 has a dependency on the v3.0 servlet >> spec. >> I know 0.5.1 had it too, because I have an app running with it in a v3 >> servlet container that works fine and dandy. >> >> I am trying to work tapestry-security 0.6.0 into another app that's in >> production on GAE. Sadly GAE is perpetually stuck on servlet spec 2.5, it >> seems there is no positive news on that changing to v3 anytime soon... ( >> https://code.google.com/p/googleappengine/issues/detail?id=3091) >> >> What I'm seeing is tapestry-security 0.6.0 not working in GAE. >> My hunch is it's most probably because it's not a v3 API servlet >> container. >> What do you say? Is this about what you'd expect given my servlet api >> impedance? >> >> Thanks >> Jon >> >> > >
