On Oct 13, 2009, at 12:18 PM, Dinesh Narayanan wrote:
> I am wondering if the "out.flush()" is causing WebSphere to think
> the response has been committed?
>
> [Dinesh] I was getting the same error even if I was commented
> out.flush(). The error occurs when the following statement is
> executed in JSPTemplateProcessor.writeTo(...) method
> d.forward(requestInvoker.get(), responseInvoker.get());
>
>
Then i cannot explain why this would occur.
Just to be sure did you verify that your version of
JSPTemplateProcessor was being invoked?
If so i cannot explain the behavior. Jersey is not really doing
anything terribly complicated w.r.t. the servlet API. Just forwarding
the request. My only guess is WebSphere does not like this type of
thing to occur in a filter. It should be easy to verify if this is the
case with a simple web app using filters.
Paul.