Jsp tag context



Keywords: jsp tag context
Description: The interface of a classic tag handler that does not want to manipulate its body. The Tag interface defines the basic protocol between a Tag handler and JSP page implementation class. It defines the

The interface of a classic tag handler that does not want to manipulate its body. The Tag interface defines the basic protocol between a Tag handler and JSP page implementation class. It defines the life cycle and the methods to be invoked at start and end tag.

The Tag interface specifies the setter and getter methods for the core pageContext and parent properties.

The JSP page implementation object invokes setPageContext and setParent, in that order, before invoking doStartTag() or doEndTag().

There are two main actions: doStartTag and doEndTag. Once all appropriate properties have been initialized, the doStartTag and doEndTag methods can be invoked on the tag handler. Between these invocations, the tag handler is assumed to hold a state that must be preserved. After the doEndTag invocation, the tag handler is available for further invocations (and it is expected to have retained its properties).

Lifecycle details are described by the transition diagram below, with the following comments:
  • [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.
  • Check the TryCatchFinally interface for additional details related to exception handling and resource management.

Once all invocations on the tag handler are completed, the release method is invoked on it. Once a release method is invoked all properties, including parent and pageContext, are assumed to have been reset to an unspecified value. The page compiler guarantees that release() will be invoked on the Tag handler before the handler is released to the GC.

If the TagLibraryDescriptor file indicates that the action must always have an empty action, by an <body-content> entry of "empty", then the doStartTag() method must return SKIP_BODY.






Photogallery Jsp tag context:


New and Notable Features within BIRT 2.2


Customize your WCM Authoring Template with JSP - IBM Web Content ...


Manual programacion - java - jsp &amp; xml


servlets - ServletConfig vs ServletContext - Stack Overflow


MyEclipse Web Projects - Genuitec


Implementing Additional Functions in the UI Shell - 11g Release 5 ...


Client Context in Detail - docs.adobe.com


Chapter 8 Custom Tags in JSP Pages (The Java EE 5 Tutorial)


Developing Portlets


Getting Started Guide


Components - docs.adobe.com


Getting Started Guide


Sharing Liferay Service Layer between two plugin portlet contexts ...


database - Large server-side data: JSON vs XML vs JSTL EL - Stack ...


org.apache.struts.taglib.bean (Struts Taglibs 1.3.0-dev API)


IBM How to configure AppScan Source Eclipse Developer plugins to ...


IBM How to configure AppScan Source Eclipse Developer plugins to ...


New and Notable Features within BIRT 2.2


Eclipse Web Tools Platform Project Wiki: Objectweb Contributions