https://bz.apache.org/bugzilla/show_bug.cgi?id=60497
--- Comment #3 from Wai-Kau Lo <w...@destinysolutions.com> --- Page 2-54 of the JavaServer Pages Specification version 2.0 describes the lifecycle of a JSP tag instance using a state transition diagram, which I have uploaded to this bug as an attachment (named JSP Tag Lifecycle Diagram) for ease of reference. The state transitions are described as follows: •[1] This transition is intended to be for releasing long-term data. no guarantees are assumed on whether any properties have been retained or not. •[2] This transition happens if and only if the tag ends normally without raising an exception •[3] Some setters may be called again before a tag handler is reused. For instance, setParent() is called if it’s reused within the same page but at a different level, setPageContext() is called if it’s used in another page, and attribute setters are called if the values differ or are expressed as request-time attribute values. Label [2] corresponds to the state transition caused by the execution of the doEndTag method, after the doStartTag method is execution. This implies that the doEndTag method should not be executed if the doStartTag method execution raises an exception. Since the doEndTag method is not executed, the tag instance will not be in a proper state for the next execution of the doStartTag, implying that we should never reuse the tag instance if the doStartTag method raises an exception during its execution. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
