It causes tomcat 4.1.12 to generate logs continuously. If I don't hit
stop in the browser, it will continue to generate logs. After a couple
of minutes, the log is tens of megs.
I don't know if it's the responsibility of the EL to throw an exception
or if jasper should be responsible. with is why the subject says maybe
:)
if you think it's a jasper bug, I will consult tomcat-dev and
investigate further. thanks.
peter
Shawn Bayern wrote:
>
> On Thu, 17 Oct 2002, peter lin wrote:
>
> > It looks like using <c:out value="${acookie.name}"/> won't retrieve
> > the value, since acookie is a hashentry, it can't do
> > acookie.getName().toString(). I'm guessing that is correct
> > functionality right?
>
> Right, for ${cookie} is a Map of all cookie names to Cookie instances.
>
> So, in the context of the test page, where does the bug come up?
>
> --
> Shawn Bayern
> "JSTL in Action" http://www.jstlbook.com
>
> --
> To unsubscribe, e-mail: <mailto:taglibs-user-unsubscribe@;jakarta.apache.org>
> For additional commands, e-mail: <mailto:taglibs-user-help@;jakarta.apache.org>
--
To unsubscribe, e-mail: <mailto:taglibs-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:taglibs-user-help@;jakarta.apache.org>
