It's actually the JSP that needs to be aware of the tapestry requests. We are injecting tapestry 5 services that have dependencies on the tapestry 5 request into the JSP or tapestry 4 pages. Without this code it breaks.
Also we are calling cleanupThread(). I've tried storeServletRequestResponse but it doesn't seem to make any difference whether it's called or not. On Mon, Feb 24, 2014 at 4:05 PM, Lance Java <lance.j...@googlemail.com>wrote: > Hmm... This could well be the source of your problem. I think you'll also > need to call ResponseGlobals. storeServletRequestResponse(...) > > I'm not sure I fully understand your non-tapestry flow. Why do you need > Tapestry to be aware of the JSP requests? > > I'm assuming you have contributed to the ignore paths filter so that > Tapestry ignores your JSP URL's? >
