Tim Moore wrote:
[...] I thought the benefit of Tag.release and pooling was that I could create a tag that does something expensive at init time (acquire a DB connection, read a file, whatever) and reuse those resources until released. Maybe that's a bad practice? But then what's the advantage of having release called only once before GC?
Yes, that was the idea, and since the "classic" API is still part of JSP 2.0, you can use it for this type of tag handler if you need it. Most tag handler's don't need it though (you can often cache the expensive objects elsewhere, such as in the application or session scope). So for the majority of case, the SimpleTag API will be the best fit.
Hans -- Hans Bergsten <[EMAIL PROTECTED]> Gefion Software <http://www.gefionsoftware.com/> Author of O'Reilly's "JavaServer Pages", covering JSP 1.2 and JSTL 1.0 Details at <http://TheJSPBook.com/> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
