## Jakarta Server Pages - 2.1
Specification Assertion Detail

Totals | Total | Active | Deprecated | Removed
# of Assertions | 986 | 960 | 9 | 17
# of Required Assertions | 982 | 956 | 9 | 17
# of Optional Assertions | 4 | 4 | 0 | 0

ID | Chapter | Section | Description | Required | Dependency | Implementation Specific | Defined by | Status | Testable
JSP:SPEC:271 | 0 | N/A | When used as a tag attribute value, the #{expr} syntax is evaluated by the container only if the the jsp-version element specified in the TLD has the value 2.1 or higher. If the version specified is less than 2.1, then the {expr} syntax is simply processed as a String literal. [EvaluationOf#{expr}] | true |  | false | technology | active | true
JSP:SPEC:272 | 0 | N/A | When used in template text, the #{ character sequence triggers a translation error, unless specifically allowed through a configuration setup. [TemplateTextPoundTranslationError] | true |  | false | technology | active | true
JSP:SPEC:273 | 0 | N/A | The #{ character sequence triggers a translation error if used for a tag attribute of a tag library where the jsp-version is greater than or equal to 2.1, and for which the attribute is not marked as a deferred expression in the TLD. [TagLibraryPoundTranslationError] | true |  | false | technology | active | true
JSP:SPEC:1 | 1 | 3.6 | It is illegal JSP syntax, which must result in a translation error, to use both an XML element attribute and a <jsp:attribute> standard action to pass the value of the same attribute. | true |  | false | technology | active | true
JSP:SPEC:2 | 1 | 3.6 | A translation error will result if the custom action invocation has <jsp:attribute> elements but does not define the body using a <jsp:body> element. | true |  | false | technology | active | true
JSP:SPEC:3 | 1 | 3.8 | White space within the body text of a document is not significant, but is preserved. | true |  | false | technology | active | true
JSP:SPEC:4 | 1 | 4.1 | Fatal translation failures shall result in the failure of subsequent client requests for the translation target with the appropriate error specification: For HTTP protocols the error status code 500 (Server Error) is returned. | true |  | false | technology | active | false
JSP:SPEC:261 | 1 | 4.3 | A JSP container must detect if a JSP error page is self-referencing and throw a translation error. [SelfReferencingErrorPage] | true |  | false | technology | active | true
JSP:SPEC:5 | 1 | 5.1 | HTML comments present within a particular translation unit are treated as uninterpreted template text by the JSP container. | true |  | false | technology | active | true
JSP:SPEC:6 | 1 | 5.1 | The body content of a JSP comment is ignored completely. | true |  | false | technology | active | true
JSP:SPEC:262 | 1 | 5.2 | The body of the content of a comment in an XML document is ignored completely. [CommentsDocumentsXml] | true |  | false | technology | active | true
JSP:SPEC:263 | 1 | 5.2 | Comments in JSP documents do not nest. [CommentsDocumentsNotNest] | true |  | false | technology | active | true
JSP:SPEC:264 | 1 | 6 | There is no special quoting mechanism within EL expressions; use a literal ?${? if the literal ${ is desired and expressions are enabled for the page (similarly, use a literal ?#{? if the literal #{ is desired). [QuotingWithinElExpressions] | true |  | false | technology | active | true
JSP:SPEC:7 | 1 | 6 | For JSP's in standard syntax, a literal %> is quoted by %\>, a literal <% is quoted by <\%, a single quote (') is quotes as \', a double quite (") is quoted as \", a backslash (\) is quoted as \\, additionally, the entities \' and \" are available to describe single and double quotes. | true |  | false | technology | active | true
JSP:SPEC:265 | 1 | 6 | Only when the EL is enabled for a page, a literal $ can be quoted by \$, and a literal # can be quoted by \#. [QuotingELSymbolsInTemplateText] | true |  | false | technology | active | true
JSP:SPEC:266 | 1 | 6 | Only when the EL is enabled for a page, a literal $ can be quoted by \$, and a literal # can be quoted by \#. [QuotingELSymbolsInAttributes] | true |  | false | technology | active | true
JSP:SPEC:8 | 1 | 8.2 | Objects with page scope are accessible only within the target page they are created. All references to such an object shall be released after the response is sent back to the client from the JSP page or the request is forwareded somwhere else. References to objects with page scope are stored in the 'pageContext' object. | true |  | false | technology | active | true
JSP:SPEC:9 | 1 | 8.2 | Objects with request scope are accessible from pages processing the same request where they were created. References to the object shall be released after the request is processed. In particular, if the request is forwarded to a resource in the same runtime, the object is still reachable. References to objects with request scope are stored in the 'request' object. | true |  | false | technology | active | true
JSP:SPEC:10 | 1 | 8.2 | Objects with session scope are accessible from pages processing requests that in the same session as the one in which they were created. It is not legal to define an object with session scope from within a page that is not session-aware. All references to the object shall be released after the associated session ends. References to objects with session scope are stored in the 'session' object associated with the page activation. | true |  | false | technology | active | true
JSP:SPEC:11 | 1 | 8.2 | Objects with application scope are accessible from pages processing requests that are in the same application as the one in which they were created. Objects with application scope can be defined (and reached) from pages that are not session-aware. References to objects with application scope are stored in the 'application' object associated with a page activation. The 'application' object is the servlet context obtained from the servlet configuration object. All references to the object shall be released when the runtime environment reclaims the ServletContext. | true |  | false | technology | active | true
JSP:SPEC:12 | 1 | 8.3 | The 'request' implicit object is an instance of jakarta.servlet.ServletRequest; if the protocol used is HTTP, then the request object is an instance of jakarta.servlet.http.HttpServletRequest (request scope). | true |  | false | technology | active | true
JSP:SPEC:13 | 1 | 8.3 | The 'response' implicit object is an instance of jakarta.servlet.ServletResponse; if the protocol used is HTTP, then the response object is an instance of jakarta.servlet.http.HttpServletResponse (page scope) | true |  | false | technology | active | true
JSP:SPEC:14 | 1 | 8.3 | The 'pageContext' implicit object is an instance of jakarta.servlet.jsp.PageContext (page scope). | true |  | false | technology | active | true
JSP:SPEC:15 | 1 | 8.3 | The 'session' implicit object is an instance of jakarta.servlet.http.HttpSession and is only valid for HTTP protocols (session scope). | true |  | false | technology | active | true
JSP:SPEC:16 | 1 | 8.3 | The 'application' implicit object is an instance of jakarta.servlet.ServletContext (same object as that returned from getServletConfig().getContext(); application scope). | true |  | false | technology | active | true
JSP:SPEC:17 | 1 | 8.3 | The 'exception' implicit object is an instance of java.lang.Throwable (page scope) and is only available in errro pages. | true |  | false | technology | active | true
JSP:SPEC:18 | 1 | 10 | White space may or may not be present after '<@%' and before '%>' within JSP directives. | true |  | false | technology | active | true
JSP:SPEC:19 | 1 | 10 | Directives do not produce any output into the current 'out' stream. | true |  | false | technology | active | true
JSP:SPEC:20 | 1 | 10.1 | The page directive can appear multiple times, and is position independent within a given translation unit. | true |  | false | technology | active | true
JSP:SPEC:21 | 1 | 10.1 | A translation error will occur if the page directive defines duplicate attribute/values within a given translation unit, unless the values for the duplicate attributes are identical for all occurrences. The import and pageEncoding attributes are exempt from this rule and can appear multiple times. | true |  | false | technology | active | true
JSP:SPEC:22 | 1 | 10.1 | The 'isScriptingEnabled' attribute of the page directive, if true, allows the presence of scripting elements (scriptlets, expressions, declarations) within a given translation unit. | true |  | false | technology | deprecated | true
JSP:SPEC:23 | 1 | 10.1 | The 'isScriptingEnabled' attribute of the page directive, if false, disallows the presence of scripting elements (scriptlets, expressions, declarations) within a given translation unit and will generate a translation error if they are present. | true |  | false | technology | deprecated | true
JSP:SPEC:24 | 1 | 10.1 | The default value for 'isScriptingEnabled' of the page directive, if not specified, is true. | true |  | false | technology | deprecated | true
JSP:SPEC:25 | 1 | 10.1 | The 'isELEnabled' attribute of the page directive, if true, directs the container to evaluate EL expressions. | true |  | false | technology | deprecated | true
JSP:SPEC:26 | 1 | 10.1 | The 'isELEnabled' attribute of the page directive , if false, will result in EL expressions not being evaluated by the container. | true |  | false | technology | deprecated | true
JSP:SPEC:27 | 1 | 10.1 | If the JSP is part of a Web application that is using a Servlet 2.3 deployment descriptor, the default value for the 'isELEnabled' attribute of the page directive is false. | true |  | false | technology | deprecated | true
JSP:SPEC:28 | 1 | 10.1 | If the JSP is part of a Web application that is using a Servlet 2.4 deployment descriptor, the default value for the 'isELEnabled' attribute of the page directive is true. | true |  | false | technology | deprecated | true
JSP:SPEC:29 | 1 | 10.1 | All scripting languages, specifiable by the page directive's 'language' attribute, must provide some implicit objects that a JSP page author can use in declarations, scriptlets, and expressions (see Section JSP.1.3.8 for list of available implicit objects) | true |  | true | technology | active | false
JSP:SPEC:30 | 1 | 10.1 | All scripting languages, specifiable by the page directive's 'language' attribute, must expose the Java technology object model to the script environment, especially implicit variables, JavaBeans components properties, and public methods. | true |  | true | technology | active | false
JSP:SPEC:31 | 1 | 10.1 | It is a fatal translation error for a page directive with a non-"java" language attribute to appear after the first scripting has been encountered. | true |  | false | technology | active | true
JSP:SPEC:32 | 1 | 10.1 | The only required scripting language value for the 'language' attribute is "java". | true |  | false | technology | active | true
JSP:SPEC:33 | 1 | 10.1 | The 'extends' attribute of the page directive specifies a fully qualified Java programming language class name, that names the superclass of the class to which this JSP page is transformed | true |  | false | technology | active | true
JSP:SPEC:34 | 1 | 10.1 | The 'import' attribute of the page directive specifies the fully qualified Java programming language type name denoting a particular type, or of a package name following by the ".*" string, denoting all the public types declared in that package, that shall be imported by the translated JSP page implementation and is thus available to the scripting language. | true |  | false | technology | active | true
JSP:SPEC:35 | 1 | 10.1 | Packages java.lang.*, jakarta.servlet.*, jakarta.servlet.jsp.*, jakarta.servlet.http.* are imported implicitly by the JSP container. [DefaultImports] | true |  | false | technology | active | true
JSP:SPEC:267 |  |  | No packages other than java.lang.*, jakarta.servlet.*, jakarta.servlet.jsp.*, jakarta.servlet.http.* may be implicitly imported. [NoOtherPackagesImplicitlyImported] | true |  | false | technology | active | true
JSP:SPEC:36 | 1 | 10.1 | The 'session' attribute of the page directive, when true, indicates that the JSP page requires participation in an HTTP session. | true |  | false | technology | active | true
JSP:SPEC:37 | 1 | 10.1 | The 'session' attribute of the page directive, when false, indicates that the JSP page does not participate in an HTTP session; the 'session' implicit object is not available to the page, and any reference to it within the translation unit will result in a translation error. | true |  | false | technology | active | true
JSP:SPEC:38 | 1 | 10.1 | If the 'session' attribute of the page directive is not specified by a page directive, then the page will, by default, participate in an HTTP session (default value of true). | true |  | false | technology | active | true
JSP:SPEC:39 | 1 | 10.1 | If the 'buffer' attribute of the page directive is not specified, no buffering will be performed and all output will be written directly through to the ServletResponse PrintWriter. | true |  | false | technology | active | true
JSP:SPEC:40 | 1 | 10.1 | The size value specified by the 'buffer' attribute of the page directive must be in kilobytes, and the suffix "kb" is mandatory. | true |  | false | technology | active | true
JSP:SPEC:41 | 1 | 10.1 | The container must allocate a buffer at least as large as that specified by the 'buffer' attribute of the page directive. | true |  | false | technology | active | true
JSP:SPEC:42 | 1 | 10.1 | The default buffer size of 8kb will be used if the 'buffer' attribute of the page directive is not specified. | true |  | false | technology | active | true
JSP:SPEC:43 | 1 | 10.1 | If the 'autoFlush' attribute of the page directive is true, the output will be automatically flushed when the buffer is filled. | true |  | false | technology | active | true
JSP:SPEC:44 | 1 | 10.1 | If the 'autoFlush' attribute of the page directive is false, an exception will be raised to indicate a buffer overflow when the buffer is filled. | true |  | false | technology | active | true
JSP:SPEC:45 | 1 | 10.1 | It is a translation error to set the 'autoFlush' attribute of the page directive to false, if the 'buffer' attribute is set to none. | true |  | false | technology | active | true
JSP:SPEC:46 | 1 | 10.1 | If the 'isThreadSafe' attribute of the page directive is false, the container must serialize requests to the JSP (it should behave like an SingleThreadModel servlet). | true |  | false | technology | active | true
JSP:SPEC:47 | 1 | 10.1 | The 'info' attribute of the page directive specifies an arbitrary string that is incorporated into the translated page, that can subsequently be obtained from the page's implementation of Servlet.getServletInfo(). | true |  | false | technology | active | true
JSP:SPEC:48 | 1 | 10.1 | The 'isErrorPage' attribute of the page directive. when true, will cause the implicit script language variable "exception" to be defined and its value is a reference to the offending Throwable from the source JSP page in error. | true |  | false | technology | active | true
JSP:SPEC:49 | 1 | 10.1 | If the 'isErrorPage' attribute of the page directive is defined as false, then the implicit script language variable "exception" will not be available, and any such reference to this variable will result in a translation error. | true |  | false | technology | active | true
JSP:SPEC:50 | 1 | 10.1 | The 'errorPage' attribute of the page directive, specifies the URL, either page-relative or context-relative, of a resource to which any Java programming language Throwable object(s) thrown but not caught by the page implementation are forwarded for error processing. The following request attributes will be made available within the error page: | true |  | false | technology | active | true
JSP:SPEC:50.1 | 1 | 4.3 | jakarta.servlet.jsp.jspException - throw Throwable object of the offending exception (for backwards compatibility with JSP 1.2) | true |  | false | technology | active | true
JSP:SPEC:50.2 | 1 | 4.3 | jakarta.servlet.error.exception - as per the Servlet specification. | true |  | false | technology | active | true
JSP:SPEC:50.3 | 1 | 4.3 | jakarta.servlet.error.status_code - as per the Servlet specification | true |  | false | technology | active | true
JSP:SPEC:50.4 | 1 | 4.3 | jakarta.servlet.error.exception_type - as per the Servlet specification. | true |  | false | technology | active | true
JSP:SPEC:50.5 | 1 | 4.3 | jakarta.servlet.error.message - as per the Servlet specification. | true |  | false | technology | active | true
JSP:SPEC:50.6 | 1 | 4.3 | jakarta.servlet.error.request_uri - as per the Servlet specification. | true |  | false | technology | active | true
JSP:SPEC:50.7 | 1 | 4.3 | jakarta.servlet.error.servlet_name - as per the Servlet specification. | true |  | false | technology | active | true
JSP:SPEC:50.8 | 1 | 4.3 | An instance of jakarta.servlet.jsp.ErrorData must be provided to the error page via PageContext.getErrorData(). | true |  | false | technology | active | true
JSP:SPEC:51 | 1 | 10.1 | If the 'errorPage' attribute of the page directive is defined, it will take presendence over any error pages defined in the web application's deployment descriptor. | true |  | false | technology | active | true
JSP:SPEC:52 | 1 | 10.1 | The character encoding (Content-Type response header) can be in the form of TYPE, or TYPE; Charset=CHARSET, with an optional white space after the ';'. Charset, if present, must be the IANA value for a character encoding. Similarly, if TYPE is a MIME type, see the IANA registry for values. | true |  | false | technology | active | true
JSP:SPEC:53 | 1 | 10.1 | The default Content-Type for JSP Pages in classic syntax is "text/html;charset=ISO-8859-1". | true |  | false | technology | active | true
JSP:SPEC:54 | 1 | 10.1 | If a charset portion of the value provided to the 'contentType' attribute is not specified, but the page encoding for the JSP page is specified, then the charset used will be that of the specified page encoding. | true |  | false | technology | active | true
JSP:SPEC:55 | 1 | 10.1 | If a charset is not provided as part of the 'contentType' attribute value, and the page encoding does not specifiy a type, then the default charset is ISO-8859-1 for JSP pages in classic syntax. | true |  | false | technology | active | true
JSP:SPEC:56 | 1 | 10.1 | If a charset is not provided as part of the 'contentType' attribute value, and the page encoding does not specifiy a type, then the default charset is UTF-8 for JSP pages in XML syntax. | true |  | false | technology | active | true
JSP:SPEC:57 | 1 | 10.1 | The 'pageEncoding' attribute of the page directive specifies the character encoding of the page. The value is in the form of CHARSET which my be the IANA value for a character encoding. If no 'pageEncoding' attribute is specified, the default of ISO-8859-1 will be used. | true |  | false | technology | active | true
JSP:SPEC:268 | 1 | 1.10 | If the isELIgnored attribute is true, EL expressions (of the form ${...} and #{...}) are ignored by the container. If false, EL expressions (of the form ${...} and #{...}) are recognized when they appear in template text or action attributes. [isELIgnored] | true |  | false | technology | active | true
JSP:SPEC:269 | 1 | 10.1 | The deferredSyntaxAllowedAsLiteral page directive attribute indicates if the character sequence #{ is allowed or not when used as a String literal in this page and translation unit. If false (the default value), a translation error occurs when the character sequence is used as a String literal. [DeferredSyntaxAllowedAsLiteralPageDirective] | true |  | false | technology | active | true
JSP:SPEC:270 | 1 | 10.1 | The trimDirectiveWhitespaces page attribute directive indicates how whitespaces in template text should be handled. If true, template text that contains only whitespaces is removed from the output. The default is not to trim whitespaces. [TrimDirectiveWhitespacesPageDirective] | true |  | false | technology | active | true
JSP:SPEC:58 | 1 | 10.2 | It is a translation error for the taglib directive to appear after actions that use the prefix specified by the directive. | true |  | false | technology | active | true
JSP:SPEC:59 | 1 | 10.2 | The 'uri' attribute of the taglib directive specifies either an absolute or relative URI that uniquely identifies the tag library descriptor associated with this prefix. | true |  | false | technology | active | true
JSP:SPEC:60 | 1 | 10.2 | The 'tagdir' attribute of the taglib directive indicates that the specified prefix is to be used to identify tag extensions installed in the /WEB-INF/tags directory or a subdirectory. | true |  | false | technology | active | true
JSP:SPEC:61 | 1 | 10.2 | A translation error must occur if the value provided to the 'tagdir' attribute of the taglib directive doesn't start with '/WEB-INF/tags' and point to a directory that exists within the web application. | true |  | false | technology | active | true
JSP:SPEC:62 | 1 | 10.2 | A translation error must occur if the 'prefix' attribute of the taglib directive is not present. | true |  | false | technology | active | true
JSP:SPEC:63 | 1 | 10.2 | A translation error must occur if both the 'tagdir' and 'uri' attributes are present in the same taglib directive. | true |  | false | technology | active | true
JSP:SPEC:64 | 1 | 10.2 | The 'prefix' attribute of the taglib directive is used to distinguish a custom action, e.g <myPrefix:myTag>. | true |  | false | technology | active | true
JSP:SPEC:65 | 1 | 10.2 | The value provided to the 'prefix' attribute of the taglib directive must follow the naming convention specified in the XML namespaces specification. | true |  | false | technology | active | false
JSP:SPEC:66 | 1 | 10.2 | It is illegal to provide an empty prefix to the taglib directive. | true |  | false | technology | active | false
JSP:SPEC:67 | 1 | 10.2 | A translation error will occur if the tag name provided in the custom action isn't found in the taglibrary designated by the prefix. | true |  | false | technology | active | true
JSP:SPEC:68 | 1 | 10.3 | A JSP container can include a mechanism for being notified if an included file changes, so the container can recompile the JSP page. However, the JSP 2.0 specification does not have a way of directing the JSP container that included files have changed. | false |  | true | technology | active | false
JSP:SPEC:69 | 1 | 10.3 | The 'file' attribute of the include directive specifies the resource to be imported either relative to web appliation context path, or relative to the page performing the include. | true |  | false | technology | active | true
JSP:SPEC:257 | 1 | 10.3 | With respect to the standard and XML syntaxes, a file included via the include directive can use either the same syntax as the including page, or a different syntax. the semantics for mixed syntax includes are described in Section JSP.1.10.5. | true |  | false | technology | active | true
JSP:SPEC:70 | 1 | 10.3 | The include directive includes content at translation time meaning the bytes of the included resource are directly inserted into the page. | true |  | false | technology | active | false
JSP:SPEC:258 | 1 | 10.4 | With respect to the standard and XML syntaxes, just as with the include directive, implicit includes can use either the same syntax as the including page, or a different syntax. The semantics for mixed syntax includes are described in Section JSP.1.10.5. | true |  | false | technology | active | true
JSP:SPEC:259 | 1 | 10.5 | For translation-time includes, included content can use either the same syntax as the including page, or a different syntax. The following semantics for translation-time includes apply. | true |  | false | technology | active | false
JSP:SPEC:259.1 | 1 | 10.5 | The JSP container must detect the syntax for each JSP file individually and parse each JSP file according to the syntax in which it is written. | true |  | false | technology | active | false
JSP:SPEC:259.2 | 1 | 10.5 | A JSP file written using the XML syntax must be well-formed according to the "XML" and "Namespaces in XML" specifications, otherwise a translation error must occur. | true |  | false | technology | active | true
JSP:SPEC:259.3 | 1 | 10.5 | When including a JSP document (written in the XML syntax), in the resulting XML View of the translation unit the root element of the included segment must have the default namespace reset to "". This is so that any namespaces associated with the empty prefix in the including document are not carried over to the included document. | true |  | false | technology | active | true
JSP:SPEC:259.4 | 1 | 10.5 | When a taglib directive is encountered in a standard syntax page, the namespace is applied globally, and is added to the <jsp:root> element of the resulting XML View of the translation unit. | true |  | false | technology | active | true
JSP:SPEC:259.5 | 1 | 10.5 | If a taglib directive is encountered in a standard syntax page that attempts to redefine a prefix that is already defined in the current scope (by a JSP segment in either syntax), a translation error must occur unless that prefix is being redefined to the same namespace URI. | true |  | false | technology | active | true
JSP:SPEC:71 | 1 | 12 | All JSP containers must support scripting elements based on the Java programming language. | true |  | false | technology | active | true
JSP:SPEC:72 | 1 | 12 | Any other scripting languages that are supported by a particular JSP container must support: The manipulation of Java objects; Invocation of methods on Java objects; Catching of Java language excepitons. | true |  | true | technology | active | false
JSP:SPEC:73 | 1 | 12.1 | A declaration (<%! DECL_BODY %>) must be a complete declarative statment, or sequence thereof, according to the syntax of the scripting language specified, otherwise a translation error will occur. | true |  | false | technology | active | true
JSP:SPEC:74 | 1 | 12.1 | Declartaions do not produce any output into the current out stream. | true |  | false | technology | active | true
JSP:SPEC:75 | 1 | 12.1 | Declarations are initialized when the JSP page is initialized and are made available to other delcarations, scriptlets, and expressions. | true |  | false | technology | active | true
JSP:SPEC:76 | 1 | 12.2 | Scriptlets (<% SCRIPTLET_BODY %>) can contain any code framents that are valid for the scripting language specified by the 'language' attribute of the page directive, and are executed at request time in the order that they appear on the JSP page. | true |  | false | technology | active | true
JSP:SPEC:77 | 1 | 12.3 | An expression element in a JSP page is a scripting language expression that is evaluated and the result is coerced to a String and emitted into the current JspWriter (out) object. | true |  | false | technology | active | true
JSP:SPEC:78 | 1 | 12.3 | If the result of the expression cannot be coerced to a String, the following must happen: If the problem is detected at translation time, a translation time error shall occur. If the coercion cannot be detected during translation, a ClassCastException shall be raised at request time. | true |  | false | technology | active | false
JSP:SPEC:79 | 1 | 12.3 | Expressions are evaluated left to right in the JSP page. | true |  | false | technology | active | true
JSP:SPEC:80 | 1 | 12.3 | If an expression appears in more than one run-time attribute, they are evaluated left-to-right in the element. | true |  | false | technology | active | true
JSP:SPEC:81 | 1 | 12.3 | A translation error will occur if the expression is not a complete expression in the scripting language in which it is written. | true |  | false | technology | active | true
JSP:SPEC:82 | 1 | 14.1 | Request-time attribute values in the form of '<%= scriptlet_expr %>' are only usable by actions, and cannot be used in directives. | true |  | false | technology | active | true
JSP:SPEC:83 | 1 | 14.1 | A translation error will occur if a request-time attribute expression does not appear by itself (multiple expressions, and mixing of expressions and string constands are not permitted). | true |  | false | technology | active | true
JSP:SPEC:84 | 1 | 14.1 | Any attempt to provide an attribute value via a request-time expression that doesn't accept request-time expressions, will result in a translation error. | true |  | false | technology | active | true
JSP:SPEC:85 | 1 | 14.2.1 | A type conversion failure for a static attribute lead to a failure at either request or translation time. | true |  | false | technology | active | false
JSP:SPEC:86 | 1 | 14.2.1 | Conversion of string values to a JavaBean property is done via setAsText(string-literal). | true |  | false | technology | active | true
JSP:SPEC:87 | 1 | 14.2.1 | Conversion of string values to boolean or Boolean is performed as indicated in java.lang.Boolean.valueOf(String). | true |  | false | technology | active | true
JSP:SPEC:88 | 1 | 14.2.1 | Conversion of string values to byte or Byte is performed as indiciated in java.lang.Byte.valueOf(String). | true |  | false | technology | active | true
JSP:SPEC:89 | 1 | 14.2.1 | Conversion of string values to char or Character is performed as indicated in String.charAt(0). | true |  | false | technology | active | true
JSP:SPEC:90 | 1 | 14.2.1 | Conversion of string values to double or Double is performed as indiciated in java.lang.Double.valueOf(String). | true |  | false | technology | active | true
JSP:SPEC:91 | 1 | 14.2.1 | Conversion of string values to int or Integer is performed as indiciated in java.lang.Integer.valueOf(String). | true |  | false | technology | active | true
JSP:SPEC:92 | 1 | 14.2.1 | Conversion of string values to float or Float is performed as indicated in java.lang.Float.valueOf(String). | true |  | false | technology | active | true
JSP:SPEC:93 | 1 | 14.2.1 | Conversion of string values to long or Long is perfomed as indicated in java.lang.Long.valueOf(String). | true |  | false | technology | active | true
JSP:SPEC:94 | 1 | 14.2.1 | Conversion of string values to short or Short is performed as indicated in java.lang.Short.valueOf(String). | true |  | false | technology | active | true
JSP:SPEC:95 | 1 | 14.2.1 | Conversion of string values to Object is performed as if new String(string). | true |  | false | technology | active | true
JSP:SPEC:96 | 1 | 14.2.2 | No type conversion is perfomed against reqeust-time expressions, they are provided to the element as is. | true |  | false | technology | active | true
JSP:SPEC:97 | 2 | 1 | An EL expression that is evaluated immediately is represented in JSP with the syntax ${}, while an EL expression whose evaluation is deferred is represented with the syntax #{} | true |  | false | technology | active | true
JSP:SPEC:98 | 2 | 2.2 | If EL is being evaluated by the container, a translation error will occur if an EL expression is provided as a value to an attribute that does not accept request-time expressions. | true |  | false | technology | deprecated | true
JSP:SPEC:274 | 2 | 2 | The EL can be used directly in template text, be it inside the body of a custom or standard actions or in template text outside of any action. [ELTemplateText] | true |  | false | technology | active | true
JSP:SPEC:99 | 2 | 2 | EL expressions will not be evaluated if the tag body is 'tagdependent'. | true |  | false | technology | active | true
JSP:SPEC:275 | 2 | 2 | Only the ${} syntax is allowed for expressions in template text. A translation error will result if #{} is used in template text unless #{} is turned off via a backwards compatibility mechanism.[ELTemplateTextRestriction] | true |  | false | technology | active | true
JSP:SPEC:276 | 2 | 3.1 | The type of a static attribute is always java.lang.String.[ElExpressionStaticAttributeType] | true |  | false | technology | active | true
JSP:SPEC:277 | 2 | 3.1 | The value of a static attribute must be a String literal. It is illegal to specify an expression. [ElExpressionStaticAttributeValue] | true |  | false | technology | active | true
JSP:SPEC:278 | 2 | 3.2 | If the type of a dynamic attribute is not specified in the TLD, defaults to java.lang.Object.[ElExpressionDynamicAttributeType] | true |  | false | technology | active | true
JSP:SPEC:279 | 2 | 3.2 | The value of a dynamic attribute can be a String literal, a scriptlet expression, or an EL expression using the ${} syntax. [ElExpressionDynamicAttributeValue] | true |  | false | technology | active | true
JSP:SPEC:280 | 2 | 3.2 | After evaluation of a dynamic attribute, the value is coerced to the expected type. The resulting value is passed in to the setter method for the tag attribute.[ElExpressionDynamicAttributeEvaluation] | true |  | false | technology | active | true
JSP:SPEC:281 | 2 | 3.3 | If type of a deferred-value attribute is not specified in the TLD, defaults to java.lang.Object.[ElDeferredValueType] | true |  | false | technology | active | true
JSP:SPEC:282 | 2 | 3.3 | The value of a deferred-value attribute can be a String literal or an EL expression using the #{} syntax. [ElDeferredValueValue] | true |  | false | technology | active | true
JSP:SPEC:283 | 2 | 3.3 | The result of parsing the expression of a deferred-value attribute is passed directly to the setter method of the tag attribute, whose argument type must be jakarta.el.ValueExpression. [ElDeferredValueProcessing] | true |  | false | technology | active | true
JSP:SPEC:284 | 2 | 3.3 | When a deferred-value attribute is evaluated by the tag handler, the value is coerced to the expected type. [ElDeferredValueCoercion] | true |  | false | technology | active | true
JSP:SPEC:285 | 2 | 3.3 | If a static value is provided for a deferred-value attribute, it is converted to a ValueExpression where isLiteralText() returns true.[ElDeferredValueStatic Evaluation] | true |  | false | technology | active | true
JSP:SPEC:286 | 2 | 3.4 | If the method signature for a deferred-method attribute is not defined in the TLD, it defaults to void method().[ElDeferredMethodSignature] | true |  | false | technology | active | true
JSP:SPEC:287 | 2 | 3.4 | The value of a deferred-method attribute can be a String literal or an EL expression using the #{} syntax. [ElDeferredMethodValue] | true |  | false | technology | active | true
JSP:SPEC:288 | 2 | 3.4 | A String literal can be provided to a deferred-method attribute, as long as the return type of the deferred method signature is not void. A MethodExpression is created, which when invoked, returns the String literal coerced to expected return type.[ElDeferredMethodStringLiteral] | true |  | false | technology | active | true
JSP:SPEC:289 | 2 | 3.4 | A translation error occurs if the return type of a string literal value for a deferred-method attribute is void or if the string literal cannot be coerced to the return type of the deferred method signature.[ElDeferredMethodStringLiteralError] | true |  | false | technology | active | true
JSP:SPEC:290 | 2 | 3.5 | The value of a deferred-expression-or-dynamic attribute can be a String literal, a scriptlet expression, or an EL expression using the ${} or #{} syntax. [AllowedDynamicAttributeValueTypes] | true |  | false | technology | active | true
JSP:SPEC:291 | 2 | 3.5 | The setter method argument of a deferred-expression-or dynamic attribute must be of type java.lang.Object. [ DynamicAttributeSetterMethod] | true |  | false | technology | active | true
JSP:SPEC:100 | 2 | 2.2 | A container must support EL expressions provided in template text be it inside the body of a custom or standard action, or in template text outside of any action. | true |  | false | technology | deprecated | true
JSP:SPEC:101 | 2 | 3.2 | The boolean literals in the EL are 'true' and 'false' | true |  | false | technology | active | true
JSP:SPEC:102 | 2 | 3.2 | EL integer literals are equivelant to Java integer literals. | true |  | false | technology | active | true
JSP:SPEC:103 | 2 | 3.2 | EL floating point literals are equivelant to Java floating point literals. | true |  | false | technology | active | true
JSP:SPEC:104 | 2 | 3.2 | String literals are encapsulated by either double or single quotes (''' or '"' respectively). Quotes need to be escaped in the String if the string value enclosed is the same type of quote. Escaping definitions are the same as those defined in JSP.1.6. | true |  | false | technology | active | true
JSP:SPEC:105 | 2 | 3.2 | The EL null literal is defined as 'null'. | true |  | false | technology | active | true
JSP:SPEC:106 | 2 | 3.4 | The EL follows ECMAScript in unifying the treatment of the "." and "[]" operators. To evaluate expr-a[expr-b]: | true |  | false | technology | active | false
JSP:SPEC:106.1 | 2 | 3.4 | Evaluate expr-a into value-a, if value-a is null, return null. | true |  | false | technology | active | true
JSP:SPEC:106.2 | 2 | 3.4 | Evaluate expr-b into value-b, if value-b is null, return null. | true |  | false | technology | active | true
JSP:SPEC:106.3 | 2 | 3.4 | If value-a is a Map, then if !value-a.containsKey(value-b) then return null, otherwise, return the value of value-a.get(value-b). | true |  | false | technology | active | true
JSP:SPEC:106.4 | 2 | 3.4 | If value-a is a List or array: | true |  | false | technology | active | true
JSP:SPEC:106.4.1 | 2 | 3.4 | If value-b cannot be coerced into an int (using coercion rules) an error occurs. | true |  | false | technology | active | true
JSP:SPEC:106.4.2 | 2 | 3.4 | If value-a.get(value-b) or Array.get(value-a, value-b) throws an ArrayIndexOutofBoundException or IndexOutOfBoundsException, return null. | true |  | false | technology | active | true
JSP:SPEC:106.4.3 | 2 | 3.4 | If value-a.get(value-b) or Array.get(value-a, value-b) throws other exception, error. | true |  | false | technology | active | true
JSP:SPEC:106.4.4 | 2 | 3.4 | Otherwise, return value-a.get(value-b) or Array.get(value-a, value-b) as appropriate. | true |  | false | technology | active | true
JSP:SPEC:106.5 | 2 | 3.4 | Otherwise (a JavaBeans object, coerce value-b to String | true |  | false | technology | active | true
JSP:SPEC:106.5.1 | 2 | 3.4 | If value-b is a readable property of value-a, return the result of the getter call. | true |  | false | technology | active | true
JSP:SPEC:106.5.2 | 2 | 3.4 | If value-b is not a readable property of value-a, return error. | true |  | false | technology | active | true
JSP:SPEC:106.5.3 | 2 | 3.4 | If the getter call throws an Exception: error. | true |  | false | technology | active | true
JSP:SPEC:107 | 2 | 3.5.1 | Binary operators - A { +,-,* } B | true |  | false | technology | active | false
JSP:SPEC:107.1 | 2 | 3.5.1 | If A or B is null, return 0 | true |  | false | technology | active | true
JSP:SPEC:107.2 | 2 | 3.5.1 | If A or B is Float, Double, or a String containing ".", "e", or "E", coerce both A and B to Double and apply operator. | true |  | false | technology | active | true
JSP:SPEC:107.3 | 2 | 3.5.1 | Otherwise coerce both A and B to Long and apply operator. | true |  | false | technology | active | true
JSP:SPEC:107.4 | 2 | 3.5.1 | If application of operator against A and B results in an exception, error. | true |  | false | technology | active | true
JSP:SPEC:108 | 2 | 3.5.2 | Binary operator - A { / or div } B | true |  | false | technology | active | false
JSP:SPEC:108.1 | 2 | 3.5.2 | If A or B is null, return 0 | true |  | false | technology | active | true
JSP:SPEC:108.2 | 2 | 3.5.2 | Coerce both A and B to Double and apply operator. | true |  | false | technology | active | true
JSP:SPEC:108.3 | 2 | 3.5.2 | If application of operator against A and B results in an exception, error. | true |  | false | technology | active | true
JSP:SPEC:109 | 2 | 3.5.3 | Binary Operator - A { % or mod } B | true |  | false | technology | active | false
JSP:SPEC:109.1 | 2 | 3.5.3 | If application of operator against A and B results in an exception, error. | true |  | false | technology | active | true
JSP:SPEC:109.2 | 2 | 3.5.3 | Otherwise coerce both A and B to Long and apply operator. | true |  | false | technology | active | true
JSP:SPEC:109.3 | 2 | 3.5.3 | If A or B is Float, Double, or a String containing ".", "e", or "E", coerce both A and B to Double and apply operator. | true |  | false | technology | active | true
JSP:SPEC:109.4 | 2 | 3.5.3 | If A or B is null, return 0 | true |  | false | technology | active | true
JSP:SPEC:110 | 2 | 3.5.4 | Unary minus operator - -A | true |  | false | technology | active | false
JSP:SPEC:110.1 | 2 | 3.5.4 | If A is null, return 0 | true |  | false | technology | active | true
JSP:SPEC:110.2 | 2 | 3.5.4 | If A is a String: | true |  | false | technology | active | true
JSP:SPEC:110.2.1 | 2 | 3.5.4 | If A contains ".", "e", or "E", coerce to a Double and apply operator. | true |  | false | technology | active | true
JSP:SPEC:110.2.2 | 2 | 3.5.4 | If operation results in exception, error. | true |  | false | technology | active | true
JSP:SPEC:110.2.3 | 2 | 3.5.4 | If A is Byte, Short, Integer, Long, Float, Double, retain type and apply operator | true |  | false | technology | active | true
JSP:SPEC:110.2.4 | 2 | 3.5.4 | If application of operator results in exception, error. | true |  | false | technology | active | true
JSP:SPEC:110.2.5 | 2 | 3.5.4 | Otherwise error if operator cannot be applied to the given expression. | true |  | false | technology | active | true
JSP:SPEC:110.3 | 2 | 3.5.4 | If A is Byte, Short, Integer, Long, Float, Double: | true |  | false | technology | active | true
JSP:SPEC:110.3.1 | 2 | 3.5.4 | retain the type and apply the operator. | true |  | false | technology | active | true
JSP:SPEC:110.3.2 | 2 | 3.5.4 | If application of operator results in exception, error. | true |  | false | technology | active | true
JSP:SPEC:111 | 2 | 3.5.6 | Relational operators - A { <,>,<=,=>,lt,gt,le,ge } B | true |  | false | technology | active | true
JSP:SPEC:111.1 | 2 | 3.5.6 | If A and B are equal, and operator is <=, le, >=, or ge, return true, otherwise return false. | true |  | false | technology | active | true
JSP:SPEC:111.2 | 2 | 3.5.6 | If A or B is null, return false. | true |  | false | technology | active | true
JSP:SPEC:111.3 | 2 | 3.5.6 | If A or B is Float or Double coerce both A and B to Double and apply operator. | true |  | false | technology | active | true
JSP:SPEC:111.4 | 2 | 3.5.6 | If A or B is Byte, Short, Character, Integer, or Long, coerce both A and B to Long and apply operator. | true |  | false | technology | active | true
JSP:SPEC:111.8 | 2 | 3.5.6 | If A or B is String coerce both A and B to String, compare lexically. | true |  | false | technology | active | true
JSP:SPEC:111.5 | 2 | 3.5.6 | If A is Comparable, and A.compareTo(B) throws an exception, error; otherwise return the result of A.compareTo(B) | true |  | false | technology | active | true
JSP:SPEC:111.6 | 2 | 3.5.6 | If B is Comparable, and B.compareTo(A) throws an exception, error; otherwise return the result of B.compareTo(A) | true |  | false | technology | active | true
JSP:SPEC:111.7 | 2 | 3.5.6 | Otherwise return error. | true |  | false | technology | active | true
JSP:SPEC:112 | 2 | 3.5.7 | Relation Operatos - A { ==, !=, eq, ne } B | true |  | false | technology | active | false
JSP:SPEC:112.1 | 2 | 3.5.7 | If A == B, apply operator. | true |  | false | technology | active | true
JSP:SPEC:112.2 | 2 | 3.5.7 | If A or B is null, return false for == (eq), true for != (ne) | true |  | false | technology | active | true
JSP:SPEC:112.3 | 2 | 3.5.7 | If A or B is Float or Double coerce both A and B to Double and apply operator. | true |  | false | technology | active | true
JSP:SPEC:112.4 | 2 | 3.5.7 | If A or B is Byte, Short, Character, Integer, or Long, coerce both A and B to Long and apply operator. | true |  | false | technology | active | true
JSP:SPEC:112.5 | 2 | 3.5.7 | If A or B is Boolean coerce both A and B to Boolean apply operator. | true |  | false | technology | active | true
JSP:SPEC:112.6 | 2 | 3.5.7 | If A or B is String coerce both A and B to String, if error occurs calling A.equals(B), error; otherwise apply operator to result of A.equals(B). | true |  | false | technology | active | true
JSP:SPEC:112.6.1 | 2 | 3.5.7 | If error occurs calling A.equals(B), error otherwise apply operator to result of A.equals(B). | true |  | false | technology | active | true
JSP:SPEC:112.6.2 | 2 | 3.5.7 | Otherwise apply operator to result of A.equals(B). | true |  | false | technology | active | true
JSP:SPEC:113 | 2 | 3.6.1 | Binary Operator - A { &&, ||, and, or } B | true |  | false | technology | active | false
JSP:SPEC:113.1 | 2 | 3.6.1 | Coerce both A and B to Boolean and apply operator. | true |  | false | technology | active | true
JSP:SPEC:114 | 2 | 3.6.2 | Unary operator - { !, not } A | true |  | false | technology | active | false
JSP:SPEC:114.1 | 2 | 3.6.2 | Coerce A to Boolean and apply operator. | true |  | false | technology | active | true
JSP:SPEC:115 | 2 | 3.7 | Empty operator - empty A | true |  | false | technology | active | false
JSP:SPEC:115.1 | 2 | 3.7 | If A is null, return true | true |  | false | technology | active | true
JSP:SPEC:115.2 | 2 | 3.7 | If A is an emtpy String, return true. | true |  | false | technology | active | true
JSP:SPEC:115.3 | 2 | 3.7 | If A is an empty array, then return true. | true |  | false | technology | active | true
JSP:SPEC:115.4 | 2 | 3.7 | If A is an emtpy Map, then return true. | true |  | false | technology | active | true
JSP:SPEC:115.5 | 2 | 3.7 | If A is an empty List, then return true. | true |  | false | technology | active | true
JSP:SPEC:115.6 | 2 | 3.7 | Otherwise return false | true |  | false | technology | active | true
JSP:SPEC:116 | 2 | 3.9 | Operator precedence (highest to lowest) - [] . then (), then -(unary) not ! emtpy, then * / div % mod, then + - (binary), then < > <= >= lt gt le ge, then == != eq ne, then && and, then || or. | true |  | false | technology | active | true
JSP:SPEC:117 | 2 | 4 | The following words are reserved by the EL, and, or, not, eq, ne, lt, gt, le, ge, true, false, null, instanceof, empty, div, mod and should not be used as identifiers without being quoted. | true |  | false | technology | active | false
JSP:SPEC:118 | 2 | 5 | If no scope qualifier is added to provided EL expression, the EL will lookup the attribute based on the behavior of PageContext.findAttribute(String), i.e, it will search the PageContext for the attribute first in the page, then request, then session, followed by application scopes and will return the value, otherwise null will be returned. | true |  | false | technology | active | true
JSP:SPEC:119 | 2 | 6.2 | If the function class, as described in the TLD, is not a public non-abstract class, a translation error will occur. | true |  | false | technology | removed | true
JSP:SPEC:120 | 2 | 6.2 | If the method, as described in the TLD, is not a public static method, a translation error will occur. | true |  | false | technology | active | true
JSP:SPEC:121 | 2 | 6.2 | If two functions within the same tag library have the same name, a translation error will occur. | true |  | false | technology | active | true
JSP:SPEC:122 | 2 | 6.4 | EL function invocation semantics: | true |  | false | technology | active | true
JSP:SPEC:122.1 | 2 | 6.4 | If the function has no namespace associated, then, if the function is used in an attribute value, assume the namespace as that of the custom action; if the function is used elsewhere, this shall be a translation error. | true |  | false | technology | active | true
JSP:SPEC:122.2 | 2 | 6.4 | Locate the TLD associated with the namespace. If none can be found, a translation error shall occur. | true |  | false | technology | active | true
JSP:SPEC:122.3 | 2 | 6.4 | Locate the function element with a name subelement with the provided function name. If none can be found, a translation error shall occur. | true |  | false | technology | active | true
JSP:SPEC:122.4 | 2 | 6.4 | Locate the public class with name equal to the value of the funcion-class element. Locate the public static method with name and signature equal to the value of the function-signature element. If any of these don't exist, a translation error shall occur. | true |  | false | technology | active | true
JSP:SPEC:122.5 | 2 | 6.4 | Evaluate each argument to the corresponding type indicated in the signature. | true |  | false | technology | active | true
JSP:SPEC:122.6 | 2 | 6.4 | Evaluate the public static Java method. The resulting type is that of the return value in the function-signature element. | true |  | false | technology | active | true
JSP:SPEC:123 | 2 | 2.3 | The 'pageContext' implicit object corresponse to the PageContext object. | true |  | false | technology | active | true
JSP:SPEC:124 | 2 | 2.3 | The 'pageScope' implicit object allows access to page scoped attribute values. | true |  | false | technology | active | true
JSP:SPEC:125 | 2 | 2.3 | The 'requestScope' implicit object allows access to request scoped attribute values. | true |  | false | technology | active | true
JSP:SPEC:126 | 2 | 2.3 | The 'sessionScope' implicit object allows access to session scoped attribute values. | true |  | false | technology | active | true
JSP:SPEC:127 | 2 | 2.3 | The 'applicationScope' implicit object allows access to application scoped attribute values. | true |  | false | technology | active | true
JSP:SPEC:128 | 2 | 2.3 | The 'param' implicit object allows access to a single parameter value (obtained via ServletRequest.getParameter(String name)). | true |  | false | technology | active | true
JSP:SPEC:129 | 2 | 2.3 | The 'paramValues' implicit allows access to a String[] of all values for the specified parameter (obtained via ServletRequest.getParameterValues(String name)). | true |  | false | technology | active | true
JSP:SPEC:130 | 2 | 2.3 | The 'header' implicit object allows access to a single request-header value (obtained by calling HttpServletRequest.getHeader(String name)). | true |  | false | technology | active | true
JSP:SPEC:131 | 2 | 2.3 | The 'headerValues' implicit object returns the a String[] of all values for the specified header (obtained via HttpServletRequest.getHeaders(String name)). | true |  | false | technology | active | true
JSP:SPEC:132 | 2 | 2.3 | The 'cookie' implicit object provides access the the named cookie. | true |  | false | technology | active | true
JSP:SPEC:132.1 | 2 | 2.3 | If there are multiple cookies identified by the same name, the implementation must return the first cookie in the array, but the cookie order provided to the implementation is currently not specified. | true |  | true | technology | active | false
JSP:SPEC:133 | 2 | 2.3 | The 'initParam' implicit object provides access to context initialization parameters (obtained via ServletContext.getInitParameter(String name)). | true |  | false | technology | active | true
JSP:SPEC:134 | 2 | 8.1 | To coerce a value X to type Y | true |  | false | technology | active | true
JSP:SPEC:134.1 | 2 | 8.1 | If X is of a primitive type, Let X be the equivalent 'boxed form' of X, otherwise, Let X be the same as X. | true |  | false | technology | active | true
JSP:SPEC:134.2 | 2 | 8.1 | If Y is of a primitive type, Let Y be the equivalent 'boxed form' of Y. Otherwise, let Y be the same as Y. | true |  | false | technology | active | true
JSP:SPEC:134.3 | 2 | 8.1 | Apply conversion rules. | true |  | false | technology | active | true
JSP:SPEC:134.4 | 2 | 8.1 | If Y is a primitive type, then the result is found by 'unboxing' the result of the coercion. If the result of the coercion is null, then error. | true |  | false | technology | active | true
JSP:SPEC:134.5 | 2 | 8.1 | If Y is not a primitive type, the the result is the result of the coercion. | true |  | false | technology | active | true
JSP:SPEC:135 | 2 | 8.2 | Coerce A to String | true |  | false | technology | active | true
JSP:SPEC:135.1 | 2 | 8.2 | If A is a String: return A | true |  | false | technology | active | true
JSP:SPEC:135.2 | 2 | 8.2 | If A is null, return and empty String (""). | true |  | false | technology | active | true
JSP:SPEC:135.3 | 2 | 8.2 | If A.toString() throws exception, error. | true |  | false | technology | active | true
JSP:SPEC:135.4 | 2 | 8.2 | Otherwise return A.toString() | true |  | false | technology | active | true
JSP:SPEC:136 | 2 | 8.3 | Coerce A to Number type N | true |  | false | technology | active | true
JSP:SPEC:136.1 | 2 | 8.3 | If A is null or "", return 0 | true |  | false | technology | active | true
JSP:SPEC:136.2 | 2 | 8.3 | If A is Character, convert to short, apply numeric rules below. | true |  | false | technology | active | true
JSP:SPEC:136.3 | 2 | 8.3 | If A is a Boolean, then error. | true |  | false | technology | active | true
JSP:SPEC:136.4 | 2 | 8.3 | If A is Number type N, return A | true |  | false | technology | active | true
JSP:SPEC:136.5 | 2 | 8.3 | If A is a Number, coerce quietly to type N | true |  | true | technology | active | true
JSP:SPEC:136.6 | 2 | 8.3 | If A is String, and N.valueOf(A) throws exception, then error. | true |  | false | technology | active | true
JSP:SPEC:136.7 | 2 | 8.3 | If A is String, and N.valueOf(A) does not throw an exception, return the value. | true |  | false | technology | active | true
JSP:SPEC:136.8 | 2 | 8.3 | All other types will result in an error. | true |  | false | technology | active | true
JSP:SPEC:137 | 2 | 8.4 | Coerce A to Character | true |  | false | technology | active | true
JSP:SPEC:137.1 | 2 | 8.4 | If A is null or "". return (char) 0 | true |  | false | technology | active | true
JSP:SPEC:137.2 | 2 | 8.4 | If A is Character, then return A | true |  | false | technology | active | true
JSP:SPEC:137.3 | 2 | 8.4 | If A is Boolean, error. | true |  | false | technology | active | true
JSP:SPEC:137.4 | 2 | 8.4 | If A is Number, coerce quietly to type Short, then return a Character whose numeric value is equivalent to that Short. | true |  | false | technology | active | true
JSP:SPEC:137.5 | 2 | 8.4 | If A is String, return A.charAt(0) | true |  | false | technology | active | true
JSP:SPEC:137.6 | 2 | 8.4 | All other types will result in an error. | true |  | false | technology | active | true
JSP:SPEC:138 | 2 | 8.5 | Coerce A to Boolean | true |  | false | technology | active | true
JSP:SPEC:138.1 | 2 | 8.5 | If A is null or "", return false | true |  | false | technology | active | true
JSP:SPEC:138.2 | 2 | 8.5 | Otherwise if A is Boolean, return A | true |  | false | technology | active | true
JSP:SPEC:138.3 | 2 | 8.5 | Otherwise if A is String, and Boolean.valueOf(A) throws exception, error. | true |  | false | technology | active | true
JSP:SPEC:138.4 | 2 | 8.5 | Otherwise if A is String , and Bollean.valueOf(A) does not throw exception, return it. | true |  | false | technology | active | true
JSP:SPEC:138.5 | 2 | 8.5 | Any other type, return error. | true |  | false | technology | active | true
JSP:SPEC:139 | 2 | 8.6 | Coerce A to any other type T | true |  | false | technology | active | true
JSP:SPEC:139.1 | 2 | 8.6 | If A is null, return null. | true |  | false | technology | active | true
JSP:SPEC:139.2 | 2 | 8.6 | If A is assignable to T, coerce quietly. | true |  | false | technology | active | true
JSP:SPEC:139.3 | 2 | 8.6 | If A is String, and T has no Property Editor, then if A is "" return null, otherwise error. | true |  | false | technology | active | true
JSP:SPEC:139.4 | 2 | 8.6 | If A is String, and T's PropertyEditor throws exception, then if A is "" return null, otherwise error. | true |  | false | technology | active | true
JSP:SPEC:139.5 | 2 | 8.6 | Otherwise, apply T's PropertyEditor | true |  | false | technology | active | true
JSP:SPEC:139.6 | 2 | 8.6 | Otherwise, error | true |  | false | technology | active | true
JSP:SPEC:140 | 3 | 3 | A jsp-property-group will apply a set of properties to a specific group of resources identified via a URL pattern. If a resource matches URL patterns in more than one group, the pattern that is the most specific applies (follows the rules for URL pattern matching as defined in the Servlet Specification). | true |  | false | technology | active | true
JSP:SPEC:292 | 2 | 9 | the setter method argument must be of type java.lang.Object. [ DynamicAttributeSetterMethod P1] | true |  | false | technology | active | false
JSP:SPEC:293 | 2 | 10 | No function mapper needs to be provided at function evaluation time.[FunctionMappingInformation] | true |  | false | technology | active | false
JSP:SPEC:294 |  |  | If an exception is thrown during the method evaluation of a function, the exception must be wrapped in an ELException and the ELException must be thrown. [FunctionMappingELException] | true |  | false | technology | active | true
JSP:SPEC:141 | 3 | 3.2 | EL expression evaluation can be activated for a group of JSP resources as specified by the URL pattern using the <el-ignored> subelement of the <jsp-property-group> element. If the value provided is true, EL expressions will be evaluated. | true |  | false | technology | active | true
JSP:SPEC:142 | 3 | 3.2 | EL expression evaluation can be deactivated for a group of JSP resources as specified by the URL pattern using the <el-ignored> subelement of the <jsp-property-group> element. If the value provided is false, EL expressions will be treated as template text (or uninterpreted attribute values). | true |  | false | technology | active | true
JSP:SPEC:252 | 3 | 3.2 | The container will not evaluated EL-like constructs (${expr}) found in deployed web applications based on Servlet 2.3 or earlier. | true |  | false | technology | active | true
JSP:SPEC:254 | 3 | 3.2 | If are JSP page matches a URL of a property group and the el-ignored element is not specified, and the web application is 2.4 or later, than any EL expressions encounterd will be evaluated. | true |  | false | technology | active | true
JSP:SPEC:255 | 3 | 3.2 | If a JSP page that matches a URL pattern of a property group specifies the isELIgnored attribute, this attribute will take precedence over any setting in the JSP property group. | true |  | false | technology | active | true
JSP:SPEC:143 | 3 | 3.3 | Scripting elements can be allowed for a group of JSP resources as specified by the URL pattern using the <scripting-invalid> subelement of the <jsp-property-group> element. If the value is true, scripting elements such as scriptlets, classic expressions, and declarations will be allowed. | true |  | false | technology | active | true
JSP:SPEC:144 | 3 | 3.3 | Scripting elements can be disallowed for a group of JSP resources as specified by the URL pattern using the <scripting-invalid> subelement of the <jsp-property-group> element. If the value is false, scripting elements such as scriptlets, classic expressions, and declarations present within this group will result in translation errors for any page containing such elements. | true |  | false | technology | active | true
JSP:SPEC:256 | 3 | 3.3 | If a JSP page matches a URL pattern of a JSP property group and the property group contains no scripting-invalid element, scripting will be allowed in the page and no translation error will occur. | true |  | false | technology | active | true
JSP:SPEC:253 | 3 | 3.4 | The <page-encoding> element is used to set the pageEncoding property of a group of JSP pages. | true |  | false | technology | active | true
JSP:SPEC:145 | 3 | 3.4 | A translation error will occur if the target translation unit specifies a different page encoding than that specified in the <page-encoding> subelement of the <jsp-property-group> element. | true |  | false | technology | active | true
JSP:SPEC:146 | 3 | 3.4 | A translation error will not occur if the target translation unit specifies the same page encoding as that specified in the <page-encoding> subelement of the <jsp-property-group> element (provided no other issues exist within the translation unit). | true |  | false | technology | active | true
JSP:SPEC:147 | 3 | 3.5 | The <include-prelude> subelement of the <jsp-property-group> element defines a context-relative path to a resource within the web application that will be automatically included into the beginning of all JSP resources of the particular group. | true |  | false | technology | active | true
JSP:SPEC:148 | 3 | 3.5 | The <include-coda> subelement of the <jsp-property-group> element defines a context-relative path to a resource within the web application that will be automatically included into the end of all JSP resources of the particular group. | true |  | false | technology | active | true
JSP:SPEC:149 | 3 | 3.5 | In both cases, <include-prelude> and <include-coda>, if there are multiple entries of these elements they will be included into the JSP page in the order they appear within the <jsp-property-group> element. | true |  | false | technology | active | true
JSP:SPEC:150 | 3 | 3.6 | The <is-xml> subelement of the <jsp-property-group> element is used to denote that a group of files are JSP doucments, and thus must be interpreted as XML documents. | true |  | false | technology | active | true
JSP:SPEC:150.1 | 3 | 3.6 | If 'true', the files denoted must be interpreted as XML documents. | true |  | false | technology | active | true
JSP:SPEC:150.2 | 3 | 3.6 | If 'false', the files in the associated property group are assumed not to be JSP documents. | true |  | false | technology | active | true
JSP:SPEC:150.3 | 3 | 3.6 | If the <is-xml> subelement is false within one property-group, but another property-group identifying the same set of files sets <is-xml> to true, then the files will be processed as XML documents. | true |  | false | technology | active | true
JSP:SPEC:295 | 3 | 3.7 | A translation error occurs if the #{ character sequence is used as a String literal (in template text of a JSP 2.1+ container or as an attribute value for a tag-library where jsp-version is 2.1+). [TranslationError#{Sequence] | true |  | false | technology | active | true
JSP:SPEC:296 | 3 | 3.7 | Allowing the character sequence #{ when used as a String literal can be done by setting the deferred-syntax-allowed-as-literal element to true in the JSP configuration. [DeferredSyntaxAllowedAsLiteralElement] | true |  | false | technology | active | true
JSP:SPEC:297 | 3 | 3.8 | Enabling the trimming of whitespaces can be done by setting the trim-directive-whitespaces element to true in the JSP configuration. [TrimDirectiveWhitespacesElement] | true |  | false | technology | active | true
JSP:SPEC:249 | 4 | 1 | For JSP pages in standard syntax, the page character encoding is determined from the followed sources: | true |  | false | technology | active | false
JSP:SPEC:249.1 | 4 | 1 | A JSP configuration element page-encoding value whoe URL pattern matches the page. | true |  | false | technology | active | true
JSP:SPEC:249.2 | 4 | 1 | The pageEncoding attribute of the page directive of the page. | true |  | false | technology | active | true
JSP:SPEC:249.2.1 | 4 | 1 | It is a translation-time error to name different encodings in the pageEncoding attribute of the page directive of a JSP page and in a JSP configuration element whos URL pattern matches the page. | true |  | false | technology | active | true
JSP:SPEC:249.3 | 4 | 1 | The charset value of the contentType attribute of the page directive. This is used to determine the page character encoding if neither a JSP configuration element page-encoding nor the pageEncoding attribute are provided. | true |  | false | technology | active | true
JSP:SPEC:249.4 | 4 | 1 | If neither the JSP configuration page-encoding element, nor the pageEncoding attribute, nor the charset of the contentType attribute are present, ISO-8859-1 will be used as the encoding for the page. | true |  | false | technology | active | true
JSP:SPEC:249.5 | 4 | 1 | Files included using the include directive are read using the character encoding of the including page. | true |  | false | technology | active | true
JSP:SPEC:250 | 4 | 2 | The JSP container will call ServletResponse.setContentType() after determining the content type as follows: | true |  | false | technology | active | false
JSP:SPEC:250.1 | 4 | 2 | If the TYPE value of the contentType attribute is present in the current translation unit, this TYPE will be used to set the initial response content type. | true |  | false | technology | active | true
JSP:SPEC:250.2 | 4 | 2 | If the contentType attribute is omitted in a JSP page using standard syntax, the initial content type is 'text/html'. | true |  | false | technology | active | true
JSP:SPEC:250.3 | 4 | 2 | If the contentType attribute is omitted in a JSP document, the initial content type is 'text/xml'. | true |  | false | technology | active | true
JSP:SPEC:250.4 | 4 | 2 | The intial response encoding will be the CHARSET value of the contentType attribute of the page directive. | true |  | false | technology | active | true
JSP:SPEC:250.5 | 4 | 2 | For JSP documents, where the contentType attribute is not present, or is present, but doesn't specify a chaset, the response encoding will be UTF-8. | true |  | false | technology | active | true
JSP:SPEC.250.6 | 4 | 2 | For JSP pages in standard syntax that do not have a contentType attribute, or the attribute is present without a charset specification: | true |  | false | technology | active | false
JSP:SPEC:250.6.1 | 4 | 2 | The response encoding used will be that of the pageEncoding attribute or that specified by the JSP configuration element page-encoding whise URL pattern matches the page. | true |  | false | technology | active | true
JSP:SPEC:250.6.2 | 4 | 2 | If the page has no pageEncoding attribute, or there is no matching jsp configuration, the response encoding will be ISO-8859-1. | true |  | false | technology | active | true
JSP:SPEC:251 | 4 | 2 | The XML view character encoding is always UTF-8 | true |  | false | technology | active | false
JSP:SPEC:249.5 | 4 | 1 | For JSP documents, the page character encoding is determined as described in section 4.3.3 and appendix F.1 of the XML specification. | true |  | false | technology | active | true
JSP:SPEC:249.6 | 4 | 1 | The pageEncoding of a JSP document can also be described via the JSP configuration element page-encoding or a pageEncoding attribute of the page directive of the page, as long as long as they are consistent with the encoding as determined in section 4.3.3 and appendix F.1 of the XML specification. | true |  | false | technology | active | true
JSP:SPEC:249.7 | 4 | 1 | It is translation-time error to name different encodings in two or more of the following: the XML prolog of a JSP page, the pageEncoding attribute of the page directive of the JSP page, and in a JSP configuration element whose URL pattern matches the page. | true |  | false | technology | active | true
JSP:SPEC:249.8 | 4 | 1 | The JSP container must raise a translation-time error if an unsupported page character encoding is requested. | true |  | false | technology | active | true
JSP:SPEC:298 | 4 | 1.1 | For tag files in standard syntax, the page character encoding is determined from a BOM or the pageEncoding attribute of the tag directive of the tag file (in this precedence order), or is ISO-8859-1 if neither is specified. [PageCharacterEncodingDetermination] | true |  | false | technology | active | false
JSP:SPEC:299 | 4 | 1.1 | When using a BOM, it is legal to describe the character encoding in a JSP configuration element page-encoding or a pageEncoding attribute of the page directive of the page, as long as they are consistent. [BOMCharacterEncodingDescription ] | true |  | false | technology | active | true
JSP:SPEC:300 | 4 | 1.2 | For JSP documents in XML syntax, it is legal to also describe the character encoding in a JSP configuration element page-encoding or a pageEncoding attribute of the page directive of the document, as long as they are consistent. [BOMLegalCharacterEncoding] | true |  | false | technology | active | true
JSP:SPEC:151 | 5 | 1 | If the <jsp:useBean> action is used within a scriptless context, then the variable exported will be available via EL expressions. | true |  | false | technology | active | true
JSP:SPEC:152 | 5 | 1 | If both 'type' and 'class' attributes of the <jsp:useBean> standard action are present, and 'class' is not assignable to 'type', a translation error will occur. | true |  | false | technology | active | true
JSP:SPEC:153 | 5 | 1 | A translation error will occur of both the 'beanName' and 'class' attributes are specified within the same useBean action. | true |  | false | technology | active | true
JSP:SPEC:154 | 5 | 1 | The 'beanName' attribute can accept dynamic attribute values (RT or EL). | true |  | false | technology | active | true
JSP:SPEC:155 | 5 | 1 | The 'beanName' attribute of the <jsp:useBean> action must be of the form "a.b.c", which can resolve to: | true |  | false | technology | active | true
JSP:SPEC:155.1 | 5 | 1 | A java class that will be resolved in the current ClassLoader | true |  | false | technology | active | true
JSP:SPEC:155.2 | 5 | 1 | A serialized bean instance in the form similar to a/b/c.ser that will be resolved in the current ClassLoader. | true |  | false | technology | active | true
JSP:SPEC:155.3 | 5 | 1 | If the resource identified by 'beanName' attribute of the <jsp:useBean> action cannot be resolved, a request-time exception, as indicated in the semantics of the instantiate() method of the java.beans.Beans class, will be raised. | true |  | false | technology | active | true
JSP:SPEC:156 | 5 | 1 | The 'id' attribute of the <jsp:useBean> actions provides the name used to identify the object instance in the specified scopes namespace, and also the scripting variable name declared and initialized with that reference. | true |  | false | technology | active | true
JSP:SPEC:156.1 | 5 | 1 | The name specified is case sensitive. | true |  | false | technology | active | true
JSP:SPEC:157 | 5 | 1 | The value's provided to the 'id' attribute of the <jsp:useBean> action must be unique within the given translation unit. Any duplicate id's found, will result in a translation error. | true |  | false | technology | active | true
JSP:SPEC:158 | 5 | 1 | The 'scope' attribute of the <jsp:useBean> action specifies the scope or namespace within which the object reference is available. | true |  | false | technology | active | true
JSP:SPEC:158.1 | 5 | 1 | If the 'scope' attribute is not specified, the default scope will be 'page'. | true |  | false | technology | active | true
JSP:SPEC:158.2 | 5 | 1 | If a value of 'page' is provided to the 'scope' attribute, the object will be exported to the page scope. | true |  | false | technology | active | true
JSP:SPEC:158.3 | 5 | 1 | If a value of 'request' is provided to the 'scope' attribute, the object will be exported to the request scope. | true |  | false | technology | active | true
JSP:SPEC:158.4 | 5 | 1 | If a value of 'session' is provided to the 'scope' attribute, the object will be exported to the session scope. | true |  | false | technology | active | true
JSP:SPEC:158.5 | 5 | 1 | If a value of 'application' is provided to the 'scope' attribute, the object will be exported to the application scope. | true |  | false | technology | active | true
JSP:SPEC:158.6 | 5 | 1 | If the value provided to the 'scope' attribute is not one of 'page', 'request', 'session', or 'application', a translation error will occur. | true |  | false | technology | active | true
JSP:SPEC:159 | 5 | 1 | A translation error will occur if the <jsp:useBean> action attempts to export an object to the session scope and sessions have been disabled for the target page. | true |  | false | technology | active | true
JSP:SPEC:160 | 5 | 1 | For all scopes, it is illegal to change the value of an instance object associated with a particular scope, such that its new runtime type is a subset of the type(s) of the object previously so associated. | true |  | true | technology | active | false
JSP:SPEC:161 | 5 | 1 | Sematics: The actions performed in jsp:useBean action are: | true |  | false | technology | active | false
JSP:SPEC:161.1 | 5 | 1 | The action searches for objects in scope, the search is done synchronized per scope namespace to avoid non-deterministic behavior. | true |  | false | technology | active | false
JSP:SPEC:161.2 | 5 | 1 | A scripting language variable of the specified type (if given) or class (if type is not give) is defined with the given 'id' int he current lexical scope of the scripting language. | true |  | false | technology | active | true
JSP:SPEC:161.3 | 5 | 1 | If the 'class' attribute of the action is provided a value that referrs to an Abstract class, an Interface, or a class with no public no-arg constructor, the implementation may throw a java.lang.InstantiationException, or may raise a translation error. | true |  | true | technology | active | true
JSP:SPEC:161.4 | 5 | 1 | If the object, as identified by the 'id' and 'scope' attributes of the action is found, and the object is not castable to the type as specified by the 'type' attribute, a java.lang.ClassCastException shall occur. The action will cease processing at this point. | true |  | false | technology | active | true
JSP:SPEC:161.5 | 5 | 1 | If the jsp:useBean has a non-empty body, it will be ignored (i.e. template text, as well as standard and custom actions will not be processed) and the action will cease processing. | true |  | false | technology | active | true
JSP:SPEC:161.6 | 5 | 1 | If the specified object is not found in the specified scope, and neither 'class' nor 'beanName' are given, a java.lang.InstantiationException shall occur and the action will cease processing. | true |  | false | technology | active | true
JSP:SPEC:161.7 | 5 | 1 | If the specified object is not found in the specified scope, and the 'class' attribute specifies a non-abstract class that defines a public no-args constructor, then the class is instantiated and the object reference is associated with a scripting variable name as identified by the 'id' attribute and exported to the scope as indicated by the 'scope' attribute. | true |  | false | technology | active | true
JSP:SPEC:161.7.1 | 5 | 1 | If the action has a non-empty body, then the body will be processed. Template text will be passed through, and standard and custom actions will be processed by the container. | true |  | false | technology | active | true
JSP:SPEC:161.8 | 5 | 1 | If the specified object is not found in the specified scope, and the 'beanName' attribute is specified, then the method instantiate() of java.beans.Beans will be invoked with the ClassLoader of the Servlet object with the value of the 'beanName' attribute as the argument. If the method succeeds, the object refernece is associated with the scripting variable identified by the 'id' attribute and expored to the scope as indicated by the 'scope' attribute. | true |  | false | technology | active | true
JSP:SPEC:161.8.1 | 5 | 1 | If the action has a non-empty body, then the body will be processed. Template text will be passed through, and standard and custom actions will be processed by the container. | true |  | false | technology | active | true
JSP:SPEC:161.8.1.1 | 5 | 11 | The body of the action can be specified via the <jsp:body> action. | true |  | false | technology | active | true
JSP:SPEC:162 | 5 | 2 | The <jsp:setProperty> action sets the values of properties in a Bean. | true |  | false | technology | active | false
JSP:SPEC:162.1 | 5 | 2 | The 'name' attribute specifies the name of a Bean instance defined by a <jsp:useBean> action or some other action. | true |  | false | technology | active | true
JSP:SPEC:162.1.1 | 5 | 2 | The Bean instance must contain the property that is being set. | true |  | false | technology | active | false
JSP:SPEC:162.1.2 | 5 | 2 | If the object in which the property will be set was not introduced before the jsp:setProperty call, the container implementation is recommended, but not required to raise a translation error. | false |  | true | technology | active | false
JSP:SPEC:162.2 | 5 | 2 | The 'property' attribute specifies the bean property whose value is to be set. | true |  | false | technology | active | true
JSP:SPEC:162.2.1 | 5 | 2 | If '*' is provided to the property attribute, the action will iterate over the current ServletRequest parameters matching parameter names and value types(s) to property names and setter method type(s), setting each matched property to the value of the matching parameter. | true |  | false | technology | active | true
JSP:SPEC:162.2.2 | 5 | 2 | If a parameter has a value of "", the corresponding property is not modified. | true |  | false | technology | active | true
JSP:SPEC:162.3 | 5 | 2 | The 'param' attribute specifies the name of the request parameter whose value will be given to a Bean property. | true |  | false | technology | active | true
JSP:SPEC:162.4 | 5 | 2 | If the 'param' attribute is omitted from the action, the request parameter name is assumed to be the same as the Bean property name. | true |  | false | technology | active | true
JSP:SPEC:162.5 | 5 | 2 | If the param is not set in the Request object, or if it has the value of "", the action has no effect (a noop). | true |  | false | technology | active | true
JSP:SPEC:162.6 | 5 | 2 | A translation error will occur if both the 'param' and 'value' attributes both specified within the same action. | true |  | false | technology | active | true
JSP:SPEC:162.7 | 5 | 2 | The 'value' attribute specifies the value to assign to the given property. | true |  | false | technology | active | true
JSP:SPEC:162.7.1 | 5 | 2 | The 'value' attribute can accept request-time expressions (RT and EL). | true |  | false | technology | active | true
JSP:SPEC:162.7.2 | 5 | 10 | The 'value' attribute can be described via the <jsp:attribute> standard action. | true |  | false | technology | active | true
JSP:SPEC:162.8 | 5 | 2 | A translation error will occur if the 'property' attribute value is '*', and any other attributes are provided to the action. | true |  | false | technology | active | true
JSP:SPEC:162.9 | 5 | 2 | When assigning values from a parameter in the request object, the conversions described in JSP.1.14.2.1 are applied, using the target property to determine the target type. | true |  | false | technology | active | true
JSP:SPEC:162.10 | 5 | 2 | When assigning from a value given as a String constant, the conversions described in JSP.1.14.2.1 are applied, using the target property to determine the target type. | true |  | false | technology | active | true
JSP:SPEC:162.11 | 5 | 2 | When assigning from a value given as a request-time attribute, no type conversions are applied, as indicated in Section JSP.1.14.2.2 | true |  | false | technology | active | true
JSP:SPEC:162.12 | 5 | 2 | When assinging values to indexed properties the values must be an array; the rules, as indicated in Section JSP.1.14.2.2 apply. | true |  | false | technology | active | true
JSP:SPEC:163 | 5 | 3 | The <jsp:getProperty> action places the value of a Bean instance property, converted to a String, into the implicit out object. | true |  | false | technology | active | true
JSP:SPEC:163.1 | 5 | 3 | The 'name' attribute specifies the name of the Bean instance from which the property is obtained. | true |  | false | technology | active | true
JSP:SPEC:163.2 | 5 | 3 | The 'property' attribute specifies the name of the property to access within the specified Bean instance. | true |  | false | technology | active | true
JSP:SPEC:163.3 | 5 | 3 | If the object referenced by the 'name' attribute was not 'introduced' via <jsp:useBean> or a custom action with an associated VariableInfo entry, the container implementation, is recommended (but nore required) to raise a translation error, since this page implementation is in violation of the specification. | false |  | true | technology | active | false
JSP:SPEC:163.4 | 5 | 3 | The conversion to String is done as in the println() methods, i.e. the toString() method of the object is used for Object instances, and primitive types are converted directly. | true |  | false | technology | active | true
JSP:SPEC:163.5 | 5 | 3 | A translation error will occur if the 'property' attribute is not specified within the action. | true |  | false | technology | active | true
JSP:SPEC:164 | 5 | 4 | The <jsp:include> action provides for inclusion of static and dynamic resources in the same context as the current page. | true |  | false | technology | active | true
JSP:SPEC:164.1 | 5 | 4 | The 'page' attribute specifies a relative URL (either page or context relative) to a resource within the same web application context. | true |  | false | technology | active | true
JSP:SPEC:164.2 | 5 | 4 | The 'flush' attribute, if true, will immediately flush the buffer prior to inclusion. | true |  | false | technology | active | true
JSP:SPEC:164.3 | 5 | 4 | The 'flush' attribute, if false, will not flush the buffer prior to inclusion. | true |  | false | technology | active | true
JSP:SPEC:164.4 | 5 | 4 | The default value for the 'flush' attribute is false. | true |  | false | technology | active | true
JSP:SPEC:164.5 | 5 | 4 | A translation error will occur of the 'page' attribute is not specified. | true |  | false | technology | active | true
JSP:SPEC:164.6 | 5 | 4 | An included page only has access to the JspWriter object (out). | true |  | false | technology | active | true
JSP:SPEC:164.7 | 5 | 4 | Any attempt by an included page to set headers, will be ignored by the container. | true |  | false | technology | active | true
JSP:SPEC:164.8 | 5 | 4 | An include action may use <jsp:param> action present as body content to provide request parameters for the included resource. | true |  | false | technology | active | true
JSP:SPEC:164.9 | 5 | 4 | The 'page' attribute can accept request-time expressions (either classic RT or EL). | true |  | false | technology | active | true
JSP:SPEC:164.10 | 5 | 10 | The 'page' attribute can be described via the <jsp:attribute> standard action. | true |  | false | technology | active | true
JSP:SPEC:165 | 5 | 5 | The <jsp:forward> action will forward the current request to the target resource, be it a static resource, a JSP page, or a servlet class in the same context as the current page. | true |  | false | technology | active | true
JSP:SPEC:165.1 | 5 | 5 | The 'page' attribute specifies the target resource (either via a page relative or context relative path) to which to dispatch the current request to. | true |  | false | technology | active | true
JSP:SPEC:165.2 | 5 | 5 | The request object will be adjusted according to the value of the page attribute. | true |  | false | technology | active | false
JSP:SPEC:165.3 | 5 | 5 | If the page is buffered, the buffer is cleard prior to forwarding. | true |  | false | technology | active | true
JSP:SPEC:165.4 | 5 | 5 | If the page output is buffered, and the buffer was flushed, and attempt to forward the request will result in an IllegalStateException | true |  | false | technology | active | true
JSP:SPEC:165.5 | 5 | 5 | If the page output was unbuffered and anything has been written to it, an attempt to forward the request will result in an IllegalStateException. | true |  | false | technology | active | true
JSP:SPEC:165.6 | 5 | 5 | The forward action can accept <jsp:param> actions as body content to provide request parameters for the target resource. | true |  | false | technology | active | true
JSP:SPEC:165.7 | 5 | 5 | A translation error will occur of the 'page' attribute is omitted from the action. | true |  | false | technology | active | true
JSP:SPEC:165.8 | 5 | 5 | The 'page' attribute accepts request-time expressions (either classic RT or EL expressions). | true |  | false | technology | active | true
JSP:SPEC:165.9 | 5 | 10 | The 'page' attribute can be described via the <jsp:attribute> standard action. | true |  | false | technology | active | true
JSP:SPEC:166 | 5 | 6 | The <jsp:param> action specifies key/value information. | true |  | false | technology | active | true
JSP:SPEC:166.1 | 5 | 6 | The 'name' attribute specifies the name of the parameter. | true |  | false | technology | active | true
JSP:SPEC:166.2 | 5 | 6 | The 'value' attribute specifies the value for this particular parameter. | true |  | false | technology | active | true
JSP:SPEC:166.3 | 5 | 6 | A translation error will occur if the <jsp:param> action is not a child of a <jsp:include>, <jsp:forward>, <jsp:invoke>, <jsp:doBody>, or a <jsp:params> action. | true |  | false | technology | active | true
JSP:SPEC:166.4 | 5 | 6 | If used in conjunction with <jsp:include> the target resource will see the original request object including the augmented parameters provided by the <jsp:param> action, with the new parameters taking precendence over the originals. | true |  | false | technology | active | true
JSP:SPEC:166.10 | 5 | 6 | If used in conjunction with <jsp:forward>, the target resource will see the original request object including the augmented parameters provided by the <jsp:param> action, with the new parameters taking precendence over the originals. | true |  | false | technology | active | true
JSP:SPEC:166.5 | 5 | 6 | If used in conjuntion with <jsp:include> or <jsp:forward>, the new parameters will not apply after the action returns. | true |  | false | technology | active | true
JSP:SPEC:166.6 | 5 | 6 | The 'value' attribute can accept request-time (either classic RT or EL) expressions. | true |  | false | technology | active | true
JSP:SPEC:166.7 | 5 | 6 | A translation error will occur if either the 'name' or 'value' attributes is not specified. | true |  | false | technology | active | true
JSP:SPEC:166.8 | 5 | 10 | The 'value' attribute can be described via the <jsp:attribute> standard action. | true |  | false | technology | active | true
JSP:SPEC:166.9 | 5 | 10 | The 'name' attribute can be described via the <jsp:attribute> standard action. | true |  | false | technology | active | true
JSP:SPEC:167 | 5 | 7 | The <jsp:plugin> action enables an JSP page author to generate plugin re-lated HTML. | true |  | false | technology | active | false
JSP:SPEC:167.1 | 5 | 7 | Depending on the browser's user-agent, the action will generate either an HTML OBJECT or EMBED tag. | true |  | true | technology | active | true
JSP:SPEC:167.2 | 5 | 7 | The <jsp:params> action specifies a set of parameters (each parameter is defined by a one or more <jsp:param> actions). | true |  | false | technology | active | true
JSP:SPEC:167.2.1 | 5 | 7 | A translation error will occur of the <jsp:params> action is present, but contains no <jsp:param> sub-actions. | true |  | false | technology | active | true
JSP:SPEC:167.2.2 | 5 | 8 | A translation error will occur if the <jsp:params> action is used in any other context outside of the <jsp:plugin> action. | true |  | false | technology | active | true
JSP:SPEC:167.3 | 5 | 7 | The <jsp:fallback> attribute specifies alternate text if the plugin cannot be started. | true |  | false | technology | active | false
JSP:SPEC:167.3.1 | 5 | 7 | The alternate text generated by the <jsp:fallback> action is provided as body content. | true |  | false | technology | active | true
JSP:SPEC:167.3.2 | 5 | 11 | The body of the <jsp:fallback> attribute can be provided via the <jsp:body> action. | true |  | false | technology | active | true
JSP:SPEC:167.3.3 | 5 | 9 | The use of <jsp:fallback> in any other context (either independent action or child or another) will result in a translation error. | true |  | false | technology | active | true
JSP:SPEC:167.4 | 5 | 7 | The 'type' attribute will specifiy the type of component that will generally be either an applet or a Bean. | true |  | false | technology | active | true
JSP:SPEC:167.4.1 | 5 | 7 | A translation error will occur if a value other than 'bean' or 'applet' is provided to the action | true |  | false | technology | active | true
JSP:SPEC:167.5 | 5 | 7 | The 'code' attribute specifies the code attribute of the object per the HTML specification. | true |  | false | technology | active | true
JSP:SPEC:167.6 | 5 | 7 | The 'codebase' attribute specifies the codebase of the object per the HTML specification. | true |  | false | technology | active | true
JSP:SPEC:167.7 | 5 | 7 | The 'align' attribute provides the alignment of the object per the HTML specification. | true |  | false | technology | active | true
JSP:SPEC:167.8 | 5 | 7 | The 'archive' attribute provides the archive used by the object per the HTML specification. | true |  | false | technology | active | true
JSP:SPEC:167.9 | 5 | 7 | The 'height' attribute specifies the height of the object per the HTML specification | true |  | false | technology | active | true
JSP:SPEC:167.9.1 | 5 | 7 | The 'height' attribute accepts request-time (either classic RT or EL) expressions. | true |  | false | technology | active | true
JSP:SPEC:167.9.2 | 5 | 10 | The 'height' attribute can be described via the <jsp:attribute> standard action. | true |  | false | technology | removed | true
JSP:SPEC:167.10 | 5 | 7 | The 'hspace' attribute specifies the hspace of the object per the HTML specification. | true |  | false | technology | active | true
JSP:SPEC:167.11 | 5 | 7 | The 'jreversion' attribute specifies the version of JRE required for the object to fuction properly. | true |  | false | technology | active | true
JSP:SPEC:167.11.1 | 5 | 7 | If the 'jreversion' attribute is not specified, the default version present in the generated HTML will be "1.2". | true |  | false | technology | active | false
JSP:SPEC:167.12 | 5 | 7 | The 'name' attribute specifies the logical name for the embedded object per the HTML specification. | true |  | false | technology | active | true
JSP:SPEC:167.13 | 5 | 7 | The 'vspace' attribute specifies the vspace to be used by the embedded object per the HTML specification. | true |  | false | technology | active | true
JSP:SPEC:167.14 | 5 | 7 | The 'title' attribute specifies the title of the embedded object per the HTML specification. | true |  | false | technology | removed | true
JSP:SPEC:167.15 | 5 | 7 | The 'width' attribute specifies the width of the embedded object per the HTML specification. | true |  | false | technology | active | true
JSP:SPEC:167.15.1 | 5 | 7 | The 'width' attribute can accep request-time (either classic RT or EL) expressions. | true |  | false | technology | active | true
JSP:SPEC:167.15.2 | 5 | 10 | The 'width' attribute can be described via the <jsp:attribute> standard action. | true |  | false | technology | active | true
JSP:SPEC:167.16 | 5 | 7 | The 'nspluginurl' attribute specifies the URL where the JRE plugin can be downloaded for netscape. | true |  | false | technology | active | true
JSP:SPEC:167.16.1 | 5 | 7 | If the 'nspluginurl' attribute is not specified, the url returned in the generated HTML is implementation specific. | true |  | true | technology | active | false
JSP:SPEC:167.17 | 5 | 7 | The 'iepluginurl' attribute specifies the URL where the JRE plugin for IE can be downloaded. | true |  | false | technology | active | true
JSP:SPEC:167.17.1 | 5 | 7 | If the 'iepluginurl' attribute is not specified, the url returned in the generated HTML is implementation specific. | true |  | true | technology | active | false
JSP:SPEC:167.18 | 5 | 7 | A translation error will occur if the 'code' attribute is not specified. | true |  | false | technology | active | true
JSP:SPEC:167.19 | 5 | 7 | A translation error will occur if the 'codebase' attribute is not specified. | true |  | false | technology | active | true
JSP:SPEC:167.20 | 5 | 7 | All of the attributes of the jsp:plugin action can be described using the jsp:attribute action. | true |  | false | technology | active | true
JSP:SPEC:167.21 | 5 | 7 | The body of the jsp:params action can be provided using the jsp:body action. | true |  | false | technology | active | true
JSP:SPEC:168 | 5 | 10 | The <jsp:attribute> action allows a page author to define the value of a tag handler attribute in an XML element instead of in the value of the XML attribute. | true |  | false | technology | active | false
JSP:SPEC:168.1 | 5 | 10 | The 'name' attribute specifies the name of the attribute of the attribute for the tag being invoked. | true |  | false | technology | active | true
JSP:SPEC:168.1.1 | 5 | 10 | If the attribute does not accept dynamic attributes, and the specified attribute name doesn't exist in the surrounding action, a translation error will occur. | true |  | false | technology | active | true
JSP:SPEC:168.1.2 | 5 | 10 | A translation error will occur if both an XML element attribute and a <jsp:attribute> element are used to specify the value for the same attribute. | true |  | false | technology | active | true
JSP:SPEC:168.1.3 | 5 | 10 | A translation error will occur if the 'name' attribute is not specified. | true |  | false | technology | active | true
JSP:SPEC:168.1.4 | 5 | 10 | If the value provided to the 'name' attribute is a QName with a prefix that doesn't match that of the applicable action, and the action does not accept dynamic attributes, or the parent action is not jsp:element, a translation error will occur. | true |  | false | technology | active | true
JSP:SPEC:168.2 | 5 | 10 | Any attempt to use the <jsp:attribute> action outside of a JSP standard action, or a JSP custom action must result in a translation error. | true |  | false | technology | active | true
JSP:SPEC:168.3 | 5 | 10 | JSP containers must support the use of <jsp:attribute> for both Classic and Simple Tag Handlers. | true |  | false | technology | active | true
JSP:SPEC:168.4 | 5 | 10 | For custom action (both Classic and Simple) attribute types of type jakarta.servlet.jsp.tagext.JspFragment, the container must create a JspFragment out of the body of the <jsp:attribute> action and pass it to the tag handler. | true |  | false | technology | active | true
JSP:SPEC:168.5 | 5 | 10 | A translation error will occur if the attribute type is jakarta.servlet.jsp.tagext.JspFragment, and the body of the <jsp:attribute> action is not scriptless. | true |  | false | technology | active | true
JSP:SPEC:168.6 | 5 | 10 | If the custom action accepts dynamic attributes, and the name of the attribute is not one explicity indeicated for the tag, then the container will evaluate the body of <jsp:attribute> and assign the computed value to the attribute using the dynamic attribute machinery. | true |  | false | technology | active | true
JSP:SPEC:168.7 | 5 | 10 | For standard or custom actions attributes that accept a runtime expression value, the container must evaluate the body of the <jsp:attribute> action and use the result of theis evaluation as the value of the attribute. | true |  | false | technology | active | true
JSP:SPEC:168.8 | 5 | 10 | A translation error must occur if the body of the <jsp:attribute> action contains anything but template text when the standard or custom action attributes do not accept dynamic values. | true |  | false | technology | active | true
JSP:SPEC:168.9 | 5 | 10 | If the enclosing action is <jsp:element> then the values of the name attribute and the body of the attribute will be used to construct the element dynamically. | true |  | false | technology | active | true
JSP:SPEC:168.10 | 5 | 10 | If the body of the <jsp:attribute> is empty, it is the equivalent of specifying "" (an empty String) as the value of the attribute | true |  | false | technology | active | true
JSP:SPEC:168.11 | 5 | 10 | A translation-time error must occur if jsp:attribute is used to define the value of an attfibute of jsp:attribute. | true |  | false | technology | active | true
JSP:SPEC:168.12 | 5 | 10 | Attribute names must be accetped and have the appropriate attribute set when jsp:attribute specifies the attribute name using a QName. | true |  | false | technology | active | true
JSP:SPEC:168.13 | 5 | 10 | If the trim attribute is not specified, then by default, strings will be trimmed at translation time, and not at runtime. | true |  | false | technology | active | true
JSP:SPEC:168.14 | 5 | 10 | If the value of the trim attribute is true, strings will be trimmed at translation time, and not at runtime. | true |  | false | technology | active | true
JSP:SPEC:168.15 | 5 | 10 | If the value of the trim attribute is false, strings will not be trimmed at translation or runtime. | true |  | false | technology | active | true
JSP:SPEC:169 | 5 | 11 | The body of the <jsp:body> action can be specified via the <jsp:body> action. | true |  | false | technology | removed | true
JSP:SPEC:248 | 5 | 11 | The <jsp:body> allows for the explicit definition of a body for a custom action. | true |  | false | technology | removed | true
JSP:SPEC:248.1 | 5 | 11 | If one or more <jsp:attribute> elements appear in the body of a tag invocation but no <jsp:body> element appears or an empty <jsp:body> element appears, it is the equivalent of the tag having an empty body. | true |  | false | technology | active | true
JSP:SPEC:248.2 | 5 | 11 | It is illegal to use <jsp:body> to provide a body to the <jsp:body> and <jsp:attribute> actions. | true |  | false | technology | active | true
JSP:SPEC:248.3 | 5 | 11 | It is illegal for the <jsp:body> action to be present in a translation unit without a valid standard action or custom action as a parent. | true |  | false | technology | active | true
JSP:SPEC:170 | 5 | 11 | The <jsp:body> allows for the explicit definition of a body for a custom action. | true |  | false | technology | removed | true
JSP:SPEC:170.1 | 5 | 11 | The 'value' attribute allows the author to provide the body of the action as an attribute value. | true |  | false | technology | removed | true
JSP:SPEC:170.1.1 | 5 | 11 | The value of this attribute must evaluate to an instance of jakarta.servlet.jsp.tagext.JspFragment, otherwise a JspException must result. | true |  | false | technology | removed | true
JSP:SPEC:170.1.2 | 5 | 11 | If the 'value' attribute of <jsp:body> is specified and the action has a body, translation error must occur. | true |  | false | technology | removed | true
JSP:SPEC:170.1.3 | 5 | 11 | If the 'value' attribute of <jsp:body> is not specified, and the action has no body, a translation error must occur. | true |  | false | technology | removed | true
JSP:SPEC:170.1.4 | 5 | 11 | The 'value' attribute can accept dynamic attribute values (both EL and RT). | true |  | false | technology | removed | true
JSP:SPEC:170.2 | 5 | 11 | If the 'value' attribute is used to specify the value of a custom action defined using a Classic Tag Handler, the container must generate code to invoke the fragment, sending the output to the current JspWriter, and passing in a Map of paramters for all AT_BEGIN and NESTED variables provided by the tag handler. | true |  | false | technology | removed | true
JSP:SPEC:170.3 | 5 | 11 | Any attempt to use the value attribute to define the body of a standard action must result in a translation error. | true |  | false | technology | removed | true
JSP:SPEC:171 | 5 | 12 | The <jsp:invoke> action will invoke the specified fragment and write the result to the current JspWriter, or to a scoped variable. | true |  | false | technology | active | true
JSP:SPEC:171.1 | 5 | 12 | The 'fragment' attribute specifies the name used to identify this fragment during this tag invocation. | true |  | false | technology | active | true
JSP:SPEC:171.2 | 5 | 12 | The 'varReader' attribute specifies the scoped attribute in which to store the result of the fragment invocation. | true |  | false | technology | active | true
JSP:SPEC:171.2.1 | 5 | 12 | The type of the scoped attribute must be java.io.Reader. | true |  | false | technology | active | true
JSP:SPEC:171.3 | 5 | 12 | The 'var' attribute specifies the scoped attribute in which to store the result of the fragment invocation. | true |  | false | technology | active | true
JSP:SPEC:171.3.1 | 5 | 12 | The type of the scoped attribute must be java.lang.String. | true |  | false | technology | active | true
JSP:SPEC:171.4 | 5 | 12 | The 'scope' attribute specifies the scope in which to store the attribute specified by the 'varReader' or 'var' attributes. | true |  | false | technology | active | true
JSP:SPEC:171.4.1 | 5 | 12 | A value of 'page' will result in the attribute being stored in the page scope. | true |  | false | technology | active | true
JSP:SPEC:171.4.2 | 5 | 12 | A value of 'request' will result in the attribute being stored in the request scope. | true |  | false | technology | active | true
JSP:SPEC:171.4.3 | 5 | 12 | A value of 'session' will result in the attribute being stored in the session scope. | true |  | false | technology | active | true
JSP:SPEC:171.4.4 | 5 | 12 | A value of 'application' will result in the attribute being stroed in the application scope. | true |  | false | technology | active | true
JSP:SPEC:171.4.5 | 5 | 12 | If the 'scope' attribute is not specified, the default value of 'page' will be used. | true |  | false | technology | active | true
JSP:SPEC:171.4.6 | 5 | 12 | /XXX FIXME What happens if client not in session and session scope is specified. | true |  | false | technology | active | true
JSP:SPEC:171.4.7 | 5 | 12 | A translation error will occur if the scope attribute is provided an invalid value. | true |  | false | technology | active | true
JSP:SPEC:171.5 | 5 | 12 | A translation error will occur of the <jsp:invoke> is present outside of a tag file context. | true |  | false | technology | active | true
JSP:SPEC:171.6 | 5 | 12.2 | If neither 'var' nor 'varReader' attribute is specified, the result of the invocation will be written to the current JspWriter. | true |  | false | technology | active | true
JSP:SPEC:171.7 | 5 | 12.2 | When the 'varReader' attribute is specified, the object must produce the content sent by the fragment to the provided writer. | true |  | false | technology | active | true
JSP:SPEC:171.8 | 5 | 12.2 | When the 'var' attribute is specified, the object must store the content sent by the fragment in a String object. | true |  | false | technology | active | true
JSP:SPEC:171.9 | 5 | 12 | A translation error must occur of both 'var' and 'varReader' are specified within the same action. | true |  | false | technology | active | true
JSP:SPEC:171.10 | 5 | 12.2 | When 'varReader' attribute is specified, the Reader exported must be resettable, such that if its reset() method is called, the result of the invoked fragment must be able to be read again without re-executing the fragment. | true |  | false | technology | active | true
JSP:SPEC:171.11 | 5 | 12.3 | A translation error will occur if there is not a one-to-one correlation between the number of <jsp:param> elements present within the body of the <jsp:invoke> action and the required variables as defined by the 'variable' directive. | true |  | false | technology | removed | true
JSP:SPEC:171.12 | 5 | 12.3 | A translation error must not occur because a <jsp:param> element appears without a corresponding variable directive. | true |  | false | technology | active | true
JSP:SPEC:171.13 | 5 | 12.3 | A translation error will occur if the body of the <jsp:invoke> action contains body content other than white space and <jsp:param> subelements. | true |  | false | technology | active | true
JSP:SPEC:171.14 | 5 | 12 | A translation error will occur of the 'fragment' attribute is not specified for a particular <jsp:invoke> action. | true |  | false | technology | active | true
JSP:SPEC:172 | 5 | 13 | The <jsp:doBody> standard action invokes the body of a tag. | true |  | false | technology | active | true
JSP:SPEC:172.1 | 5 | 13 | The 'varReader' attribute specifies the scoped attribute in which to store the result of the body invocation. | true |  | false | technology | active | true
JSP:SPEC:172.1.1 | 5 | 13 | The type of the scoped attribute must be java.io.Reader. | true |  | false | technology | active | true
JSP:SPEC:172.2 | 5 | 13 | The 'var' attribute specifies the scoped attribute in which to store the result of the body invocation. | true |  | false | technology | active | true
JSP:SPEC:172.2.1 | 5 | 13 | The type of the scoped attribute must be java.lang.String. | true |  | false | technology | active | true
JSP:SPEC:172.3 | 5 | 13 | The 'scope' attribute specifies the scope in which to store the attribute specified by the 'varReader' attribute. | true |  | false | technology | active | true
JSP:SPEC:172.3.1 | 5 | 13 | A value of 'page' will result in the attribute being stored in the page scope. | true |  | false | technology | active | true
JSP:SPEC:172.3.2 | 5 | 13 | A value of 'request' will result in the attribute being stored in the request scope. | true |  | false | technology | active | true
JSP:SPEC:172.3.3 | 5 | 13 | A value of 'session' will result in the attribute being stored in the session scope. | true |  | false | technology | active | true
JSP:SPEC:172.3.4 | 5 | 13 | A value of 'application' will result in the attribute being stroed in the application scope. | true |  | false | technology | active | true
JSP:SPEC:172.3.5 | 5 | 13 | If the 'scope' attribute is not specified, the default value of 'page' will be used. | true |  | false | technology | active | true
JSP:SPEC:172.3.6 | 5 | 13 | /XXX FIXME What happens if client not in session and session scope is specified. | true |  | false | technology | active | true
JSP:SPEC:172.3.7 | 5 | 13 | A translation error will occur if the 'scope' attribute is provided an invalid value. | true |  | false | technology | active | true
JSP:SPEC:172.4 | 5 | 13 | A translation error will occur if the 'var' and 'varReader' attributes are both specified within the same action. | true |  | false | technology | active | true
JSP:SPEC:172.5 | 5 | 13 | A translation error will occur if the <jsp:doBody> action contains body content other than white space and <jsp:param> subelements. | true |  | false | technology | active | true
JSP:SPEC:172.6 | 5 | 12 | A translation error will occur if there is not a one-to-one correlation between the number of <jsp:param> elements present within the body of the <jsp:doBody> action and the required fragment inputs as defined by the 'variable' directive. | true |  | false | technology | removed | true
JSP:SPEC:172.7 | 5 | 12 | A translation error must not occur because a <jsp:param> element appears without a corresponding variable directive. | true |  | false | technology | active | true
JSP:SPEC:172.8 | 5 | 12 | A translation error must occur if a <jsp:param> is specified with the same name as a variable with a scope of AT_BEGIN, or NESTED. | true |  | false | technology | active | true
JSP:SPEC:172.9 | 5 | 12 | A translation error must not occur because a <jsp:param> is specified with the same name as a variable with a scope of AT_END. | true |  | false | technology | active | true
JSP:SPEC:173 | 6 | 1 | A JSP document is identified though the following algorithm in order or precedence: | true |  | false | technology | active | true
JSP:SPEC:173.1 | 6 | 1 | If a <jsp-property-group> explicitly identifies a set of files as JSP Documents (through the use of <is-xml>), then that indication overrides any other determination. | true |  | false | technology | active | true
JSP:SPEC:173.2 | 6 | 1 | If there is no explicit association and the extension is ".jspx", then the file is a JSP document. | true |  | false | technology | active | true
JSP:SPEC:173.3 | 6 | 1 | If the file is explicitly or implicitly defined as a JSP page and the top element is a jsp:root element, then the file is identified as a JSP doucment (provided for backwards compatibility). | true |  | false | technology | active | true
JSP:SPEC:173.4 | 6 | 1 | It is a translation error for a file that id identified as a JSP document to not be a well-formed XML document. | true |  | false | technology | active | true
JSP:SPEC:174 | 6 | 1 | RT expressions must be expressed in JSP Documents using the following syntax: "%= expr %". | true |  | false | technology | active | true
JSP:SPEC:174.1 | 6 | 1 | Whitespace after the starting '%=' and before the ending '%" is optional. | true |  | false | technology | active | true
JSP:SPEC:174.2 | 1 | 12.3 | If an expression appears in more than one run-time attribute, they are evaluated left-to-right in the element. | true |  | false | technology | active | true
JSP:SPEC:175 | 6 | 1 | It is legal to use any prefix for JSP standard actions within JSP documents as long as the require URI, 'http://java.sun.com/JSP/page" is associated with the specified prefix. | true |  | false | technology | active | true
JSP:SPEC:176 | 6 | 3.2 | JSP documents and tag files in XML syntax need not have a jsp:root element as its root element. | true |  | false | technology | active | true
JSP:SPEC:177 | 6 | 3.2 | The jsp:root element can only appear as the root element in a JSP document or in a tag file in XMLsyntax; otherwise a translation error shall occur. | true |  | false | technology | active | true
JSP:SPEC:178 | 6 | 1.4 | The jsp:directive.page, a child element of the jsp:root element, defines page level properties with the same semantics as the page directive in JSP syntax. | true |  | false | technology | active | true
JSP:SPEC:178.1 | 1 | 10.1 | jsp:directive.page can appear multiple times, and is position independent within a given translation unit. | true |  | false | technology | active | true
JSP:SPEC:178.2 | 1 | 10.1 | A translation error will occur if jsp:directive.page defines duplicate attribute/values within a given translation unit, with the exception of the import attribute. | true |  | false | technology | active | true
JSP:SPEC:178.3 | 1 | 10.1 | The 'isScriptingEnabled' attribute of jsp:directive.page, if true, allows the presence of scripting elements (scriptlets, expressions, declarations) within a given translation unit. | true |  | false | technology | active | true
JSP:SPEC:178.4 | 1 | 10.1 | The 'isScriptingEnabled' attribute of jsp:directive.page, if false, disallows the presence of scripting elements (scriptlets, expressions, declarations) within a given translation unit and will generate a translation error if they are present. | true |  | false | technology | active | true
JSP:SPEC:178.5 | 1 | 10.1 | The default value for 'isScriptingEnabled' of jsp:directive.page, if not specified, is true. | true |  | false | technology | active | true
JSP:SPEC:178.6 | 1 | 10.1 | The 'isELEnabled' attribute of jsp:directive.page, if true, directs the container to evaluate EL expressions. | true |  | false | technology | active | true
JSP:SPEC:178.7 | 1 | 10.1 | The 'isELEnabled' attribute of jsp:directive.page , if false, will result in EL expression not being evaluated by the container. | true |  | false | technology | active | true
JSP:SPEC:178.8 | 1 | 10.1 | If the JSP is part of a Web application that is using a Servlet 2.3 or lower deployment descriptor, the default value for the 'isELEnabled' attribute of jsp:directive.page is false. | true |  | false | technology | active | true
JSP:SPEC:178.9 | 1 | 10.1 | If the JSP is part of a Web application that is using a Servlet 2.4 deployment descriptor, the default value for the 'isELEnabled' attribute of jsp:directive.page is true. | true |  | false | technology | active | true
JSP:SPEC:178.10 | 1 | 10.1 | All scripting languages, specifiable by jsp:directive.page's 'language' attribute, must provide some implicit objects that a JSP page author can use in declarations, scriptlets, and expressions (see Section JSP.1.3.8 for list of available implicit objects) | true |  | true | technology | active | false
JSP:SPEC:178.11 | 1 | 10.1 | All scripting languages, specifiable by jsp:directive.page's 'language' attribute, must expose the Java technology object model to the script environment, especially implicit variables, JavaBeans components properties, and public methods. | true |  | true | technology | active | false
JSP:SPEC:178.12 | 1 | 10.1 | It is a fatal translation error for a page directive with a non-"java" language attribute to appear after the first scripting has been encountered. | true |  | false | technology | active | true
JSP:SPEC:178.13 | 1 | 10.1 | The only required scripting language value for the 'language' attribute is "java". | true |  | false | technology | active | true
JSP:SPEC:178.14 | 1 | 10.1 | The 'extends' attribute of jsp:directive.page specifies a fully qualified Java programming language class name, that names the superclass of the class to which this JSP page is transformed | true |  | false | technology | active | true
JSP:SPEC:178.15 | 1 | 10.1 | The 'import' attribute of jsp:directive.page specifies the fully qualified Java programming language type name denoting a particular type, or of a package name following by the ".*" string, denoting all the public types declared in that package, that shall be imorted by the translated JSP page implementation and is thus available to the scripting language. | true |  | false | technology | active | true
JSP:SPEC:178.16 | 1 | 10.1 | The default import list for a JSP page is java.lang.*, jakarta.servlet.*, jakarta.servlet.jsp.*, jakarta.servlet.http.* | true |  | false | technology | active | true
JSP:SPEC:178.17 | 1 | 10.1 | The 'session' attribute of jsp:directive.page, when true, indicates that the JSP page requires participation in an HTTP session. | true |  | false | technology | active | true
JSP:SPEC:178.18 | 1 | 10.1 | The 'session' attribute of jsp:directive.page, when false, indicates that the JSP page does not participate in an HTTP session; the 'session' implicit object is not available to the page, and any reference to it within the translation unit will result in a translation error. | true |  | false | technology | active | true
JSP:SPEC:178.19 | 1 | 10.1 | If the 'session' attribute of jsp:directive.page is not specified, then the page will, by default, participate in an HTTP session (default value of true). | true |  | false | technology | active | true
JSP:SPEC:178.20 | 1 | 10.1 | If the 'buffer' attribute of jsp:directive.page is not specified, no buffering will be performed and all output will be written directly through to the ServletResponse PrintWriter. | true |  | false | technology | active | true
JSP:SPEC:178.21 | 1 | 10.1 | The size value specified by the 'buffer' attribute of jsp:directive.page must be in kilobytes, and the suffix "kb" is mandatory. | true |  | false | technology | active | true
JSP:SPEC:178.22 | 1 | 10.1 | The container must allocate a buffer at least as large as that specified by the 'buffer' attribute of jsp:directive.page. | true |  | false | technology | active | true
JSP:SPEC:178.23 | 1 | 10.1 | The default buffer size of 8kb will be used if the 'buffer' attribute of the page directive is not specified. | true |  | false | technology | active | true
JSP:SPEC:178.24 | 1 | 10.1 | If the 'autoFlush' attribute of the page directive is true, the output will be automatically flushed when the buffer is filled. | true |  | false | technology | active | true
JSP:SPEC:178.25 | 1 | 10.1 | If the 'autoFlush' attribute of the page directive is false, an exception will be raised to indicate a buffer overflow. | true |  | false | technology | active | true
JSP:SPEC:178.26 | 1 | 10.1 | It is illegal to set the 'autoFlush' attribute of jsp:directive.page to false, if the 'buffer' attribute is set to none. | true |  | false | technology | active | true
JSP:SPEC:178.27 | 1 | 10.1 | If the 'isThreadSafe' attribute of jsp:directive.page is false, the container must serialize requests to the JSP (it should behave like an STM servlet). | true |  | false | technology | active | true
JSP:SPEC:178.28 | 1 | 10.1 | The 'info' attribute of jsp:directive.page specifies an arbitrary string that is incorporated into the translated page, that can subsequently be obtained from the page's implementation of Servlet.getServletInfo(). | true |  | false | technology | active | true
JSP:SPEC:178.29 | 1 | 10.1 | The 'isErrorPage' attribute of jsp:directive.page. when true, will cause the implicit script language variable "exception" to be defined and its value is a reference to the offending Throwable from the source JSP page in error. | true |  | false | technology | active | true
JSP:SPEC:178.30 | 1 | 10.1 | If the 'isErrorPage' attribute of jsp:directive.page is defined as false, then the implicit script language variable "exception" will not be available, and any such reference to this variable will result in a translation error. | true |  | false | technology | active | true
JSP:SPEC:178.31 | 1 | 10.1 | The 'errorPage' attribute of jsp:directive.page, specifies the URL, either page-relative or context-relative, of a resource to which any Java programming language Throwable object(s) thrown but not caught by the page implementation are forwarded for error processing. The following request attributes will be made available within the error page: | true |  | false | technology | active | true
JSP:SPEC:178.31.1 | 1 | 4.3 | jakarta.servlet.jsp.jspException - throw Throwable object of the offending exception (for backwards compatibility with JSP 1.2) | true |  | false | technology | active | true
JSP:SPEC:178.31.2 | 1 | 4.3 | jakarta.servlet.error.exception - as per the Servlet specification. | true |  | false | technology | active | true
JSP:SPEC:178.31.3 | 1 | 4.3 | jakarta.servlet.error.status_code - as per the Servlet specification | true |  | false | technology | active | true
JSP:SPEC:178.31.4 | 1 | 4.3 | jakarta.servlet.error.exception_type - as per the Servlet specification. | true |  | false | technology | active | true
JSP:SPEC:178.31.5 | 1 | 4.3 | jakarta.servlet.error.message - as per the Servlet specification. | true |  | false | technology | active | true
JSP:SPEC:178.31.6 | 1 | 4.3 | jakarta.servlet.error.request_uri - as per the Servlet specification. | true |  | false | technology | active | true
JSP:SPEC:178.31.7 | 1 | 4.3 | jakarta.servlet.error.servlet_name - as per the Servlet specification. | true |  | false | technology | active | true
JSP:SPEC:178.31.8 | 1 | 4.3 | An instance of jakarta.servlet.jsp.ErrorData must be provided to the error page. | true |  | false | technology | active | true
JSP:SPEC:178.32 | 1 | 10.1 | If the 'errorPage' attribute of jsp:directive.page is defined, it will take presendence over any error pages defined in the web application's deployment descriptor. | true |  | false | technology | active | true
JSP:SPEC:178.33 | 1 | 10.1 | The character encoding (Content-Type response header) can be in the form of TYPE, or TYPE; Charset=CHARSET, with an optional white space after the ';'. Charset, if present, must be the IANA value for a character encoding. Similarly, if TYPE is a MIME type, see the IANA registry for values. | true |  | false | technology | active | true
JSP:SPEC:178.34 | 1 | 10.1 | The default Content-Type for JSP Pages in XML syntax is "text/xml". | true |  | false | technology | active | true
JSP:SPEC:178.35 | 1 | 10.1 | If a charset portion of the value provided to the 'contentType' attribute is not specified, but the page encoding for the JSP page is specified, then the charset used will be that of the specified page encoding. | true |  | false | technology | active | true
JSP:SPEC:178.36 | 1 | 10.1 | If a charset is not provided as part of the 'contentType' attribute value, and the page encoding does not specifiy a type, then the default charset is ISO-8859-1 for JSP pages in classic syntax. | true |  | false | technology | active | true
JSP:SPEC:178.37 | 1 | 10.1 | If a charset is not provided as part of the 'contentType' attribute value, and the page encoding does not specifiy a type, then the default charset is UTF-8 for JSP pages in XML syntax. | true |  | false | technology | active | true
JSP:SPEC:178.38 | 1 | 10.1 | The 'pageEncoding' attribute of jsp:directive.page specifies the character encoding of the page. The value is in the form of CHARSET which my be the IANA value for a character encoding. If no 'pageEncoding' attribute is specified, the default of ISO-8859-1 will be used. | true |  | false | technology | active | true
JSP:SPEC:178.39 | 6 | 1.1 | A JSP container must support the presence of the jsp:directive.page element within a JSP page. | true |  | false | technology | active | true
JSP:SPEC:179 | 6 | 1.5 | The jsp:directive.include element, like the include directive, is used to subsitute test and/or code during JSP page translation and has the same semantics as the include directive for JSP pages. | true |  | false | technology | active | true
JSP:SPEC:179.1 | 6 | 1.5 | The jsp:directive:include element can appear anywhere within a JSP document. | true |  | false | technology | active | true
JSP:SPEC:179.2 | 1 | 10.5 | A JSP container can include a mechanism for being notified if an included file changes, so the container can recompile the JSP page. However, the JSP 2.0 specification does not have a way of directing the JSP container that included files have changed. | false |  | true | technology | active | false
JSP:SPEC:179.3 | 1 | 10.5 | The 'file' attribute of jsp:directive.include specifies the resource to be imported either relative to web appliation context path, or relative to the page performing the include. | true |  | false | technology | active | true
JSP:SPEC:179.4 | 1 | 10.5 | The jsp:directive.include element includes content at translation time meaning the bytes of the included resource are directly inserted into the page. | true |  | false | technology | active | true
JSP:SPEC:179.5 | 6 | 1.1 | A JSP container must support the presence of the jsp:directive.include element within a JSP page. | true |  | false | technology | active | true
JSP:SPEC:180 | 6 | 1.6 | The jsp:declaration element is used to declare scripting language constructs that are available to all other scripting elements and follows the same semantics as declarations in standard JSP syntax. | true |  | false | technology | active | true
JSP:SPEC:180.1 | 1 | 12.1 | A declaration (<jsp:declaration>DECL_BODY</jsp:declaration>) must be a complete declarative statment, or sequence thereof, according to the syntax of the scripting language specified, otherwise a translation error will occur. | true |  | false | technology | active | true
JSP:SPEC:180.2 | 1 | 12.1 | Declartaions do not produce any output into the current out stream. | true |  | false | technology | active | true
JSP:SPEC:180.3 | 1 | 12.1 | Declarations are initialized when the JSP page is initialized and are made available to other delcarations, scriptlets, and expressions. | true |  | false | technology | active | true
JSP:SPEC:180.4 | 6 | 1.1 | A JSP container must support the presence of the jsp:declaration element within a JSP page. | true |  | false | technology | active | true
JSP:SPEC:180.5 | 6 | 1.1 | A JSP container must support the presence of the jsp:declaration element within a JSP page. | true |  | false | technology | removed | true
JSP:SPEC:181 | 6 | 1.7 | The jsp:scriptlet element are program fragments with the same semantics as scriptlets in standard JSP syntax. | true |  | false | technology | active | true
JSP:SPEC:181.1 | 1 | 12.2 | Scriptlets (<jsp:scriptlet>SCR_BODY</jsp:scriptlet>) can contain any code framents that are valid for the scripting language specified by the 'language' attribute of the page directive, and are executed at request time in the order that they appear on the JSP page. | true |  | false | technology | active | true
JSP:SPEC:181.2 | 6 | 1.1 | A JSP container must support the presence of the jsp:scriptlet element within a JSP page. | true |  | false | technology | active | true
JSP:SPEC:182 | 6 | 1.8 | The jsp:expression element is used to describe complete expressions in the scripting language that get evaluated at response time. The semantics are the same as expressions in standard JSP syntax. | true |  | false | technology | active | true
JSP:SPEC:182.1 | 1 | 12.3 | The result of the expression is coerced to a String and emitted into the current JspWriter (out) object. | true |  | false | technology | active | true
JSP:SPEC:182.2 | 1 | 12.3 | If the result of the expression cannot be coerced to a String, the following must happen: If the problem is detected at translation time, a translation time error shall occur. If the coercion cannot be detected during translation, a ClassCaseException shall be raised at request time. | true |  | false | technology | active | false
JSP:SPEC:182.3 | 1 | 12.3 | Expressions are evaluated left to right in the JSP document. | true |  | false | technology | active | true
JSP:SPEC:182.4 | 1 | 12.3 | A translation error will occur if the expression is not a complete expression in the scripting language in which it is written. | true |  | false | technology | active | true
JSP:SPEC:182.5 | 6 | 1.1 | A JSP container must support the presence of the jsp:expression element within a JSP page. | true |  | false | technology | active | true
JSP:SPEC:183 | 6 | 1.9 | The jsp:element element is used to dynamically define an XML element | true |  | false | technology | active | true
JSP:SPEC:183.1 | 6 | 1.9 | The name of the element can be provided via the 'name' attribute. | true |  | false | technology | active | true
JSP:SPEC:183.2 | 6 | 1.9 | The value of the 'name' attribute can be provided via the jsp:attribute element. | true |  | false | technology | active | true
JSP:SPEC:183.3 | 6 | 1.9 | The body of the jsp:element element will be the body of the generated element. | true |  | false | technology | active | true
JSP:SPEC:183.4 | 6 | 1.9 | The body of the jsp:element element can be provided by the jsp:body element. | true |  | false | technology | active | true
JSP:SPEC:183.5 | 2 | 1.1 | JSP containers must support the presence of the jsp:element within standard JSP pages. | true |  | false | technology | active | true
JSP:SPEC:184 | 6 | 1.12 | The jsp:text element can be used to enclose template text that will be emitted to the current JspWriter (retaining any whitespace within the element). | true |  | false | technology | active | true
JSP:SPEC:184.1 | 6 | 1.1 | JSP contianer's must support the presence of jsp:text elements within standard JSP files. | true |  | false | technology | active | true
JSP:SPEC:185 | 6 | 1.13 | Any elements that are not standard or custom actions are to be passed to the current JspWriter after whitespace processing. | true |  | false | technology | active | true
JSP:SPEC:186 | 6 | 2.1 | The following steps must be taken by containers when converting a JSP document to it's internal XML view: | true |  | false | technology | active | false
JSP:SPEC:186.1 | 6 | 2.1 | Expand all include directives into the JSP framgments they include. | true |  | false | technology | active | true
JSP:SPEC:186.2 | 6 | 2.1 | Add the jsp:id attribute | true |  | false | technology | active | true
JSP:SPEC:187 | 6 | 2.2 | The following steps must be taken by a container to convert a JSP page into its XML view: | true |  | false | technology | active | true
JSP:SPEC:187.1 | 6 | 2.2 | Expand all include directives into the JSP framgments the include. | true |  | false | technology | active | true
JSP:SPEC:187.2 | 6 | 2.2 | Add a jsp:root element as the root, with appropriate xmlns:jsp attribute, and convert the taglib directive into xmlns:attributes of the jsp:root element. | true |  | false | technology | active | true
JSP:SPEC:187.3 | 6 | 2.2 | Convert declarations, scriptlets, and expressions into their equivalent XML forms. | true |  | false | technology | active | true
JSP:SPEC:187.3.1 | 5 | 2.7 | JSP declarations are translated into jsp:declaration elements. | true |  | false | technology | active | true
JSP:SPEC:187.3.2 | 5 | 2.8 | JSP scriptlets are translated into jsp:scriptlet elements. | true |  | false | technology | active | true
JSP:SPEC:187.3.3 | 6 | 2.9 | JSP expressions are translated into jsp:expression elements. | true |  | false | technology | active | true
JSP:SPEC:187.4 | 6 | 2.2 | Convert request-time attribute expressions into their equivalent XML forms. | true |  | false | technology | active | true
JSP:SPEC:187.5 | 6 | 2.2 | Convert JSP quotations to XML quitations. | true |  | false | technology | active | true
JSP:SPEC:187.6 | 6 | 2.2 | Create jsp:text elements for all template text. | true |  | true | technology | active | true
JSP:SPEC:187.7 | 6 | 2.2 | Add the jsp:id attribute. | true |  | false | technology | active | true
JSP:SPEC:187.8 | 6 | 2.3 | JSP comments (<%-- comment --%>) are not passed through to the XML view of a JSP page. | true |  | false | technology | active | true
JSP:SPEC:187.9 | 6 | 2.4 | JSP page directives are translated into <jsp:directive.page> elements. | true |  | false | technology | active | true
JSP:SPEC:187.10 | 5 | 2.5 | JSP taglib directives are translated into xmlns:prefix attributes of the jsp:root element. | true |  | false | technology | active | true
JSP:SPEC:260 | 6 | 2.4 | A JSP Document with a DOCTYPE declaration must be validated by the container in the translation phase. Validation errors must be handled the same way as any other translation phase errors, as described in Section JSP.1.4.1. | true |  | false | technology | active | true
JSP:SPEC:188 | 6 | 2.13 | As of JSP 2.0, the JSP container must support the jsp:id attribute which is only present in the XML view of a JSP page to improve the quality of translation time errors. | true |  | false | technology | active | true
JSP:SPEC:189 | 7 | 1.4.7 | Scripting variables can be defined in one of two ways: | true |  | false | technology | active | true
JSP:SPEC:189.1 | 7 | 1.4.7 | Directly within the TLD for a particular action via the <variable> element. | true |  | false | technology | active | true
JSP:SPEC:189.2 | 7 | 1.4.7 | Using a subclass of the TagExtraInfo interface, specifically providing a method body to the getVariableInfo() call. | true |  | false | technology | active | true
JSP:SPEC:301 | 7 | 1.5 | The <body-content> of a SimpleTag cannot be "JSP". [BodyContentSimpleTagNotJsp] | true |  | false | technology | active | true
JSP:SPEC:190 | 7 | 1.6 | A translation error must occur if a piece of JSP code that is to be translated into a JSPFragment (any JSP code in the body of a named attribute (<jsp:attribute), that is declared to be a fragment in the TLD, or for the body of any tag handled by a Simple Tag Handler). | true |  | false | technology | active | true
JSP:SPEC:191 | 7 | 1.9 | A tag library can define listener classes (See Servlet.2.4 specification) which will be instantiated and registered by the JSP container. | true |  | false | technology | active | true
JSP:SPEC:192 | 7 | 1.9 | Listeners must be instantiated before the start of the application, however, the order in which listeners are registered is undefined. | true |  | true | technology | active | false
JSP:SPEC:302 | 7 | 1.11 | Tag handlers which implement interfaces jakarta.servlet.jsp.tagext.Tag and jakarta.servlet.jsp.tagext.SimpleTag may be annotated for injection. [TagHandlerResourceInjection] | true |  | false | technology | active | true
JSP:SPEC:303 | 7 | 1.11 | Resource injection occurs immediately after an instance of a tag handler is constructed, and before any of the tag properties are initialized. [TagHandlerResourceInjectionTiming] | true |  | false | technology | active | true
JSP:SPEC:304 | 7 | 1.11 | Event Listeners can be annotated for resource injection. [EventListenerResourceInjection] | true |  | false | technology | active | true
JSP:SPEC:305 | 7 | 1.11 | Resource injection occurs immediately after an instance of an event handler is constructed, and before it is registered. [EventListenerResourceInjectionTiming P1] | true |  | false | technology | active | true
JSP:SPEC:193 | 7 | 2.1 | When tag libraries are deployed in a JSP container as a JAR file, the standard JAR conventions described in the Servlet 2.4 specification apply, including the conventions for dependencies on extensions. | true |  | false | technology | active | true
JSP:SPEC:194 | 7 | 2.1 | Packaged tag libraries must have at least one tag library descript file. | true |  | false | technology | active | false
JSP:SPEC:195 | 7 | 2.1 | Both classic and simple tag handlers (implemented in either Java or as tag files) can be packaged together in the same JAR file. | true |  | false | technology | active | true
JSP:SPEC:196 | 7 | 2.3 | If a JSP container cannot locate a TLD resource path for a given URI, a fatal translation error shall result. | true |  | false | technology | active | true
JSP:SPEC:197 | 7 | 2.3 | If the URI resolves to two different TLD resource paths, a translation error will occur. | true |  | false | technology | active | true
JSP:SPEC:198 | 7 | 3.1 | A TLD must end with the extension ".tld" to be recognized by the container. | true |  | false | technology | active | true
JSP:SPEC:199 | 7 | 3.1 | When taglibraries are deployed in a JAR file, the TLDs must be present in the META-INF directory in order to be recognized by the container. | true |  | false | technology | active | true
JSP:SPEC:200 | 7 | 3.1 | When deployed directly in the web application, the TLD's must be be in the WEB-INF directory, or some subdirectory thereof. | true |  | false | technology | active | true
JSP:SPEC:201 | 7 | 3.1 | A translation error will occur if the TLD resource path doesn't ultimately resolve directly to a TLD within the web application, or to a JAR file that has the taglib.tld file in the META-INF directory of the JAR. | true |  | false | technology | active | true
JSP:SPEC:306 | 7 | 3.1 | TLD files must not be placed inside /WEB-INF/tags or a subdirectory of it, unless named implicit.tld and intended to configure an implicit tag library with its JSP version and tlib-version. [TldPlacementInWEB-INFtags] | true |  | false | technology | active | true
JSP:SPEC:202 | 7 | 3.3 | Explicit taglib map entries between URI's and TLD resource paths can be described using taglib elements of the Web Application Deployment descriptor (web.xml). | true |  | false | technology | active | true
JSP:SPEC:203 | 7 | 3.4 | Implicit taglib map entries can be described via a TLD file(s) located in the META-INF directory of the JAR file (TLD is not named taglib.tld). | true |  | false | technology | active | true
JSP:SPEC:203.1 | 7 | 3.4 | Each TLD file is examined. If it has a <uri> element, then a new <taglib> element is created, with a <taglib-uri> subelement whose value is that of the <uri> element, and with a <taglib-location> subelement that refers to the TLD file. | true |  | false | technology | active | true
JSP:SPEC:203.2 | 7 | 3.4 | If the created <taglib> element has a different <taglib-uri> to any in the taglib map, it is added to the map. | true |  | false | technology | active | true
JSP:SPEC:204 | 7 | 3.9 | The JSP container may "know of" some specific URIs and may provide alternate implementations for the tag libraries described by these URI's. | true |  | true | technology | active | false
JSP:SPEC:204.1 | 7 | 3.9 | When the container does provide an alternate implementation, the implementation must provide the same behavior as that described by the required, portable tag library description described by the URI. | true |  | true | technology | active | false
JSP:SPEC:204.2 | 7 | 3.9 | A JSP container must always use the mapping specified for a URI in the web.xml deployment descriptor if present. If the deployer wishes to use the platform-specific implementation of the well-known URI, the mapping for that URI should be removed at deployment time. | true |  | true | technology | active | false
JSP:SPEC:205 | 7 | 3.6.1 | The <taglib-uri> element may be URI of the following types: | true |  | false | technology | active | true
JSP:SPEC:205.1 | 7 | 3.6.1 | An absolute URI. | true |  | false | technology | active | true
JSP:SPEC:205.2 | 7 | 3.6.1 | A context-relative URI (URI starting with '/'). | true |  | false | technology | active | true
JSP:SPEC:205.3 | 7 | 3.6.1 | A page-relative URI (URI that doesn't start with '/'). | true |  | false | technology | active | true
JSP:SPEC:206 | 7 | 3.6.1 | If the <taglib-location> sublement is a relative URI without a leading slash, the resolution of the taglib location will be relative to /WEB-INF. | true |  | false | technology | active | true
JSP:SPEC:206.1 | 7 | 3.6.1 | The result of the resolution will be a context-relative path (starts with "/"). | true |  | false | technology | active | false
JSP:SPEC:207 | 7 | 3.6.2 | The following describes the resolution process of the taglib directive to compute the TLD resource path. | true |  | false | technology | active | true
JSP:SPEC:207.1 | 7 | 3.6.2 | If the URI is an absolute URI, check the taglib map for an entry whose URI is the specified absolute URI. If found, the corresponding taglib location is the TLD resource path. The taglib will be usable in the page. | true |  | false | technology | active | true
JSP:SPEC:207.2 | 7 | 3.6.2 | If the absolute URI is not found in the taglib map, a translation error will occur. | true |  | false | technology | active | true
JSP:SPEC:207.3 | 7 | 3.6.2 | If the URI is a context-relative path (URI starts with '/'), look in taglib amp for an entry whose taglib URI matchs the provided URI. If found, the corresponding location is the TLD resource path. The tag library will be available to the page | true |  | false | technology | active | true
JSP:SPEC:207.4 | 7 | 3.6.2 | If the context-relative URI is not found in the taglib map, then the URI provided by the taglib directive is the TLD resource path. | true |  | false | technology | active | true
JSP:SPEC:207.5 | 7 | 3.6.2 | If at translation time, the resource (either a TLD or a JAR where taglib.tld is in the META-INF directory) doesn't exist as specified by the provided context-relative path, a translation error will occur. | true |  | false | technology | active | true
JSP:SPEC:207.6 | 7 | 3.6.2 | If the URI is a page-relative path (the URI doesn't start with a '/') look in the taglib map for the same page-relative path. If found, the corresponding taglib location in the map is the TLD resource path. The tag library will be available to the page. | true |  | false | technology | active | true
JSP:SPEC:207.7 | 7 | 3.6.2 | If the page-relative URI is not found in the taglib map, resolve the page relative path to the current JSP page where the directive appears. This will be used as the TLD resource path. If the resource is found at the resolved location, the tag library will be available to the page. | true |  | false | technology | active | true
JSP:SPEC:207.8 | 7 | 3.6.2 | If, at translation time, the resource identified by the resolved page-relative path doesn't exist (either a TLD or a JAR file with a taglib.tld in META-INF), a translation error will occur. | true |  | false | technology | active | true
JSP:SPEC:208 | 7 | 3.10 | JSP containers must not alter their behavior based on the content, the presence, or the absence of a particular Tag or Tag Library Extension Element. | true |  | false | technology | active | true
JSP:SPEC:209 | 7 | 3.10 | JSP containers must consider invalid any tag library that specifies mustUnderstand='true' for any Tag or Tag Library Extension element. | true |  | false | technology | active | false
JSP:SPEC:210 | 7 | 4.1.1 | All attribute constraints as described in the TLD must be enforced by the container. | true |  | false | technology | active | true
JSP:SPEC:211 | 8 | 3 | The following must hold true for all tag handlers defined as tag files: | true |  | false | technology | active | true
JSP:SPEC:211.1 | 8 | 3 | The tag file implementation must keep a copy of the JspContext instance passed to it by the invoking page via setJspContext(). This is called the 'Invoking JSP Context'. | true |  | false | technology | active | true
JSP:SPEC:211.2 | 8 | 3 | The tag file implementation must create and maintain a second instance of JspContext called a 'JSP Context Wrapper'. If the Invoking JSP Context is an instance of PageContext, the JSP Context Wrapper must also be an instance of PageContext. | true |  | false | technology | active | true
JSP:SPEC:211.3 | 8 | 3 | For each invocation of the tag, the JSP Context Wrapper must present a clean page scope containing no initial elements. | true |  | false | technology | active | true
JSP:SPEC:211.4 | 8 | 3 | All scopes other than the page scope must be identical to this in the Invoking JSP Context and must be modified accordingly when updates are made to those scopes in the JSP Context Wrapper. | true |  | false | technology | active | true
JSP:SPEC:211.5 | 8 | 3 | Any modifications to the page scope, however, must not affect the Invoking JSP Context. | true |  | false | technology | active | true
JSP:SPEC:211.6 | 8 | 3 | For each attribute declared and specified, a page-scoped variable must be created in the page scope of the JSP Context Wrapper. | true |  | false | technology | active | true
JSP:SPEC:211.7 | 8 | 3 | The name of the variable must be the same as the declared attribute name. | true |  | false | technology | active | true
JSP:SPEC:211.8 | 8 | 3 | The value of the variable must be the value of the attribute passed in during invocation. | true |  | false | technology | active | true
JSP:SPEC:211.9 | 8 | 3 | For each attribute declared as optional and not specified, no page-scoped variable is created. | true |  | false | technology | active | true
JSP:SPEC:211.10 | 8 | 3 | If the tag accepts dynamic attributes, then page-scoped variables must also be made available for each dynamic attribute passed in. | true |  | false | technology | active | true
JSP:SPEC:211.11 | 8 | 3 | The 'pageContext' scripting variable must point to the JSP Context Wrapper instead of the Invoking JSP Context | true |  | false | technology | active | true
JSP:SPEC:211.12 | 8 | 3 | The tag handler must behave as through a tag library descriptor entry was defined for it, in accordance with the tag, attribute, and variable directives that appear in the tag file translation unit. | true |  | false | technology | active | true
JSP:SPEC:212 | 8 | 3 | If <jsp:forward> is used within a tag file, the generated tag handler must stop processing upon the return of RequestDispatcher.forward() and throw a jakarta.servlet.jsp.SkipPageException | true |  | false | technology | active | true
JSP:SPEC:213 | 8 | 3 | If a tag file invokes a Classic Tag Handler which returns SKIP_PAGE, from doEndTag() , tag file must terminate and SkipPageException must be thrown. | true |  | false | technology | active | true
JSP:SPEC:214 | 8 | 3 | If a tag file invokes a Classic Tag Handler invokes a a Simple Tag Handler which throws SkipPageException, the tag file must terminate and SkipPageException must be thrown. | true |  | false | technology | active | true
JSP:SPEC:215 | 8 | 3 | If a tag file invokes a Simple Tag Handler which throws a SkipPageException, processing must terminate with the tag file throwing a SkipPageException | true |  | false | technology | active | true
JSP:SPEC:216 | 8 | 3 | In the case of either Simple or Classic Tag Handlers, the doFinally() method must be called on enclosing tags that implement the TryCatchFinally interface before returning. | true |  | false | technology | active | true
JSP:SPEC:217 | 8 | 3 | The doEndTag() methods of enclosing classic tags must not be called when SkipPageException is thrown. | true |  | false | technology | active | true
JSP:SPEC:218 | 8 | 3 | When a tag file attempts to invoke a classic tag handler (i.e one that implements the Tag interface), it must cast the JspContext passed to the SimpleTag into a PageContext | true |  | false | technology | active | true
JSP:SPEC:219 | 8 | 3 | If the cast by a Simple Tag Handler of a JspContext to a PageContext fails, the invocation of the classic tag files, and a JspException must be thrown. | true |  | false | technology | active | false
JSP:SPEC:220 | 8 | 4.1 | Tag files can be packaged in the /META-INF/tags directory of a JAR file installed in the /WEB-INF/lib directory. | true |  | false | technology | active | true
JSP:SPEC:220.1 | 8 | 4.2 | Any tag files packaged in a JAR file must have a Tag Library Descriptor (TLD) present within the JAR file with a reference for each tag that is to be recognized by the container in the TLD. | true |  | false | technology | active | true
JSP:SPEC:220.2 | 8 | 4.2 | Any tag files within a JAR file that are not defined within a TLD must be ignored by the container. | true |  | false | technology | active | true
JSP:SPEC:220.3 | 8 | 4.2 | A tag library is considered invalid and must be rejected by the container if a <tag-file> element has a <name> subelement with the same content as a <name> subelement in a <tag> element. | true |  | false | technology | active | false
JSP:SPEC:314 | 8 | 4.2 | Tag files packaged in a JAR inherit the JSP version of the TLD that references them. [JspVersionInheritanceInJarPackagedTagFiles] | true |  | false | technology | active | true
JSP:SPEC:221 | 8 | 4.3 | Tag files can be packaged in the /WEB-INF/tags/ directory of a web application or a subdirectory thereof. | true |  | false | technology | active | true
JSP:SPEC:221.1 | 8 | 4.3 | The JSP container must interpret the '/WEB-INF/tags/' directory and each subdirectory under it, as another implicitly defined tag library containing tag handlers defined by the tag files that appear in the directory. | true |  | false | technology | active | true
JSP:SPEC:221.2 | 8 | 4.3 | The JSP container must generate an implicit tag library for each directory under and included /WEB-INF/tags/. | true |  | false | technology | active | true
JSP:SPEC:221.3 | 8 | 4.3 | The tag library can only be imported via the tagdir attribute of the taglib directive. | true |  | false | technology | active | true
JSP:SPEC:221.3.1 | 8 | 4.3 | The <tlib-version> element will be defined as 1.0 | true |  | false | technology | active | false
JSP:SPEC:221.3.2 | 8 | 4.3 | <short-name> is derived from the directory name that that tag file resides in. | true |  | false | technology | active | false
JSP:SPEC:221.3.2.1 | 8 | 4.3 |  | true |  | false | technology | removed | false
JSP:SPEC:221.3.3 | 8 | 4.3 | The <tag-file> element is considered to exist for each tag file in this directory. | true |  | false | technology | active | false
JSP:SPEC:221.3.3.1 | 8 | 4.3 | The <name> for each is the filename of the tag file, withouth the .tag extension | true |  | false | technology | active | true
JSP:SPEC:221.3.3.2 | 8 | 4.3 | The <path> element for each is the path of the tag file, relative to the root of the web application. | true |  | false | technology | active | false
JSP:SPEC:307 | 8 | 4.3 | The JSP version of an implicit tag library defaults to 2.0. [ImplicitTldDefaultJspVersion] | true |  | false | technology | active | true
JSP:SPEC:308 | 8 | 4.3 | The JSP version and tlib-version of an implicit tag library may be configured by placing a TLD with the reserved name implicit.tld in the same directory as the implicit tag library?s constituent tag files. [ImplicitTldReservedName] | true |  | false | technology | active | true
JSP:SPEC:309 | 8 | 4.3 | A JSP 2.1 container must consider only the JSP version and tlib-version specified by an implicit.tld file, and ignore its short-name element. [ImplicitTldVersionInfo] | true |  | false | technology | active | true
JSP:SPEC:310 | 8 | 4.3 | Any elements in addition to jsp-version, tlib-version, and short-name in an implicit.tld file must cause a translation error. [ImplicitTldAdditionalElements] | true |  | false | technology | active | true
JSP:SPEC:311 | 8 | 4.3 | The JSP version specified in an implicit.tld file must be equal to or greater than 2.0, or else a translation error must be reported. [ImplicitTldMinimumJspVersion] | true |  | false | technology | active | true
JSP:SPEC:222 | 8 | 4.3 | Upon deployment, the JSP container must seach for and process all tag files appearing in these directories and subdirectories. In processing a tag file, the container makes the custom actions defined in these tags available to JSP files. | true |  | false | technology | active | true
JSP:SPEC:312 | 8 | 4.3 | If a tag library directory contains two files with the same tag name, the tag library is considered invalid. [TwoFilesSameTagName] | true |  | false | technology | active | true
JSP:SPEC:313 | 8 | 4.3 | It a tag file is referenced by both a TLD as well as an implicit TLD, the JSP versions of the TLD and implicit TLD do not need to match. [TldImplicitTldJspVersionNotMatch] | true |  | false | technology | active | true
JSP:SPEC:223 | 8 | 5 | A translation error will occur of a page directive is present within a tag file. | true |  | false | technology | active | true
JSP:SPEC:224 | 8 | 5 | The taglib directive is legal within Tag files. The semantics of the taglib directive within a tag file are identical to those of a JSP page. | true |  | false | technology | active | true
JSP:SPEC:225 | 8 | 5 | The include directive is legal within Tag files. The semantics of the include directive within a tag file are identical to those of a JSP page. | true |  | false | technology | active | true
JSP:SPEC:225.1 | 8 | 5 | If the included file contains syntax unsuitable for tag files, a translation error will occur. | true |  | false | technology | active | true
JSP:SPEC:226 | 8 | 5 | The tag directive is only applicable to tag files. Any attempt to use the tag directive in a JSP page will result in a translation error. | true |  | false | technology | active | true
JSP:SPEC:227 | 8 | 5 | The attribute directive is only applicable to tag files. Any attempt to use the attribute directive in a JSP page will result in a translation error. | true |  | false | technology | active | true
JSP:SPEC:228 | 8 | 5 | The variable directive is only applicable to tag files. Any attempt to use the variable directive in a JSP page will result in a translation error. | true |  | false | technology | active | true
JSP:SPEC:229 | 8 | 5.1 | The 'tag' directive is similar to the page directive, but applied to tag files instead of JSP's. | true |  | false | technology | active | true
JSP:SPEC:229.1 | 8 | 5.1 | A translation unit can container more than one instance of the tag directive, all the attributes will apply to the complete translation unit (i.e. tag directives are position independent). | true |  | false | technology | active | true
JSP:SPEC:229.2 | 8 | 5.1 | Unrecoginized attributes or values will result in a fatal translation error. | true |  | false | technology | active | true
JSP:SPEC:229.3 | 8 | 5.1 | The 'display-name' attribute provides a short name that is intended to be displayed by tools. | true |  | false | technology | active | true
JSP:SPEC:229.4 | 8 | 5.1 | Multiple 'display-name' attribute/value (re)definitions will result in a translation error if values do not match. | true |  | false | technology | active | true
JSP:SPEC:229.5 | 8 | 5.1 | The 'body-content' attribute specifies the body content of this tag. | true |  | false | technology | active | true
JSP:SPEC:229.5.1 | 8 | 5.1 | A valid value is 'empty' meaning no body. | true |  | false | technology | active | true
JSP:SPEC:229.5.2 | 8 | 5.1 | A valid value is 'tagdependent'. | true |  | false | technology | active | true
JSP:SPEC:229.5.3 | 8 | 5.1 | A valid value is 'scriptless' | true |  | false | technology | active | true
JSP:SPEC:229.5.4 | 8 | 5.1 | If the 'body-content' attribute is not specified, it will default to 'scriptless' | true |  | false | technology | active | true
JSP:SPEC:229.5.5 | 8 | 5.1 | Any other value provided to the 'body-content' attribute aside from 'empty', 'tagdependent', or 'scriptless' will result in a translation error. | true |  | false | technology | active | true
JSP:SPEC:229.6 | 8 | 5.1 | Multiple 'body-content' attribute/value (re)definitions will result in a translation error if values do not match. | true |  | false | technology | active | true
JSP:SPEC:229.7 | 8 | 5.1 | The 'dynamic-attributes' attribute indicates whether this tag supports additional attributes with dynamic names. | true |  | false | technology | active | true
JSP:SPEC:229.7.1 | 8 | 5.1 | If 'true', the generated tag handler must implement the jakarta.servlet.jsp.tagext.DynamicAttributes interface. | true |  | false | technology | active | true
JSP:SPEC:229.7.2 | 8 | 5.1 | If 'false' the generated tag handler will not implement the jakarta.servlet.jsp.tagext.DynamicAttributes interface. | true |  | false | technology | active | true
JSP:SPEC:229.7.3 | 8 | 5.1 | The default value is 'false'. | true |  | false | technology | active | false
JSP:SPEC:229.7.4 | 8 | 5.1 | If any values are provided to the 'dynamic-attributes' attribute aside from 'true' or 'false' a translation error will occur. | true |  | false | technology | active | true
JSP:SPEC:229.8 | 8 | 5.1 | Multiple 'dyanmic-attribute' attribute/value (re)definitions will result in a translation error if values do not match. | true |  | false | technology | active | true
JSP:SPEC:229.9 | 8 | 5.1 | The 'small-icon' attribute specifies a relative path, from the tag source file, of an image file containg a small icon that can be used by tools. | true |  | false | technology | active | true
JSP:SPEC:229.9.1 | 8 | 5.1 | If the 'small-icon' attribute is not specified, no icon will be used. | true |  | false | technology | active | false
JSP:SPEC:229.10 | 8 | 5.1 | Multiple 'small-icon' attribute/value (re)definitions will result in a translation error if values do not match. | true |  | false | technology | active | true
JSP:SPEC:229.11 | 8 | 5.1 | The 'large-icon' attribute specifies a relative path from the tag source file, of an image file containing a large icon that can be used by tools. | true |  | false | technology | active | true
JSP:SPEC:229.11.1 | 8 | 5.1 | If the 'large-icon' attribute is not specified, no icon will be used. | true |  | false | technology | active | false
JSP:SPEC:229.12 | 8 | 5.1 | Multiple 'large-icon' attribute/value (re)definitions will result in a translation error if values do not match. | true |  | false | technology | active | true
JSP:SPEC:229.13 | 8 | 5.1 | The 'description' attribute provides an arbitrary string that describes this tag. | true |  | false | technology | active | true
JSP:SPEC:229.13.1 | 8 | 5.1 | If the 'description' attribute is not specified, no description will be available. | true |  | false | technology | active | false
JSP:SPEC:229.14 | 8 | 5.1 | Multiple 'description' attribute/value (re)definitions will result in a translation error if values do not match. | true |  | false | technology | active | true
JSP:SPEC:229.15 | 8 | 5.1 | The 'example' attribute defines an arbitraty string describing the use of this action. | true |  | false | technology | active | true
JSP:SPEC:229.15.1 | 8 | 5.1 | If the 'example' attribute is not specified, no example string will be available. | true |  | false | technology | active | false
JSP:SPEC:229.16 | 8 | 5.1 | Multiple 'example' attribute/value (re)definitions will result in a translation error if values do not match. | true |  | false | technology | active | true
JSP:SPEC:229.17 | 8 | 5.1 | The 'language' attribute specifies the scripting language used by the tag file. | true |  | false | technology | active | true
JSP:SPEC:229.17.1 | 1 | 10.1 | All scripting languages, specifiable by the tag directive's 'language' attribute, must provide some implicit objects that a JSP page author can use in declarations, scriptlets, and expressions (see Section JSP.1.3.8 for list of available implicit objects) | true |  | true | technology | active | false
JSP:SPEC:229.17.2 | 1 | 10.1 | All scripting languages, specifiable by the tag directive's 'language' attribute, must expose the Java technology object model to the script environment, especially implicit variables, JavaBeans components properties, and public methods. | true |  | true | technology | active | false
JSP:SPEC:229.17.3 | 1 | 10.1 | It is a fatal translation error for a tag directive with a non-"java" language attribute to appear after the first scripting has been encountered. | true |  | false | technology | active | true
JSP:SPEC:229.17.4 | 1 | 10.1 | The only required scripting language value for the 'language' attribute is "java". | true |  | false | technology | active | true
JSP:SPEC:229.18 | 8 | 5.1 | Multiple 'language' attribute/value (re)definitions will result in a translation error if values do not match. | true |  | false | technology | active | true
JSP:SPEC:229.19 | 8 | 5.1 | The 'import' attribute of the tag directive specifies the fully qualified Java programming language type name denoting a particular type, or of a package name following by the ".*" string, denoting all the public types declared in that package, that shall be imorted by the translated JSP page implementation and is thus available to the scripting language. | true |  | false | technology | active | true
JSP:SPEC:229.19.1 | 1 | 10.1 | The default import list for a tag is java.lang.*, jakarta.servlet.*, jakarta.servlet.jsp.*, jakarta.servlet.http.* | true |  | false | technology | active | true
JSP:SPEC:229.19.2 | 8 | 5.1 | multiple uses of this attribute are cumulative (with ordered set union semantics). | true |  | false | technology | active | true
JSP:SPEC:229.20 | 8 | 5.1 | The 'pageEncoding' attribute of the tag directive specifies the character encoding of the tag. The value is in the form of CHARSET which my be the IANA value for a character encoding. If no 'pageEncoding' attribute is specified, the default of ISO-8859-1 will be used. | true |  | false | technology | active | true
JSP:SPEC:229.21 | 8 | 5.1 | Multiple 'pageEncoding' attribute/value (re)definitions will result in a translation error. | true |  | false | technology | active | true
JSP:SPEC:229.22 | 8 | 5.1 | The 'pageEncoding' attribute of the tag directive is not influenced at all by any global configuration present in the web.xml | true |  | false | technology | active | true
JSP:SPEC:229.23 | 8 | 5.1 | The 'isScriptingEnabled' attribute specified whether scripting elements are legal within the tag file. | true |  | false | technology | active | true
JSP:SPEC:229.23.1 | 1 | 10.1 | The 'isScriptingEnabled' attribute of the tag directive, if false, disallows the presence of scripting elements (scriptlets, expressions, declarations) within a given translation unit and will generate a translation error if they are present. | true |  | false | technology | active | true
JSP:SPEC:229.23.2 | 1 | 10.1 | The default value for 'isScriptingEnabled' of the tag directive, if not specified, is true. | true |  | false | technology | active | true
JSP:SPEC:229.23.3 | 8 | 5.1 | Any value other than 'true' or 'false' provided to the 'isScriptingEnabled' attribute will result in a translation error. | true |  | false | technology | active | true
JSP:SPEC:229.24 | 8 | 5.1 | Multiple 'isScriptingEnabled' attribute/value (re)definitions will result in a translation error if values do not match. | true |  | false | technology | active | true
JSP:SPEC:229.25 | 8 | 5.1 | The 'isELEnabled' attribute of the tag directive specifies whether or not the container should evaluate EL expressions. | true |  | false | technology | active | true
JSP:SPEC:229.25.1 | 1 | 10.1 | The 'isELEnabled' attribute of the page directive , if false, will result in EL expressions not being evaluated by the container. | true |  | false | technology | active | true
JSP:SPEC:229.25.2 | 1 | 10.1 | The default value, if 'isELEnabled' is not specified, is true. | true |  | false | technology | active | true
JSP:SPEC:229.25.3 | 8 | 5.1 | Any value other than 'true' or 'false' provided to the 'isELEnabled' attribute will result in a translation error. | true |  | false | technology | active | true
JSP:SPEC:229.26 | 8 | 5.1 | The deferredSyntaxAllowedAsLiteral attribute of the tag directive carries the same syntax and semantics of the deferredSyntaxAllowedAsLiteral attribute of the page directive. [DeferredSyntaxAllowedAsLiteralTagDirectiveAttribute] | true |  | false | technology | active | true
JSP:SPEC:229.26.1 | 8 | 5.1 | The deferredSyntaxAllowedAsLiteral attribute of the tag directive causes a translation error if specified in a tag file with a JSP version less than 2.1. [deferredSyntaxAllowedAsLiteralMinimumJspVersion] | true |  | false | technology | active | true
JSP:SPEC:229.27 | 8 | 5.1 | The trimDirectiveWhiteSpaces attribute of the tag directive carries the same syntax and semantics of the trimDirectiveWhitespaces attribute of the page directive. [TrimDirectiveWhitespacesTagDirectiveAttribute] | true |  | false | technology | active | true
JSP:SPEC:229.26 | 8 | 5.1 | Multiple 'isELEnabled' attribute/value (re)definitions will result in a translation error if values do not match. | true |  | false | technology | active | true
JSP:SPEC:230 | 8 | 5.2 | The attribute directive is analogous to the <attribute> element in the Tag Library Descriptor, and allows for the declaration of custom action attributes. | true |  | false | technology | active | true
JSP:SPEC:230.1 | 8 | 5.2 | The 'name' attribute specifies the unique name of the attribute being declared. | true |  | false | technology | active | true
JSP:SPEC:230.1.1 | 8 | 5.2 | A translation error will occur if the 'name' attribute is not specified. | true |  | false | technology | active | true
JSP:SPEC:230.1.2 | 8 | 5.2 | A translation error will result if there is an attribute directive with a name attribute equal to the value of the name-given attribute of a variable directive in this translation unit. | true |  | false | technology | active | true
JSP:SPEC:230.1.3 | 8 | 5.2 | A translation error will result if there is an attribute directive with a name attribute equal to the value of the dynamicattributes attribute of a tag directive in this translation unit. | true |  | false | technology | active | true
JSP:SPEC:230.2 | 8 | 5.2 | A translation error will occur if more than one attribute directive appears in the same translation unit with the same name. | true |  | false | technology | active | true
JSP:SPEC:230.3 | 8 | 5.2 | The 'required' attribute indicates whether or not the attribute must be present. | true |  | false | technology | active | false
JSP:SPEC:230.3.1 | 8 | 5.2 | If 'true' the attribute is requried and a translation error will occur if the attribute is not provided. | true |  | false | technology | active | true
JSP:SPEC:230.3.2 | 8 | 5.2 | If 'false', the attribute need not be present. | true |  | false | technology | active | true
JSP:SPEC:230.3.3 | 8 | 5.2 | If the 'required' attribute is not specified, the value of 'false' will be assumed. | true |  | false | technology | active | true
JSP:SPEC:230.4 | 8 | 5.2 | The 'fragment' attribute specifies whether this attribute is a fragment to be evaluated by the tag handler or a normal attribute to be evaluated by the container prior to being passed to the tag handler. | true |  | false | technology | active | true
JSP:SPEC:230.4.1 | 8 | 5.2 | If 'true', the type of the attribute is fixed to jakarta.servlet.jsp.tagext.JspFragment. | true |  | false | technology | active | true
JSP:SPEC:230.4.5 | 8 | 5.2 | If the 'fragment' attribute is true, and the 'type' attribute is specified, a translation error will occur | true |  | false | technology | active | true
JSP:SPEC:230.4.2 | 8 | 5.2 | If 'true' the 'rtexprvalue' attribute is fixed at true. | true |  | false | technology | active | true
JSP:SPEC:230.4.2.1 | 8 | 5.2 | A translation error will occur if the 'fragment' attribute is 'true' and the 'rtexprvalue' attribute is specified. | true |  | false | technology | active | true
JSP:SPEC:230.4.3 | 8 | 5.2 | If 'false', the container will evaluate the attribute before passing it to the tag handler. | true |  | false | technology | active | true
JSP:SPEC:230.4.4 | 8 | 5.2 | If the 'fragment' attribute is not specified, the behavior will be as if it was defined as 'false' | true |  | false | technology | active | true
JSP:SPEC:230.5 | 8 | 5.2 | The 'rtexprevalue' attribute specifies whether this attribute accepts dynamic attribute value. | true |  | false | technology | active | true
JSP:SPEC:230.5.1 | 8 | 5.2 | If 'true', the attribute can accept dynamic values. | true |  | false | technology | active | true
JSP:SPEC:230.5.2 | 8 | 5.2 | If 'false', the attribute cannot accept a dynamic value. Any attempt to pass a dynamic value when false will result in a translation error. | true |  | false | technology | active | true
JSP:SPEC:230.5.3 | 8 | 5.2 | If 'rtexprvalue' is not specified, the default of 'false' will be assumed. | true |  | false | technology | active | true
JSP:SPEC:230.5.4 | 8 | 5.2 | A translation error will occur if any other value outside of 'true' or 'false' is provided. | true |  | false | technology | active | true
JSP:SPEC:230.6 | 8 | 5.2 | The 'type' attribute specifies the runtime type of the attribute being described. | true |  | false | technology | active | true
JSP:SPEC:230.6.1 | 8 | 5.2 | If the 'type' attribute is not specified, the default of java.lang.String will be assumed. | true |  | false | technology | active | true
JSP:SPEC:230.6.2 | 8 | 5.2 | It is a translation error to specify a primitive type. | true |  | false | technology | active | true
JSP:SPEC:230.7 | 8 | 5.2 | The 'description' attribute specifies a description of the attribute. | true |  | false | technology | active | true
JSP:SPEC:230.7.1 | 8 | 5.2 | If the 'description' attribute is not specified, no description will be available. | true |  | false | technology | active | false
JSP:SPEC:230.8 | 8 | 5.2 | The deferredValue attribute of the attribute directive determines whether the attribute's value represents a deferred value expression | true |  | false | technology | active | false
JSP:SPEC:230.8.1 | 8 | 5.2 | Only one of deferredValue or deferredMethod attribute directive attributes may be true. [OnlyOneOfDeferredValueOrMethod] | true |  | false | technology | active | true
JSP:SPEC:230.8.2 | 8 | 5.2 | If the deferredValueType of the attribute directive is specified, default for deferredValue is true, otherwise default is false.[DefaultDeferredValue] | true |  | false | technology | active | true
JSP:SPEC:230.8.3 | 8 | 5.2 | The deferredValue attribute causes a translation error if specified in a tag file with a JSP version less than 2.1. [deferredValueMinimumJspVersion] | true |  | false | technology | active | true
JSP:SPEC:230.9 | 8 | 5.2 | The deferredValueType attribute of the attribute directive is the expected type resulting from the evaluation of the attribute's value expression. | true |  | false | technology | active | false
JSP:SPEC:230.9.1 | 8 | 5.2 | The deferredValueType attribute defaults to java.lang.String if not specified. [DeferredValueTypeNotSpecified] | true |  | false | technology | active | true
JSP:SPEC:230.9.2 | 8 | 5.2 | If both deferredValueType and deferredValue are specified, deferredValue must be true. [BothDeferredValueTypeAndDeferredValue] | true |  | false | technology | active | true
JSP:SPEC:230.9.3 | 8 | 5.2 | deferredValue is true, the default for deferredValueType is java.lang.Object.[DeferredValueTypeDefaultWhenDeferredValueTrue] | true |  | false | technology | active | true
JSP:SPEC:230.9.4 | 8 | 5.2 | The deferredValueType attribute causes a translation error if specified in a tag file with a JSP version less than 2.1. [deferredValueTypeMinimumJspVersion] | true |  | false | technology | active | true
JSP:SPEC:230.10 | 8 | 5.2 | The deferredMethod attribute of the attribute directive determines whether the attribute's value represents a deferred method expression. | true |  | false | technology | active | false
JSP:SPEC:230.10.1 | 8 | 5.2 | If deferredMethodSignature is specified, the default of the deferredMethod attribute is true, otherwise default is false. [DefaultDeferredMethod] | true |  | false | technology | active | true
JSP:SPEC:230.10.2 | 8 | 5.2 | The deferredMethod attribute causes a translation error if specified in a tag file with a JSP version less than 2.1. [deferredMethodMinimumJspVersion] | true |  | false | technology | active | true
JSP:SPEC:230.11 | 8 | 5.2 | The deferredMethodSignature attribute of the attribute directive represents the signature, as defined in the Java Language Specification, of the method to be invoked in the attribute's method expression. | true |  | false | technology | active | false
JSP:SPEC:230.11.1 | 8 | 5.2 | If both deferredMethod and deferredMethodSignature are specified, deferredMethod must be true. [BothDeferredMethodAndSignature] | true |  | false | technology | active | true
JSP:SPEC:230.11.2 | 8 | 5.2 | If deferredMethod is true and deferredMethodSignature is not specified, deferredMethodSignature defaults to void methodname(). [DefaultDeferredMethodSignature] | true |  | false | technology | active | true
JSP:SPEC:230.11.3 | 9 | 5.2 | The deferredMethodSignature attribute causes a translation error if specified in a tag file with a JSP version less than 2.1. [deferredMethodSignatureMinimumJspVersion] | true |  | false | technology | active | true
JSP:SPEC:231 | 8 | 5.3 | The variable directive is analogous to the <variable> element in the Tag Library Descriptor, and defines the details of a variable exposed by the tag handler to the calling page. | true |  | false | technology | active | true
JSP:SPEC:231.1 | 8 | 5.3 | The 'name-given' attribute specifies the name of the scripting variable to be exposed by the tag. | true |  | false | technology | active | true
JSP:SPEC:231.1.1 | 8 | 5.3 | A translation error will occur if two variable directives have the same value for the 'name-given' attribute. | true |  | false | technology | active | true
JSP:SPEC:231.2 | 8 | 5.3 | The 'name-from-attribute' directive specifies the name of an attribute whose (translation-time) value will give the name of the variable. | true |  | false | technology | active | true
JSP:SPEC:231.2.1 | 8 | 5.3 | A translation error will occur if two variable directives have the same value for the 'name-from-attribute' attribute. | true |  | false | technology | active | true
JSP:SPEC:231.3 | 8 | 5.3 | A translation error will occur if both the 'name-given' and the 'name-from-attribute' attributes are specified within the same directive. | true |  | false | technology | active | true
JSP:SPEC:231.4 | 8 | 5.3 | A translation error will occur if neither the 'name-given' or the 'name-from-attribute' attributes are not specified wihin a variable directive. | true |  | false | technology | active | true
JSP:SPEC:231.5 | 8 | 5.3 | The 'variable-class' attribute specifies the class of the variable. | true |  | false | technology | active | true
JSP:SPEC:231.5.1 | 8 | 5.3 | If the 'variable-class' attribute is not specified, the default class of java.lang.String will be assumed. | true |  | false | technology | active | true
JSP:SPEC:231.6 | 8 | 5.3 | The 'scope' attribute specifies the scope of the variable being declared. | true |  | false | technology | active | true
JSP:SPEC:231.6.1 | 8 | 5.3 | Valid values are AT_BEGIN, AT_END, or NESTED. | true |  | false | technology | active | true
JSP:SPEC:231.6.2 | 8 | 5.3 | If the 'scope' attribute is not specified, the default scope of NESTED will be used. | true |  | false | technology | active | true
JSP:SPEC:231.6.3 | 8 | 5.3 | If any other value is provided outside of AT_BEGIN, NESTED, or AT_END, a translation error will occur. | true |  | false | technology | active | true
JSP:SPEC:231.6.4 | 8 | 5.3 | A translation error must occur if both 'scope' and 'fragment' are specified. | true |  | false | technology | active | true
JSP:SPEC:231.7 | 8 | 5.3 | The 'declare' attribute specifies whether the variable is declared or not. | true |  | false | technology | active | true
JSP:SPEC:231.7.1 | 8 | 5.3 | If 'true', the variable will be declared and available based on the specified scope. | true |  | false | technology | active | true
JSP:SPEC:231.7.2 | 8 | 5.3 | If 'false', the variable will not be declared. | true |  | false | technology | active | true
JSP:SPEC:231.7.3 | 8 | 5.3 | A translation error must occur if both 'declare' and 'fragment' are specified. | true |  | false | technology | active | true
JSP:SPEC:231.8 | 8 | 5.3 | The 'fragment' attribute specifies that the value of this variable is scoped to the specified fragment and does not appear in the body of the tag. | true |  | false | technology | active | true
JSP:SPEC:231.8.1 | 8 | 5.3 | A translation error will occur if the value of 'fragment' does not match the name of an attribute declared earier in this page with 'fragment=true'. | true |  | false | technology | active | true
JSP:SPEC:231.8.2 | 8 | 5.3 | A translation error will occur if 'fragment' is specified and either 'scope' or 'declare' is specified. | true |  | false | technology | active | true
JSP:SPEC:231.9 | 8 | 5.3 | The 'description' attribute provides an optional description for the variable being declared. | true |  | false | technology | active | true
JSP:SPEC:231.9.1 | 8 | 5.3 | If the 'description' attribute is not specified, no description will be available. | true |  | false | technology | active | false
JSP:SPEC:232 | 8 | 6 | XML view of Tag Files | true |  | false | technology | active | false
JSP:SPEC:232.1 | 8 | 6 | The XML equivalent of the tag directive is the jsp:directive.tag element. The semantics followed are the same as the tag directive in standard syntax. | true |  | false | technology | active | true
JSP:SPEC:232.1.1 | 8 | 5.1 | A translation unit can contain more than one instance of the tag directive, all the attributes will apply to the complete translation unit (i.e. tag directives are position independent). | true |  | false | technology | active | true
JSP:SPEC:232.1.2 | 8 | 5.1 | Unrecoginized attributes or values will result in a fatal translation error. | true |  | false | technology | active | true
JSP:SPEC:232.1.3 | 8 | 5.1 | The 'display-name' attribute provides a short name that is intended to be displayed by tools. | true |  | false | technology | active | true
JSP:SPEC:232.1.4 | 8 | 5.1 | Multiple 'display-name' attribute/value (re)definitions will result in a translation error if values do not match. | true |  | false | technology | active | true
JSP:SPEC:232.1.5 | 8 | 5.1 | The 'body-content' attribute specifies the body content of this tag. | true |  | false | technology | active | true
JSP:SPEC:232.1.5.1 | 8 | 5.1 | A valid value is 'empty' meaning no body. | true |  | false | technology | active | true
JSP:SPEC:232.1.5.2 | 8 | 5.1 | A valid value is 'tagdependent'. | true |  | false | technology | active | true
JSP:SPEC:232.1.5.3 | 8 | 5.1 | A valid value is 'scriptless' | true |  | false | technology | active | true
JSP:SPEC:232.1.5.4 | 8 | 5.1 | If the 'body-content' attribute is not specified, it will default to 'scriptless' | true |  | false | technology | active | true
JSP:SPEC:232.1.5.5 | 8 | 5.1 | Any other value provided to the 'body-content' attribute aside from 'empty', 'tagdependent', or 'scriptless' will result in a translation error. | true |  | false | technology | active | true
JSP:SPEC:232.1.6 | 8 | 5.1 | Multiple 'body-content' attribute/value (re)definitions will result in a translation error if values do not match. | true |  | false | technology | active | true
JSP:SPEC:232.1.7 | 8 | 5.1 | The 'dynamic-attributes' attribute indicates whether this tag supports additional attributes with dynamic sata. | true |  | false | technology | active | true
JSP:SPEC:232.1.7.1 | 8 | 5.1 | If 'true', the generated tag handler must implement the jakarta.servlet.jsp.tagext.DynamicAttributes interface. | true |  | false | technology | active | true
JSP:SPEC:232.1.7.2 | 8 | 5.1 | If 'false' the generated tag handler will not implement the jakarta.servlet.jsp.tagext.DynamicAttributes interface. | true |  | false | technology | active | true
JSP:SPEC:232.1.7.3 | 8 | 5.1 | The default value is 'false'. | true |  | false | technology | active | false
JSP:SPEC:232.1.7.4 | 8 | 5.1 | If any values are provided to the 'dynamic-attributes' attribute aside from 'true' or 'false' a translation error will occur. | true |  | false | technology | active | true
JSP:SPEC:232.1.8 | 8 | 5.1 | Multiple 'dyanmic-attribute' attribute/value (re)definitions will result in a translation error if values do not match. | true |  | false | technology | active | true
JSP:SPEC:232.1.9 | 8 | 5.1 | The 'small-icon' attribute specifies a relative path, from the tag source file, of an image file containg a small icon that can be used by tools. | true |  | false | technology | active | true
JSP:SPEC:232.1.9.1 | 8 | 5.1 | If the 'small-icon' attribute is not specified, no icon will be used. | true |  | false | technology | active | false
JSP:SPEC:232.1.10 | 8 | 5.1 | Multiple 'small-icon' attribute/value (re)definitions will result in a translation error if values do not match. | true |  | false | technology | active | true
JSP:SPEC:232.1.11 | 8 | 5.1 | The 'large-icon' attribute specifies a relative path from the tag source file, of an image file containing a large icon that can be used by tools. | true |  | false | technology | active | true
JSP:SPEC:232.1.11.1 | 8 | 5.1 | If the 'large-icon' attribute is not specified, no icon will be used. | true |  | false | technology | active | false
JSP:SPEC:232.1.12 | 8 | 5.1 | Multiple 'large-icon' attribute/value (re)definitions will result in a translation error if values do not match. | true |  | false | technology | active | true
JSP:SPEC:232.1.13 | 8 | 5.1 | The 'decription' attribute provides an arbitrary string that describes this tag. | true |  | false | technology | active | true
JSP:SPEC:232.1.13.1 | 8 | 5.1 | If the 'description' attribute is not specified, no description will be available. | true |  | false | technology | active | false
JSP:SPEC:232.1.14 | 8 | 5.1 | Multiple 'description' attribute/value (re)definitions will result in a translation error if values do not match. | true |  | false | technology | active | true
JSP:SPEC:232.1.15 | 8 | 5.1 | The 'example' attribute defines an arbitraty string describe the use of this action. | true |  | false | technology | active | true
JSP:SPEC:232.1.15.1 | 8 | 5.1 | If the 'example' attribute is not specified, no example string will be available. | true |  | false | technology | active | false
JSP:SPEC:232.1.16 | 8 | 5.1 | Multiple 'example' attribute/value (re)definitions will result in a translation error if values do not match. | true |  | false | technology | active | true
JSP:SPEC:232.1.17 | 8 | 5.1 | The 'language' attribute specifies the scripting language used by the tag file. | true |  | false | technology | active | true
JSP:SPEC:232.1.17.1 | 1 | 10.1 | All scripting languages, specifiable by the tag directive's 'language' attribute, must provide some implicit objects that a JSP page author can use in declarations, scriptlets, and expressions (see Section JSP.1.3.8 for list of available implicit objects) | true |  | true | technology | active | false
JSP:SPEC:232.1.17.2 | 1 | 10.1 | All scripting languages, specifiable by the tag directive's 'language' attribute, must expose the Java technology object model to the script environment, especially implicit variables, JavaBeans components properties, and public methods. | true |  | true | technology | active | false
JSP:SPEC:232.1.17.3 | 1 | 10.1 | It is a fatal translation error for a tag directive with a non-"java" language attribute to appear after the first scripting has been encountered. | true |  | false | technology | active | true
JSP:SPEC:232.1.17.4 | 1 | 10.1 | The only required scripting language value for the 'language' attribute is "java". | true |  | false | technology | active | true
JSP:SPEC:232.1.18 | 8 | 5.1 | Multiple 'language' attribute/value (re)definitions will result in a translation error if values do not match. | true |  | false | technology | active | true
JSP:SPEC:232.1.19 | 8 | 5.1 | The 'import' attribute of the tag directive specifies the fully qualified Java programming language type name denoting a particular type, or of a package name following by the ".*" string, denoting all the public types declared in that package, that shall be imorted by the translated JSP page implementation and is thus available to the scripting language. | true |  | false | technology | active | true
JSP:SPEC:232.1.19.1 | 1 | 10.1 | The default import list for a tag is java.lang.*, jakarta.servlet.*, jakarta.servlet.jsp.*, jakarta.servlet.http.* | true |  | false | technology | active | true
JSP:SPEC:232.1.20 | 8 | 5.1 | The 'pageEncoding' attribute of the tag directive specifies the character encoding of the tag. The value is in the form of CHARSET which my be the IANA value for a character encoding. If no 'pageEncoding' attribute is specified, the default of ISO-8859-1 will be used. | true |  | false | technology | active | true
JSP:SPEC:232.1.21 | 8 | 5.1 | Multiple 'pageEncoding' attribute/value (re)definitions will result in a translation error. | true |  | false | technology | active | true
JSP:SPEC:232.1.22 | 8 | 5.1 | The 'pageEncoding' attribute of the tag directive is not influenced at all by any global configuration present in the web.xml | true |  | false | technology | active | true
JSP:SPEC:232.1.23 | 8 | 5.1 | The 'isScriptingEnabled' attribute specified whether scripting elements are legal within the tag file. | true |  | false | technology | active | true
JSP:SPEC:232.1.23.1 | 1 | 10.1 | The 'isScriptingEnabled' attribute of the tag directive, if false, disallows the presence of scripting elements (scriptlets, expressions, declarations) within a given translation unit and will generate a translation error if they are present. | true |  | false | technology | active | true
JSP:SPEC:232.1.23.2 | 1 | 10.1 | The default value for 'isScriptingEnabled' of the tag directive, if not specified, is true. | true |  | false | technology | active | true
JSP:SPEC:232.1.23.3 | 8 | 5.1 | Any value other than 'true' or 'false' provided to the 'isScriptinEnabled' attribute will result in a translation error. | true |  | false | technology | active | true
JSP:SPEC:232.1.24 | 8 | 5.1 | Multiple 'isScriptingEnabled' attribute/value (re)definitions will result in a translation error if values do not match. | true |  | false | technology | active | true
JSP:SPEC:232.1.25 | 8 | 5.1 | The 'isELEnabled' attribute of the tag directive specifies whether or not the container should evaluate EL expressions. | true |  | false | technology | active | true
JSP:SPEC:232.1.25.1 | 1 | 10.1 | The 'isELEnabled' attribute of the page directive , if false, will result in EL expressions not being evaluated by the container. | true |  | false | technology | active | true
JSP:SPEC:232.1.25.2 | 1 | 10.1 | The default value, if 'isELEnabled' is not specified, is true. | true |  | false | technology | active | true
JSP:SPEC:232.1.25.3 | 8 | 5.1 | Any value other than 'true' or 'false' provided to the 'isELEnabled' attribute will result in a translation error. | true |  | false | technology | active | true
JSP:SPEC:232.1.26 | 8 | 5.1 | Multiple 'isELEnabled' attribute/value (re)definitions will result in a translation error if values do not match. | true |  | false | technology | active | true
JSP:SPEC:232.2 | 8 | 6 | The attribute directive of a tag file can be described in XML using the jsp:directive.attribute element. The semantics of this element are the same as the attribute directive in standard syntax. | true |  | false | technology | active | true
JSP:SPEC:232.2.1 | 8 | 5.2 | The 'name' attribute specified the unique name of the attribute being declared. | true |  | false | technology | active | true
JSP:SPEC:232.2.1.1 | 8 | 5.2 | A translation error will occur if the 'name' attribute is not specified. | true |  | false | technology | active | true
JSP:SPEC:232.2.2 | 8 | 5.2 | A translation error will occur if mnore than one attribute directive appears in the same translation unit with the same name. | true |  | false | technology | active | true
JSP:SPEC:232.2.3 | 8 | 5.2 | The 'required' attribute indicates whether or not the attribute must be present. | true |  | false | technology | active | false
JSP:SPEC:232.2.3.1 | 8 | 5.2 | If 'true' the attribute is requried and a translation error will occur if the attribute is not provided. | true |  | false | technology | active | true
JSP:SPEC:232.2.3.2 | 8 | 5.2 | If 'false', the attribute need not be present. | true |  | false | technology | active | true
JSP:SPEC:232.2.3.3 | 8 | 5.2 | If the 'required' attribute is not specified, the value of 'false' will be assumed. | true |  | false | technology | active | true
JSP:SPEC:232.2.4 | 8 | 5.2 | The 'fragment' attribute specifies whether this attribute is a fragment to be evaluated by the tag handler or a normal attribute to be evaluated by the container prior to being passed to the tag handler. | true |  | false | technology | active | true
JSP:SPEC:232.2.4.1 | 8 | 5.2 | If 'true', the type of the attribute is fixed to jakarta.servlet.jsp.tagext.JspFragment and a translation error will occur if the 'type' attribute is specified. | true |  | false | technology | active | true
JSP:SPEC:232.2.4.2 | 8 | 5.2 | If 'true' the 'rtexprvalue' attribute is fixed at true. | true |  | false | technology | active | true
JSP:SPEC:232.2.4.2.1 | 8 | 5.2 | A translation error will occur if the 'fragment' attribute is 'true' and the 'rtexprvalue' attribute is specified. | true |  | false | technology | active | true
JSP:SPEC:232.2.4.3 | 8 | 5.2 | If 'false', the container will evaluate the attribute before passing it to the tag handler. | true |  | false | technology | active | true
JSP:SPEC:232.2.4.4 | 8 | 5.2 | If the 'fragment' attribute is not specified, the behavior will be as if it was defined as 'false' | true |  | false | technology | active | true
JSP:SPEC:232.2.5 | 8 | 5.2 | The 'rtexprevalue' attribute specifies whether this attribute accepts dynamic attribute value. | true |  | false | technology | active | true
JSP:SPEC:232.2.5.1 | 8 | 5.2 | If 'true', the attribute can accept dynamic values. | true |  | false | technology | active | true
JSP:SPEC:232.2.5.2 | 8 | 5.2 | If 'false', the attribute cannot accept a dynamic value. Any attempt to pass a dynamic value when false will result in a translation error. | true |  | false | technology | active | true
JSP:SPEC:232.2.5.3 | 8 | 5.2 | If 'rtexprvalue' is not specified, the default of 'false' will be assumed. | true |  | false | technology | active | true
JSP:SPEC:232.2.5.4 | 8 | 5.2 | A translation error will occur if any other value outside of 'true' or 'false' is provided. | true |  | false | technology | active | true
JSP:SPEC:232.2.6 | 8 | 5.2 | The 'type' attribute specifies the runtime type of the attribute being described. | true |  | false | technology | active | true
JSP:SPEC:232.2.6.1 | 8 | 5.2 | If the 'type' attribute is not specified, the default of java.lang.String will be assumed. | true |  | false | technology | active | true
JSP:SPEC:232.2.7 | 8 | 5.2 | The 'description' attribute specifies a description of the attribute. | true |  | false | technology | active | true
JSP:SPEC:232.2.7.1 | 8 | 5.2 | If the 'description' attribute is not specified, no description will be available. | true |  | false | technology | active | false
JSP:SPEC:232.3 | 8 | 5.2 | The variable directive of a tag file can be described in XML using the jsp:directive.variable element. The semantics are the same as the variable directive in standard syntax. | true |  | false | technology | active | true
JSP:SPEC:232.3.1 | 8 | 5.3 | The 'name-given' attribute specifies the name of the scriptin variable to be exposed by the tag. | true |  | false | technology | active | true
JSP:SPEC:232.3.1.1 | 8 | 5.3 | A translation error will occur if two variable directives have the same value for the 'name-given' attribute. | true |  | false | technology | active | true
JSP:SPEC:232.3.2 | 8 | 5.3 | The 'name-from-attribute' directive specifies the name of an attribute whose (translation-time) value will give the name of the variable. | true |  | false | technology | active | true
JSP:SPEC:232.3.2.1 | 8 | 5.3 | A translation error will occur if two variable directives have the same value for the 'name-from-attribute' attribute. | true |  | false | technology | active | true
JSP:SPEC:232.3.3 | 8 | 5.3 | A translation error will occur if both the 'name-given' and the 'name-from-attribute' attributes are specified within the same directive. | true |  | false | technology | active | true
JSP:SPEC:232.3.4 | 8 | 5.3 | A translation error will occur if neither the 'name-given' or the 'name-from-attribute' attributes are not specified wihin a variable directive. | true |  | false | technology | active | true
JSP:SPEC:232.3.5 | 8 | 5.3 | The 'variable-class' attribute specifies the class of the variable. | true |  | false | technology | active | true
JSP:SPEC:232.3.5.1 | 8 | 5.3 | If the 'variable-class' attribute is not specified, the default class of java.lang.String will be assumed. | true |  | false | technology | active | true
JSP:SPEC:232.3.6 | 8 | 5.3 | The 'scope' attribute specifies the scope of the variable being declared. | true |  | false | technology | active | true
JSP:SPEC:232.3.6.1 | 8 | 5.3 | Valid values are AT_BEGIN, AT_END, or NESTED. | true |  | false | technology | active | true
JSP:SPEC:232.3.6.2 | 8 | 5.3 | If the 'scope' attribute is not specified, the default scope of NESTED will be used. | true |  | false | technology | active | true
JSP:SPEC:232.3.6.3 | 8 | 5.3 | If any other value is provided outside of AT_BEGIN, NESTED, or AT_END, a translation error will occur. | true |  | false | technology | active | true
JSP:SPEC:232.3.6.4 | 8 | 5.3 | A translation error must occur if both 'scope' and 'fragment' are specified. | true |  | false | technology | active | true
JSP:SPEC:232.3.7 | 8 | 5.3 | The 'declare' attribute specifies whether the variable is declared or not. | true |  | false | technology | active | true
JSP:SPEC:232.3.7.1 | 8 | 5.3 | If 'true', the variable will be declared and available based on the specified scope. | true |  | false | technology | active | true
JSP:SPEC:232.3.7.2 | 8 | 5.3 | If 'false', the variable will not be declared. | true |  | false | technology | active | true
JSP:SPEC:232.3.7.3 | 8 | 5.3 | A translation error must occur if both 'declare' and 'fragment' are specified. | true |  | false | technology | active | true
JSP:SPEC:232.3.8 | 8 | 5.3 | The 'fragment' attribute specifies that the value of this variable is scoped to the specified fragment and does not appear in the boyd of the tag. | true |  | false | technology | active | true
JSP:SPEC:232.3.8.1 | 8 | 5.3 | A translation error will occur if the value of 'fragment' does not match the name of an attribute declared earier in this page with 'fragment=true'. | true |  | false | technology | active | true
JSP:SPEC:232.3.8.2 | 8 | 5.3 | A translation error will occur if 'fragment' is specified and either 'scope' or 'declare' is specified. | true |  | false | technology | active | true
JSP:SPEC:232.3.9 | 8 | 5.3 | The 'description' attribute provides an optional description for the variable being declared. | true |  | false | technology | active | true
JSP:SPEC:232.3.9.1 | 8 | 5.3 | If the 'description' attribute is not specified, no description will be available. | true |  | false | technology | active | false
JSP:SPEC:233 | 9 | 1.1 | A JSP page is valid for a Java Platform if and only if the JSP page implementation class, together with any other classes defined by the JSP container, is a valid program for the given Java Platform, and if it passes the validation methods for all the tag libraries associated with the JSP page. | true |  | false | technology | active | true
JSP:SPEC:234 | 10 | 1 | In JSP 2.0 only 'init' and 'destroy' events are allowed events. | true |  | false | technology | active | false
JSP:SPEC:235 | 10 | 1 | A JSP page author may provide a jspInit() method, which if present, must be called by the container to prepare the page before the first request is delivered. | true |  | false | technology | active | true
JSP:SPEC:236 | 10 | 1.1.1 | A JSP page author may provide a jspDestroy() method that can be called by a Container, when a request is not being serviced by the JSP page, to reclaim resources. | true |  | true | technology | active | false
JSP:SPEC:237 | 10 | 1.1.1 | A translation error will occur if a JSP page author attempts to override any Servlet methods through a declaration scripting element. | true |  | false | technology | active | false
JSP:SPEC:238 | 10 | 1.1.2 | The enforcement of the contract between the JSP container and the JSP page author is aided by the requirement that the Servlet class corresponding to the JSP page must implement the HttpJspPage interface if the protocol is HTTP. | true |  | false | technology | active | true
JSP:SPEC:239 | 10 | 1.1.2 | The enforcement of the contract between the JSP container and the JSP page author is aided by the requirement that the Servlet class corresponding to the JSP page must implement the JspPage interface of the protocol is not HTTP. | true |  | false | technology | active | false
JSP:SPEC:240 | 10 | 2 | The name of the JSP implementation class is implementation dependent. | true |  | true | technology | active | false
JSP:SPEC:241 | 10 | 2 | The package that the JSP implementation class belongs to is implementation dependent. | true |  | true | technology | active | false
JSP:SPEC:242 | 10 | 2.1 | All JSP implementation classes must implement the following methods | true |  | false | technology | active | true
JSP:SPEC:242.1 | 10 | 2.1 | Method with signature: public void jspInit() | true |  | false | technology | active | true
JSP:SPEC:242.2 | 10 | 2.1 | Method with signature: public void jspDestroy() | true |  | false | technology | active | true
JSP:SPEC:242.3 | 10 | 2.1 | Method with signature: public void _jspService(<ServletRequestSubType>, <ServletResponseSubType>) throws IOException, ServletException -- NOTE: The request/response subtype indicates that the request and response object provided must implement the jakarta.servlet.ServletRequest and jakarta.servlet.ServletResponse interfaces respectively. | true |  | false | technology | active | true
JSP:SPEC:242.3.1 | 10 | 2,1 | The _jspService(ServletRequest, ServletResponse) method may not be declared in a JSP page via the JSP declaration mechanism. | true |  | false | technology | active | false
JSP:SPEC:243 | 10 | 2.1 | JSP containers that conform to this specification (in both JSP page implementation classes, and JSP container runtime) must implement the jakarta.servlet.ServletRequest and jakarta.servlet.ServletResponse interfaces. | true |  | false | technology | active | false
JSP:SPEC:244 | 10 | 4 | All JSP 2.0 compliant containers must support a simple precompilation protocol, as well as some basic reserved parameter names. | true |  | false | technology | active | true
JSP:SPEC:244.1 | 10 | 4 | A request to a page with the request parameter 'jsp_precompile" is a precompilation request. | true |  | false | technology | active | true
JSP:SPEC:244.1.1 | 10 | 4.2 | If the value of the request parameter 'jsp_precompile' is 'true' the request will not be delivered to the target page. | true |  | false | technology | active | true
JSP:SPEC:244.1.2 | 10 | 4.2 | If the value of the request parameter 'jsp_precompile' is 'false', the request will not be delivered to the target page. | true |  | false | technology | active | true
JSP:SPEC:244.1.3 | 10 | 4.2 | If the value of the request parameter 'jsp_precompile' is 'debug', the request will not be delivered to the target page. | true |  | false | technology | active | true
JSP:SPEC:244.1.4 | 10 | 4.2 | If the value of the request parameter 'jsp_precompile' is empty (i.e. ""), the request will not be delivered to the target page. | true |  | false | technology | active | true
JSP:SPEC:244.1.5 | 10 | 4.2 | If the value of the request parameter 'jsp_precompile' is any other value aside from 'true', 'false', 'debug', or an empty parameter, a translation error will occur. | true |  | false | technology | active | true
JSP:SPEC:245 | 10 | 5 | All JSP 2.0 containers must implement JSR-045 by generating source map debugging information for JSP pages written in either standard or XML syntax. | true |  | false | technology | active | false
JSP:SPEC:246 | 10 | 5 | The JSP compiler, when producing a class with JSP-045 debug extensions must produce a .class file with a SourceDebugExtension attribute, mapping each line or lines of JSP code to the corresponding generated line or lines of Java code. | true |  | false | technology | active | false
JSP:SPEC:247 | 10 | 5 | The strata, as defined by JSP-045, that maps to the original JSP source must be named JSP in the Source Debug Extension. | true |  | false | technology | active | false
JSP:SPEC:315 | 10 | 1.11 | The XML view of an escaped EL expression using the #{expr} syntax follows the same rules as the ${expr} syntax, where ${ is simply substituted with #{.[#{expr}SameAs${expr}] | true |  | false | technology | active | true
JSP:SPEC:316 | 10 | 1.12 | The same rules for deriving the XML view of escaped expressions for the ${expr} syntax apply for the #{expr} syntax, where ${ is simply substituted with #{[TemplateTextPoundSign] | true |  | false | technology | active | true
JSP:SPEC:317 | 11 | 5 | SP 2.1 containers are required to provide support for JSR-45 for JSP pages and tag files written in either standard or XML syntax. [JSR45DebuggingSupport] | true |  | false | technology | active | true
JSP:SPEC:318 | D | 1 | In determining the page encoding of a JSP file where the file is preceded by a BOM: Read the file using the encoding indicated by the BOM, and search for a pageEncoding attribute in a page declaration. Report an error if any of the following conditions are met: There is a <page-encoding> configuration element whose URL pattern matches this page and whose encoding does not match the encoding indicated by the BOM. There is a pageEncoding page directive attribute whose encoding does not match the encoding indicated by the BOM. [BOMErrorReporting] | true |  | false | technology | active | true