Re: DO NOT REPLY [Bug 13392] - When tag pooling is enabled, release() is not called on tag instances

[peter lin <pe...@labs.gte.com>]

I'm not sure what all the debate is over. Since you know for sure
doStartTag() will be called, couldn't your tag call .release() as the
first thing it does in doStartTag()?

Wouldn't that easily solve the problem? since the spec does cover the
issue as Jan pointed out, having doStartTag() call release() would be an
quick and easy fix.  maybe I'm just over simplifying the problem.

peter lin


bugzilla@apache.org wrote:
> 
> DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
> RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
> <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13392>.
> ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
> INSERTED IN THE BUG DATABASE.
> 
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13392
> 
> When tag pooling is enabled, release() is not called on tag instances
> 
> Juan.Oropeza@oracle.com changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>              Status|CLOSED                      |REOPENED
>          Resolution|INVALID                     |
> 
> ------- Additional Comments From Juan.Oropeza@oracle.com  2002-10-10 16:32 -------
> My preference is to have this fixed in the base release and to tell our
> customers that Tomcat works fine and that the tag pooling functionality works
> well with their applications without diabling this key feature. Why are you
> against such a practical change?
> 
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>