JavaSercer Pages redirect com.ora.jsp.tags.generic.RedirectTag JSP Encodes the url attribute and possible param tags in the body and sets redirect headers. page true true … At the top of the TLD file, you find a standard XML declaration and a DOCTYPE declaration, specifying the Document Type Definition (DTD) for this file. A DTD defines the rules for how elements in an XML file must be used, such as the order of the elements, which elements are mandatory and which are optional, if an element can be included multiple times, etc. If you’re not familiar with XML, don’t worry about this. Just accept the fact that you need to copy the first two elements of Example 16.8 faithfully into your own TLD files. Regarding the order of the elements, just follow the same order as in Example 16.8. Whether an element is mandatory or optional is spelled out in the following descriptions of each element. After the two declarations, the first element in the TLD file must be the element. This is the main element for the TLD, enclosing all more specific elements that describe the library. Within the body of the element, you can specify elements that describe the library as such, as well as each individual tag handler. Let’s start with the five elements that describe the library itself. The element is mandatory and is used to specify the tag library version. The version should be specified as a series of numbers separated by dots. In other words, the normal conventions for software version numbers, such as 1.1 or 2.0.3, should be used. The element, specifying the version of the JSP specification that the library depends on, is optional. The default value is 1.1. The element is intended to be used by page authoring tools. It’s a mandatory element that should contain the default prefix for the action elements. In Example 16.8 the value is ora, meaning that an authoring tool by default generates custom action elements using the ora prefix, for instance . This element value can also be used by a tool as the value of the prefix attribute if it generates the taglib directive in the JSP page. The element value must not include whitespace or other special characters, or start with a digit or underscore. The element is also intended to benefit authoring tools. The value can be used as the default value for the uri attribute in a taglib directive. It’s an optional element, following the same character rules as the element. The last element that describes the library as such is the optional element. It can be used to provide a short description of the library, perhaps something a tool might display to help users decide if the library is what they are looking for. Besides the general elements, the TLD must include at least one element. The element contains other elements that describe different aspects of the custom action: , , , , , and . The element is mandatory and contains the unique name for the corresponding custom action element. The element, also mandatory, contains the fully qualified class name for the tag handler class. If the action introduces variables or needs to do additional syntax validation as described in the next section, the optional element is used to specify the fully qualified class name for the TagExtraInfo subclass. page 230
Note: If you are looking for cheap and inexpensive provider to host and run your tomcat application check professional tomcat hosting services
This entry was posted
on Saturday, January 20th, 2007 at 6:11 pm and is filed under Java.
You can follow any responses to this entry through the RSS 2.0 feed.
Responses are currently closed, but you can trackback from your own site.