tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 16830] - Jasper do not reset BodyContent for tags with BodySupport and empty content
Date Wed, 24 Mar 2004 08:23:57 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=16830>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=16830

Jasper do not reset BodyContent for tags with BodySupport and empty content





------- Additional Comments From issa.gorissen@axa.be  2004-03-24 08:23 -------
Thx Kin-Man! Your comments are greatly appreciated.

Anyway, you're right that the spec does not explicitly tell what should the 
container do and what the tag developer must expect from the container when tag 
pooling is in place. Isn't it better to push the JSP leads to clarify this, 
instead of making assumptions for implicit mechanism?

And the spec is rather thin on the explanation of the INIT PROTOCOL (what are 
those AttSet? What the container must do after doEndTag?).

BTW, is there any really good explanation of the life cycle of a BodyTag with a 
tag pooling container on the Net somewhere?

I guess a backdoor for tag developers is to use the TryCatchFinally 
fonctionnality to reset the bodycontent, right?

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


Mime
View raw message