Its poor practise to have a sql: jstl tag in production ready code.
> How do you deal with this when using pure JSTL sql calls using a
> connection? How does JSTL sql library release the connection at the
> end of a page to ensure that connections don't get leaked?
For reasons exactly like th
I would consider integrating this as part of your application and stay just
standalone tomcat (or load balanced tomcat). Keep it simple.
http://www.opensymphony.com/oscache/
Very useful.
__
This email has been scanned for all viruses by the MessageLabs SkyScan
service
