TAP5-986 & Jetty error dispatches

[Kalle Korhonen <ka...@gmail.com>]

Originally brought up on Tynamo user list, some users & committers
have complained about seeing null pointer exceptions when using
servlet standard error pages. I decided to track it down as we've seen
the same in our functional tests. I explained the issue in detail at
https://issues.apache.org/jira/browse/TAP5-986 but at least Jetty 7
simply starts handling the error request in the same thread that was
assigned for the original request. I can make a simple fix for
TAP5-986 but the issue brings up a larger point of whether T5 should
better consider multiple container dispatches (e.g. REQUEST, ERROR)
being handled by the same thread. I kind of feel that's a container
issue as the container isn't providing proper request isolation in
that case but I'm not sure if the servlet spec says anything about it.

Kalle

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org