Perhaps the in-memory store can make serialized copies of the state
upon storing it in there?
On 2/19/08, Carlos Pita [EMAIL PROTECTED] wrote:
Of course, I'm proposing this just for development environments that
use the reloading filter. Thanks for the remark, anyway. Perhaps I
should
You should be aware that you now disabled the serialization, which may
cause problems on your production environment if you don't pay
Of course, I'm proposing this just for development environments that
use the reloading filter. Thanks for the remark, anyway. Perhaps I
should have been clearer,
Something like this will do the trick:
class PickyHttpSessionStore extends HttpSessionStore {
public PickyHttpSessionStore(Application application) {
super(application);
}
@Override
public void setAttribute(Request request, String name, Object value)
You could throw an Error. Not very nice, but at least you'll notice.
Erik.
Carlos Pita wrote:
... That said, this will only show error log entries, because of the catch
in RequestCycle:
I would like to see an error page instead, errors of this kind end up
showing themselves as
Carlos Pita schrieb:
I would like to see an error page instead, errors of this kind end up
showing themselves as obscure page expiration issues that are hard to
trace if you don't know where to look.
+1 on this one!
-
To
