tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wong Kok Wai <>
Subject Re: *Bad* stack trace.
Date Wed, 05 Jan 2000 01:40:03 GMT
I was the one who first reported the error. To solve the problem, I removed the
following from the JSP:

  ServletOutputStream tmp= response.getOutputStream();

and change all tmp.println to use <%= instead.

This is a common way of coding in JSP 0.92 but should be changed for JSP 1.1.
This may be cause of your problem too.

> >
> >1.  The exception couldn't get the message "serverResponse.writer.ise"
> >from  I don't like how StringManager just
> >changes the message to "cannot find message associated with key" as this
> >is a  very bad thing and you should probably throw a RuntimeException so
> >that you complain louder.
> >
> >2.  The exception is generated on the out.flush() from the generated
> >jsp.  Therefore I can't get this to work with my current Java library.
> >All other example .jsps work but not ours so I assume it is some of our
> >code that is manifesting this.
> >

View raw message