> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, March 06, 2001 3:24 PM
> To: [EMAIL PROTECTED]
> Subject: RE: HTTP Status Codes and Error Pages
>
>
> > Costin - were you going to make the changes
> > (out.flush() -> out.flushBuffers()) in
> > JspParseEventListener.generateFooter() and
> > PageContextImpl.include() that we had discussed? I
> > had thought that you implied you were going to do it
> > (that was before I was a committer) but I just noticed
> > that the out.flush() calls are still the same as
> > before.
>
> Well, 2 things happened - first I had to do the changes in
> jasper ( i.e. jasper-runtime ), and make it available in
> lib/common ( so I can cast JspWriter to JspWriterImpl -
> jasper.jar is not visible to serlvets/jsps )
>
> Second, we are waiting ( Larry ? ) for a clarification,
> to decide which is the best solution.
I am in favor of including the "flushBuffer" fix in
Tomcat 3.3 Milestone 2. The JSP 1.1 and 1.2 specs don't
address differences in JSP buffer handling between
when the JSP is included and when it's not, at least not
that I could find. Since Tomcat 4.0 uses flushBuffer for
included pages, I think it would be good make Tomcat 3.3's
behavior consistent with this.
Larry
>
> The fix is trivial now - I tried on my machine and
> seemed to work fine ( i.e. pass the test suite ).
>
> Costin
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
