I've looked at the request/response traffic and nothing looks unusual.
In fact the JSONObject that is passed to
JSONObjectEventResultProcessor.processResultValue(JSONObject value)
looks perfectly fine.
We do have a custom filter, which enables tapestry injection in
non-tapestry 5 environments, (i.e JSP and tapestry 4 pages)
It's a bit of an ugly hack too, but we have not been able to find any
alternatives.
The main module contains this:
public static void contributeHttpServletRequestHandler(
OrderedConfiguration<HttpServletRequestFilter> configuration) {
configuration.addInstance("StoreRequestResponseIntoGlobals",
StoreRequestGlobalsFilter.class, "before:*");
}
Here is the filter code.
It's purpose is to provide request/response objects for legacy Tapestry 4
pages and JSPs.
Note that we are using the constructors for Request and Response objects.
If we try to inject these we get a StackOverflowException.
public class StoreRequestGlobalsFilter implements HttpServletRequestFilter {
...
@Override
public boolean service(HttpServletRequest servletRequest,
HttpServletResponse servletResponse,
HttpServletRequestHandler handler) throws
IOException {
Request request =
new RequestImpl(
servletRequest,
applicationCharset,
sessionFactory);
Response response = new ResponseImpl(servletRequest, servletResponse);
requestGlobals.storeRequestResponse(request, response);
return handler.service(servletRequest, servletResponse);
}
}
On Sat, Feb 22, 2014 at 2:14 AM, Lance Java <lance.j...@googlemail.com>wrote:
> Strange, do you have any custom request filters running? Any custom
> threads?
>
> Failing that, can you use the dev tools in your browser to inspect the
> requests / response traffic? Anything strange?
>
