You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@struts.apache.org by bu...@apache.org on 2002/01/08 00:05:50 UTC

DO NOT REPLY [Bug 5726] - Reusing instance of FormTag class in Resin

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=5726>.
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=5726

Reusing instance of FormTag class in Resin

arron@keyboardmonkey.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From arron@keyboardmonkey.com  2002-01-07 15:05 -------
This is as per the JSP spec.
If you read the javadoc for javax.servlet.jsp.tagext.Tag you will see this in
place. The change to struts in the worst case would be to make the fields mandatory.

You already have the solution (specify the names each time), and it is according
to the spec. The reason the spec does this is so containers can optimise their
run-time by not creating so many tag objects. And you can see why. Resin is an
efficient container in this respect and only builds tags for those which
absolutely require it, otherwise it reuses tags to save energy.

Resin's a good JSP container and it's a good spec. This is just a minor
side-affect of using both.

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