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 [EMAIL PROTECTED] 2004-03-24 08:44 ------- Thanks for the lengthy explanation! Unfortunately there is some degree of freedom as to the correct interpretation of the spec. If you consider the spec in absence of tag pooling then it is clear, that the body content of a tag that has no body remains unchanged. Typically this will be 'null' since tag implementors usually won't initialize this to something else (they would have to implement BodyContent for this sole purpose). Now, tag pooling is supposed to *not* change the semantics of a JSP. In this case not invoking setBodyContent(null) would better meet this requirement than not doing it. The only solution I can see that is both conformant to the spec and working would be to request of each tag implementor that he/she resets bodyContent to 'null' in doEndTag(). I am just not sure whether that is possible/desired in all situations. Maybe there are cases where one wants access to the body content even after doEndTag() - maybe for the doEndTag() method of an enclosing tag. We'll probably need another life cycle event in interface Tag that is invoked when an instance returns to a pool. (release() is invoked when the tag is completely discarded). That would be the best solution IMHO. Thanks for listening! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
