Thank you for your replies. I will have a look to Struts later, I think it is too late for this project. Furthermore, I got a solution to my problem, and the solution was to set the parameter enablePooling to false in my config file. But I still have a problem: 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? Or is there a way to do the same thing but with tomcat 4.0.x ?
Regards. Micka�l.
Nikola Milutinovic wrote:
You could use jstl instead, but from my experience SQL in the jsp is more trouble then it is worth and causes imense headaches
when you want to do something complicated. Just a suggestion but it could be a good time for you to have a look at migrating to Struts or some other framework which suits your needs :D
In other words, when JSP becomes too complex, it is time to transform your design into J2EE blueprint (which is endorsed by Struts). Each request can have three components handling it:
- incoming JSP: packaging of request parameters into beans, attaching them to request scope - main servlet: does all the work of "business logic" and attaches resulting beans/variables to request scope - outgoing JSP: performs "presentation logic", based on data supplied to it via request scope.
Nix.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
