Alright - I'm not entirely sure if anyone will find any use for this, but I
implemented the approach suggested by Lance (thank you Lance!) and pushed
the code into BitBucket : https://bitbucket.org/akochnev/tap5-gae-utils
The project wiki explains how to use it, but in short, just include the
modu
A much better option is to fix the bug with a RequestFilter. Wrap the
response in a custom implementation that sets a flag to true when
redirect() is called and returns the correct value in isComitted()
Just out of curiosity - this exception is thrown by Tapestry itself;
however, since it's just a "sanity check" and it only happens on the Dev
server , is there a way to disable this filter using Tapestry IoC ?
org.apache.tapestry5.internal.services.ImmediateActionRenderResponseF
ilter.handle(Immed
This is caused by this issue:
http://code.google.com/p/googleappengine/issues/detail?id=8201
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/T5-and-AppEngine-1-7-3-dev-server-IllegalStateException-tp5717683p5719841.html
Sent from the Tapestry - User mailing list archive a
Correction, this issue seems to have shown up w/ GAE 1.7.2 instead of 1.7.3
. Reverting the appengine sdk to version 1.7.1.1 resolves the issue whereas
staying w/ 1.7.2 does not.
Cheers - Alex K
On Mon, Nov 5, 2012 at 11:35 PM, Alex Kotchnev wrote:
> I was migrating an older application running
