However, I still have one question: we followed the steps in the following page: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jasper-howto.html to pre-compile all the JSP files using ant before deploying our web application, in this case do you know how I can set the enablePooling to false in order to compile the files correctly?
Thank you for your help. Greetings,
Micka�l.
Glenn Nielsen wrote:
Tomcat 4.1 introduced JSP custom tag pooling in the JSP engine. JSP custom tag pooling can improve performance of JSP a great deal but the downside is that it can break older JSP tag libraries which may have bugs when used this way. This may be what you are seeing with DbTags.
You can disable JSP custom tag pooling by setting the JspSservlet init parameter enablePooling to false in your tomcat conf/web.xml.
Regards,
Glenn
Mickael Cappozzo wrote:
Hello Martin,
I read your problem, we experienced this behaviour also during the testing to understand if I was doing something wrong or not...
We checked also the taglibs sources and we didn't find any answers :-(
However, we used the same dbtags before under tomcat 4.0 and it worked, but with tomcat 4.1 it doesn't, this is also strange...
Greetings,
Micka�l.
Martin van Dijken wrote:
Hey Mickael,
I just noticed the exact same thing under totally different circumstances. I posted about it and haven't heard from anybody. Has nobody else had this?
I checked the Jakarta-taglibs cvs and it seems the sql:resultset tag is doing everything correctly, although we both know it's not.
I've created a new bug in bugzilla and put yours and my message there.
check: http://issues.apache.org/bugzilla/show_bug.cgi?id=22927
Greetings,
Martin van Dijken
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
