without EL it works fine. I've tried with scriplet code and it works fine. I've tried it with the correct syntax and it works fine.
it's only when the syntax is incorrect that it doesn't throw an exception like "symbol cannot be resolved", "clascastexception" or some other exception. Right or wrong, I expect the EL to realize "duh, that's the wrong syntax silly pete. I'm throwing an exception." when I have time, I'll try to verify jstl 1.0.2 with 4.0.6 and see if has the same effect. If it doesn't cause continuous logging, it's probably a bug in tomcat. The funny thing is the page compiles just fine. peter Shawn Bayern wrote: > > On Fri, 18 Oct 2002, peter lin wrote: > > > 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. > > Again, I'm not sure of the specific action that you're saying causes this > looping. Is there something in the EL that you're saying causes a loop? > Is it the iteration over 'cookie'? Can you replicate it without using the > EL? > > Shawn > > -- > 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>
