struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 17613] - Problem with html:messages Tag and Tomcat Tag Pooling
Date Mon, 03 Mar 2003 19:57:21 GMT
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=17613>.
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=17613

Problem with html:messages Tag and Tomcat Tag Pooling





------- Additional Comments From Larry.Zappeterrini@sanchezprojects.com  2003-03-03 19:57
-------
Now you have prompted me to actually read the JSP specification ;-). My concern 
is that with tag pooling in place, one page may set an attribute on 
html:messages, say footer for example. I may have html:messages on another page 
that does not define the attribute footer. The JSP specification dictates that 
undeclared attributes should not be set, so setFooter is never called on the 
second page. So there is a particular instance of MessagesTag in the tag pool 
that has a value set for footer. If the tag that has no footer attribute 
specified happens to use that instance from the tag pool with footer set, it 
will erroneously have a value for footer. The specification recommends that any 
request scope values in the tag should be reset in the method doFinally. I have 
not actually tested this behavior to see if it performs improperly, but after 
examining the JSP specification I believe that it is highly likely.

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org


Mime
View raw message