DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13499>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13499 Jasper throws an exception on an immediate pageContext.forward() [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Minor |Major ------- Additional Comments From [EMAIL PROTECTED] 2002-10-10 16:01 ------- Sure. Like I said, the exception makes semantic sense. But there's nothing in the spec, that I see, that implies this *should* be illegal. If it *is* illegal by spec, I'm more than willing to fix my code. For the record, I *do* use a buffer. But I set it on the servlet level, in a base class that all my JSPs extend. A quick reading of your comment implies that the spec has no problem with this, but the current implementation of Jasper 2 can't handle this (entirely legal) case. As I said, I'm more than happy to fix my code if it's wrong, but it's a little annoying to change upwards of 900 JSPs if it's something that Jasper can, and should, be fixed to handle. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
