JRun Response Wrappers and Filters

[B. David Coles]

Using JRun4, attempting to wrap the response in a filter and modify it after Struts Action is done processing.

Response comes back to my filter, I can sys-out the wrapper it and see the HTML generated by the JSP Struts called.

In Tomcat4, the JSP loads into the browser as expected.

In JRun4 (using Updater 4), a blank screen is placed in the browser.

Using debugging through Eclipse, I can see that the blank page is returned to the browser before the filter is done with it's magic after the doFilter call.

I've been able to ascertain the following:

In the Action, the Response used by the execute method IS my wrapper

JRun is not calling flushBuffer() on the response, where Tomcat is doing so

Taking a WILD stab, I'd say that it's the RequestDispatcher implementation in JRun that is not taking care of this.

Anybody else having this problem or know of a solution??

Thanks a ton!

[Mike Curwen]

I've heard of something quite like this, but it's apparently fixed ...

http://jira.opensymphony.com/browse/SIM-42

Maybe you can chase down the JRun bug mentioned in this report, and take it up with the JRun folks if you can prove it's still broken.