diff --git a/tck/docs/JakartaServerPages3.1-ReleaseNotes.html b/tck/docs/JakartaServerPages3.1-ReleaseNotes.html
new file mode 100644
index 00000000..db198313
--- /dev/null
+++ b/tck/docs/JakartaServerPages3.1-ReleaseNotes.html
@@ -0,0 +1,97 @@
+
+
+
+ The Jakarta EE Server Pages, Version 3.1 Technology Compatibility Kit
+ (TCK) includes the following items:
+ The Jakarta EE Server Pages TCK tests have been built with JDK 8 (1.8)
+ and tested with JavaTM
+ Platform, Standard Edition 8 and 11.
+ The Jakarta EE Server Pages TCK tests have been run on the following
+ platforms:
+ The Jakarta EE Server Pages TCK tests have been run against the Eclipse
+ Jakarta EE Server Pages Compatible Implementation Version 3.1.
+ The online version of the JT Harness version 5.0 documentation is
+ available here.
+
+ID | Return | Method/Field | Description | Required | Deprecated | Testable |
+
+JSP:JAVADOC:1 | ErrorData | jakarta.servlet.jsp.ErrorData.ErrorData
+
+ (
+ Throwable
+ , int
+ , String
+ , String
+ )
+ | Creates a new ErrorData object
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:2 | Throwable | jakarta.servlet.jsp.ErrorData.getThrowable
+ | Returns the Throwable that caused the error
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:3 | int | jakarta.servlet.jsp.ErrorData.getStatusCode
+ | Returns the status code of the error
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:4 | String | jakarta.servlet.jsp.ErrorData.getRequestURI
+ | Returns the request URI
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:5 | String | jakarta.servlet.jsp.ErrorData.getServletName
+ | Returns the name of the servlet invoked
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:6 | SkipPageException | jakarta.servlet.jsp.SkipPageException.SkipPageException
+ | Creates a SkipPageException with no message.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:7 | SkipPageException | jakarta.servlet.jsp.SkipPageException.SkipPageException
+
+ (
+ String
+ )
+ | Creates a SkipPageException with the provided message.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:8 | SkipPageException | jakarta.servlet.jsp.SkipPageException.SkipPageException
+
+ (
+ String
+ , Throwable
+ )
+ | Creates a SkipPageException with the provided message and root cause.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:9 | SkipPageException | jakarta.servlet.jsp.SkipPageException.SkipPageException
+
+ (
+ Throwable
+ )
+ | Creates a SkipPageException with the provided root cause.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:10 | PageContext | jakarta.servlet.jsp.PageContext.PageContext
+ |
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:11 | void | jakarta.servlet.jsp.PageContext.initialize
+
+ (
+ Servlet
+ , ServletRequest
+ , ServletResponse
+ , String
+ , boolean
+ , int
+ , boolean
+ )
+ | The initialize method is called to initialize an uninitialized PageContext so that it may be used by a JSP Implementation class to service an incoming request and response within it's _jspService() method.
+ This method is typically called from JspFactory.getPageContext() in order to initialize state. This method is required to create an initial JspWriter, and associate the "out" name in page scope with this newly created object. This method should not be used by page or tag library authors.
+
+ | true |
+
+ | false |
+
+
+JSP:JAVADOC:12 | void | jakarta.servlet.jsp.PageContext.initialize
+
+ (
+ Servlet
+ , ServletRequest
+ , ServletResponse
+ , String
+ , boolean
+ , int
+ , boolean
+ )
+ throws
+ IOException
+ | during creation of JspWriter | true |
+
+ | false |
+
+
+JSP:JAVADOC:13 | void | jakarta.servlet.jsp.PageContext.initialize
+
+ (
+ Servlet
+ , ServletRequest
+ , ServletResponse
+ , String
+ , boolean
+ , int
+ , boolean
+ )
+ throws
+ IllegalStateException
+ | if out not correctly initialized | true |
+
+ | false |
+
+
+JSP:JAVADOC:14 | void | jakarta.servlet.jsp.PageContext.initialize
+
+ (
+ Servlet
+ , ServletRequest
+ , ServletResponse
+ , String
+ , boolean
+ , int
+ , boolean
+ )
+ throws
+ IllegalArgumentException
+ | If one of the given parameters is invalid | true |
+
+ | false |
+
+
+JSP:JAVADOC:15 | void | jakarta.servlet.jsp.PageContext.release
+ | This method shall "reset" the internal state of a PageContext, releasing all internal references, and preparing the PageContext for potential reuse by a later invocation of initialize().
+ This method is typically called from JspFactory.releasePageContext(). Subclasses shall envelope this method. This method should not be used by page or tag library authors.
+
+ | true |
+
+ | false |
+
+
+JSP:JAVADOC:16 | HttpSession | jakarta.servlet.jsp.PageContext.getSession
+ | The current value of the session object (an HttpSession).
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:17 | Object | jakarta.servlet.jsp.PageContext.getPage
+ | The current value of the page object (In a Servlet environment this is an isntance of jakarta.servlet.Servlet).
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:18 | ServletRequest | jakarta.servlet.jsp.PageContext.getRequest
+ | The current value of the request object (a ServletRequest).
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:19 | ServletResponse | jakarta.servlet.jsp.PageContext.getResponse
+ | The current value of the response object (a ServletResponse).
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:20 | Exception | jakarta.servlet.jsp.PageContext.getException
+ | The current value of the exception object (an Exception).
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:21 | ServletConfig | jakarta.servlet.jsp.PageContext.getServletConfig
+ | The ServletConfig instance.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:22 | ServletContext | jakarta.servlet.jsp.PageContext.getServletContext
+ | The ServletContext instance.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:23 | void | jakarta.servlet.jsp.PageContext.forward
+
+ (
+ String
+ )
+ | This method is used to re-direct, or "forward" the current ServletRequest and ServletResponse to another active component in the application. If the relativeUrlPath begins with a "/" then the URL specified is calculated relative to the DOCROOT of the ServletContext for this JSP. | true |
+
+ | true |
+
+
+JSP:JAVADOC:24 | void | jakarta.servlet.jsp.PageContext.forward
+
+ (
+ String
+ )
+ | This method is used to re-direct, or "forward" the current ServletRequest and ServletResponse to another active component in the application. If the path does not begin with a "/" then the URL specified is calculated relative to the URL of the request that was mapped to the calling JSP. | true |
+
+ | true |
+
+
+JSP:JAVADOC:25 | void | jakarta.servlet.jsp.PageContext.forward
+
+ (
+ String
+ )
+ | It is only valid to call this method from a Thread executing within a _jspService(...) method of a JSP. Once this method has been called successfully, it is illegal for the calling Thread to attempt to modify the ServletResponse object. Any such attempt to do so, shall result in undefined behavior. Typically, callers immediately return from _jspService(...) after calling this method. | true |
+
+ | false |
+
+
+JSP:JAVADOC:26 | void | jakarta.servlet.jsp.PageContext.forward
+
+ (
+ String
+ )
+ throws
+ ServletException
+ | if the page that was forwarded to throws a ServletException | true |
+
+ | true |
+
+
+JSP:JAVADOC:27 | void | jakarta.servlet.jsp.PageContext.forward
+
+ (
+ String
+ )
+ throws
+ IOException
+ | if an I/O error occurred while forwarding | true |
+
+ | true |
+
+
+JSP:JAVADOC:29 | void | jakarta.servlet.jsp.PageContext.forward
+
+ (
+ String
+ )
+ throws
+ IllegalStateException
+ | if ServletResponse is not in a state where a forward can be performed | true |
+
+ | true |
+
+
+JSP:JAVADOC:31 | void | jakarta.servlet.jsp.PageContext.include
+
+ (
+ String
+ )
+ | Causes the resource specified to be processed as part of the current ServletRequest and ServletResponse being processed by the calling Thread. The output of the target resources processing of the request is written directly to the ServletResponse output stream. The current JspWriter "out" for this JSP is flushed as a side-effect of this call, prior to processing the include. If the relativeUrlPath begins with a "/" then the URL specified is calculated relative to the DOCROOT of the ServletContext for this JSP. | true |
+
+ | true |
+
+
+JSP:JAVADOC:32 | void | jakarta.servlet.jsp.PageContext.include
+
+ (
+ String
+ )
+ | Causes the resource specified to be processed as part of the current ServletRequest and ServletResponse being processed by the calling Thread. The output of the target resources processing of the request is written directly to the ServletResponse output stream. The current JspWriter "out" for this JSP is flushed as a side-effect of this call, prior to processing the include. If the path does not begin with a "/" then the URL specified is calculated relative to the URL of the request that was mapped to the calling JSP. | true |
+
+ | true |
+
+
+JSP:JAVADOC:33 | void | jakarta.servlet.jsp.PageContext.include
+
+ (
+ String
+ )
+ | It is only valid to call this method from a Thread executing within a _jspService(...) method of a JSP. | true |
+
+ | false |
+
+
+JSP:JAVADOC:34 | void | jakarta.servlet.jsp.PageContext.include
+
+ (
+ String
+ )
+ throws
+ ServletException
+ | if the inclusion throws a ServletException ?????? | true |
+
+ | true |
+
+
+JSP:JAVADOC:35 | void | jakarta.servlet.jsp.PageContext.include
+
+ (
+ String
+ )
+ throws
+ IOException
+ | if an I/O error occurred while including | true |
+
+ | true |
+
+
+JSP:JAVADOC:38 | void | jakarta.servlet.jsp.PageContext.include
+
+ (
+ String
+ , boolean
+ )
+ | Causes the resource specified to be processed as part of the current ServletRequest and ServletResponse being processed by the calling Thread. If the relativeUrlPath begins with a "/" then the URL specified is calculated relative to the DOCROOT of the ServletContext for this JSP. | true |
+
+ | true |
+
+
+JSP:JAVADOC:39 | void | jakarta.servlet.jsp.PageContext.include
+
+ (
+ String
+ , boolean
+ )
+ | Causes the resource specified to be processed as part of the current ServletRequest and ServletResponse being processed by the calling Thread. If the path does not begin with a "/" then the URL specified is calculated relative to the URL of the request that was mapped to the calling JSP. | true |
+
+ | true |
+
+
+JSP:JAVADOC:40 | void | jakarta.servlet.jsp.PageContext.include
+
+ (
+ String
+ , boolean
+ )
+ | Causes the resource specified to be processed as part of the current ServletRequest and ServletResponse being processed by the calling Thread.
+ The output of the target resources processing of the request is written directly to the current JspWriter returned by a call to getOut(). If flush is true, The current JspWriter "out" for this JSP is flushed as a side-effect of this call, prior to processing the include.
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:385 | void | jakarta.servlet.jsp.PageContext.include
+
+ (
+ String
+ , boolean
+ )
+ | Causes the resource specified to be processed as part of the current ServletRequest and ServletResponse being processed by the calling Thread.
+ The output of the target resources processing of the request is written directly to the current JspWriter returned by a call to getOut(). If flush is false, "out" is not flushed.
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:41 | void | jakarta.servlet.jsp.PageContext.include
+
+ (
+ String
+ , boolean
+ )
+ | It is only valid to call this method from a Thread executing within a _jspService(...) method of a JSP. | true |
+
+ | false |
+
+
+JSP:JAVADOC:42 | void | jakarta.servlet.jsp.PageContext.include
+
+ (
+ String
+ , boolean
+ )
+ throws
+ ServletException
+ | if the page that was forwarded to throws a ServletException ???>??? | true |
+
+ | true |
+
+
+JSP:JAVADOC:43 | void | jakarta.servlet.jsp.PageContext.include
+
+ (
+ String
+ , boolean
+ )
+ throws
+ IOException
+ | if an I/O error occurred while including | true |
+
+ | true |
+
+
+JSP:JAVADOC:46 | void | jakarta.servlet.jsp.PageContext.handlePageException
+
+ (
+ Exception
+ )
+ | This method is intended to process an unhandled "page" level exception by forwarding the exception to the specified error page for this JSP. | true |
+
+ | true |
+
+
+JSP:JAVADOC:47 | void | jakarta.servlet.jsp.PageContext.handlePageException
+
+ (
+ Exception
+ )
+ | If forwarding is not possible (for example because the response has already been committed) an implementation dependent mechanism should be used to invoke the error page (e.g. 'including' the error page instead). | true |
+
+ | false |
+
+
+JSP:JAVADOC:48 | void | jakarta.servlet.jsp.PageContext.handlePageException
+
+ (
+ Exception
+ )
+ | A JSP implementation class shall typically clean up any local state prior to invoking this and will return immediately thereafter. It is illegal to generate any output to the client, or to modify any ServletResponse state after invoking this call. This method is kept for backwards compatiblity reasons. Newly generated code should use PageContext.handlePageException(Throwable). | true |
+
+ | false |
+
+
+JSP:JAVADOC:49 | void | jakarta.servlet.jsp.PageContext.handlePageException
+
+ (
+ Exception
+ )
+ throws
+ ServletException
+ | if an error occurs while invoking the error page | true |
+
+ | false |
+
+
+JSP:JAVADOC:50 | void | jakarta.servlet.jsp.PageContext.handlePageException
+
+ (
+ Exception
+ )
+ throws
+ IOException
+ | if an I/O error occurred while invoking the error page | true |
+
+ | false |
+
+
+JSP:JAVADOC:51 | void | jakarta.servlet.jsp.PageContext.handlePageException
+
+ (
+ Exception
+ )
+ throws
+ NullPointerException
+ | if the exception is null | true |
+
+ | true |
+
+
+JSP:JAVADOC:53 | void | jakarta.servlet.jsp.PageContext.handlePageException
+
+ (
+ Throwable
+ )
+ | This method is identical to the handlePageException(Exception), except that it accepts a Throwable.
+ This is the preferred method to use as it allows proper implementation of the errorpage semantics. This method is intended to process an unhandled "page" level exception by redirecting the exception to either the specified error page for this JSP.
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:54 | void | jakarta.servlet.jsp.PageContext.handlePageException
+
+ (
+ Throwable
+ )
+ | This method is identical to the handlePageException(Exception), except that it accepts a Throwable.
+ This is the preferred method to use as it allows proper implementation of the errorpage semantics. If no error page was specified, the result is implementation specific.
+ | true |
+
+ | false |
+
+
+JSP:JAVADOC:55 | void | jakarta.servlet.jsp.PageContext.handlePageException
+
+ (
+ Throwable
+ )
+ | A JSP implementation class shall typically clean up any local state prior to invoking this and will return immediately thereafter. It is illegal to generate any output to the client, or to modify any ServletResponse state after invoking this call. | true |
+
+ | false |
+
+
+JSP:JAVADOC:56 | void | jakarta.servlet.jsp.PageContext.handlePageException
+
+ (
+ Throwable
+ )
+ throws
+ ServletException
+ | if an error occurs while invoking the error page | true |
+
+ | false |
+
+
+JSP:JAVADOC:57 | void | jakarta.servlet.jsp.PageContext.handlePageException
+
+ (
+ Throwable
+ )
+ throws
+ IOException
+ | if an I/O error occurred while invoking the error page | true |
+
+ | false |
+
+
+JSP:JAVADOC:58 | void | jakarta.servlet.jsp.PageContext.handlePageException
+
+ (
+ Throwable
+ )
+ throws
+ NullPointerException
+ | if the exception is null | true |
+
+ | true |
+
+
+JSP:JAVADOC:59 | void | jakarta.servlet.jsp.PageContext.handlePageException
+
+ (
+ Throwable
+ )
+ throws
+ SecurityException
+ | if target resource cannot be accessed by caller | true |
+
+ | true |
+
+
+JSP:JAVADOC:60 | BodyContent | jakarta.servlet.jsp.PageContext.pushBody
+ | Return a new BodyContent object, save the current "out" JspWriter, and update the value of the "out" attribute in the page scope attribute namespace of the PageContext
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:61 | JspWriter | jakarta.servlet.jsp.PageContext.popBody
+ | Return the previous JspWriter "out" saved by the matching pushBody(), and update the value of the "out" attribute in the page scope attribute namespace of the JspConxtext
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:62 | ErrorData | jakarta.servlet.jsp.PageContext.getErrorData
+ | Provides convenient access to error information.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:63 | void | jakarta.servlet.jsp.JspWriter.newLine
+ | Write a line separator.
+ The line separator string is defined by the system property line.separator, and is not necessarily a single newline ('\n') character.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:64 | void | jakarta.servlet.jsp.JspWriter.newLine
+ throws
+ IOException
+ | If an I/O error occurs | true |
+
+ | false |
+
+
+JSP:JAVADOC:65 | void | jakarta.servlet.jsp.JspWriter.print
+
+ (
+ boolean
+ )
+ | Print a boolean value.
+
+
+ The string produced by is translated into bytes according to the platform's default character encoding, and these bytes are written in exactly the manner of the method.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:66 | void | jakarta.servlet.jsp.JspWriter.print
+
+ (
+ boolean
+ )
+ throws
+ IOException
+ | If an error occured while writing | true |
+
+ | false |
+
+
+JSP:JAVADOC:67 | void | jakarta.servlet.jsp.JspWriter.print
+
+ (
+ char
+ )
+ | Print a character.
+
+ The character is translated into one or more bytes according to the platform's default character encoding, and these bytes are written in exactly the manner of the method.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:68 | void | jakarta.servlet.jsp.JspWriter.print
+
+ (
+ char
+ )
+ throws
+ IOException
+ | If an error occured while writing | true |
+
+ | false |
+
+
+JSP:JAVADOC:69 | void | jakarta.servlet.jsp.JspWriter.print
+
+ (
+ int
+ )
+ | Print an integer.
+
+
+ The string produced by is translated into bytes according to the platform's default character encoding, and these bytes are written in exactly the manner of the method.
+
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:70 | void | jakarta.servlet.jsp.JspWriter.print
+
+ (
+ int
+ )
+ throws
+ IOException
+ | If an error occured while writing | true |
+
+ | false |
+
+
+JSP:JAVADOC:71 | void | jakarta.servlet.jsp.JspWriter.print
+
+ (
+ long
+ )
+ | Print a long integer.
+
+
+ The string produced by is translated into bytes according to the platform's default character encoding, and these bytes are written in exactly the manner of the method.
+
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:72 | void | jakarta.servlet.jsp.JspWriter.print
+
+ (
+ long
+ )
+ throws
+ IOException
+ | If an error occured while writing | true |
+
+ | false |
+
+
+JSP:JAVADOC:73 | void | jakarta.servlet.jsp.JspWriter.print
+
+ (
+ float
+ )
+ | Print a floating-point number.
+
+
+ The string produced by is translated into bytes according to the platform's default character encoding, and these bytes are written in exactly the manner of the method.
+
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:74 | void | jakarta.servlet.jsp.JspWriter.print
+
+ (
+ float
+ )
+ throws
+ IOException
+ | If an error occured while writing | true |
+
+ | false |
+
+
+JSP:JAVADOC:75 | void | jakarta.servlet.jsp.JspWriter.print
+
+ (
+ double
+ )
+ | Print a double-precision floating-point number.
+
+
+ The string produced by is translated into bytes according to the platform's default character encoding, and these bytes are written in exactly the manner of the method.
+
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:76 | void | jakarta.servlet.jsp.JspWriter.print
+
+ (
+ double
+ )
+ throws
+ IOException
+ | If an error occured while writing | true |
+
+ | false |
+
+
+JSP:JAVADOC:77 | void | jakarta.servlet.jsp.JspWriter.print
+
+ (
+ char[]
+ )
+ | Print an array of characters.
+
+ The characters are converted into bytes according to the platform's default character encoding, and these bytes are written in exactly the manner of the method.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:78 | void | jakarta.servlet.jsp.JspWriter.print
+
+ (
+ char[]
+ )
+ throws
+ IOException
+ | If an error occured while writing | true |
+
+ | false |
+
+
+JSP:JAVADOC:79 | void | jakarta.servlet.jsp.JspWriter.print
+
+ (
+ char[]
+ )
+ throws
+ NullPointerException
+ | If <code>s</code> is <code>null</code> | true |
+
+ | true |
+
+
+JSP:JAVADOC:80 | void | jakarta.servlet.jsp.JspWriter.print
+
+ (
+ String
+ )
+ | Print a string.
+
+ If the argument is null then the string "null" is printed. Otherwise, the string's characters are converted into bytes according to the platform's default character encoding, and these bytes are written in exactly the manner of the method.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:81 | void | jakarta.servlet.jsp.JspWriter.print
+
+ (
+ String
+ )
+ throws
+ IOException
+ | If an error occured while writing | true |
+
+ | false |
+
+
+JSP:JAVADOC:82 | void | jakarta.servlet.jsp.JspWriter.print
+
+ (
+ Object
+ )
+ | Print an object.
+
+
+ The string produced by the method is translated into bytes according to the platform's default character encoding, and these bytes are written in exactly the manner of the method.
+
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:83 | void | jakarta.servlet.jsp.JspWriter.print
+
+ (
+ Object
+ )
+ throws
+ IOException
+ | If an error occured while writing | true |
+
+ | false |
+
+
+JSP:JAVADOC:84 | void | jakarta.servlet.jsp.JspWriter.println
+ | Terminate the current line by writing the line separator string.
+ The line separator string is defined by the system property line.separator, and is not necessarily a single newline character ('\n').
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:85 | void | jakarta.servlet.jsp.JspWriter.println
+ throws
+ IOException
+ | If an error occured while writing | true |
+
+ | false |
+
+
+JSP:JAVADOC:86 | void | jakarta.servlet.jsp.JspWriter.println
+
+ (
+ boolean
+ )
+ | Print a boolean value and then terminate the line.
+
+
+ This method behaves as though it invokes and then .
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:87 | void | jakarta.servlet.jsp.JspWriter.println
+
+ (
+ boolean
+ )
+ throws
+ IOException
+ | If an error occured while writing | true |
+
+ | false |
+
+
+JSP:JAVADOC:88 | void | jakarta.servlet.jsp.JspWriter.println
+
+ (
+ char
+ )
+ | Print a character and then terminate the line.
+
+
+ This method behaves as though it invokes and then .
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:89 | void | jakarta.servlet.jsp.JspWriter.println
+
+ (
+ char
+ )
+ throws
+ IOException
+ | If an error occured while writing | true |
+
+ | false |
+
+
+JSP:JAVADOC:90 | void | jakarta.servlet.jsp.JspWriter.println
+
+ (
+ int
+ )
+ | Print an integer and then terminate the line.
+
+
+ This method behaves as though it invokes and then .
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:91 | void | jakarta.servlet.jsp.JspWriter.println
+
+ (
+ int
+ )
+ throws
+ IOException
+ | If an error occured while writing | true |
+
+ | false |
+
+
+JSP:JAVADOC:92 | void | jakarta.servlet.jsp.JspWriter.println
+
+ (
+ long
+ )
+ | Print a long integer and then terminate the line.
+
+
+ This method behaves as though it invokes and then .
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:93 | void | jakarta.servlet.jsp.JspWriter.println
+
+ (
+ long
+ )
+ throws
+ IOException
+ | If an error occured while writing | true |
+
+ | false |
+
+
+JSP:JAVADOC:94 | void | jakarta.servlet.jsp.JspWriter.println
+
+ (
+ float
+ )
+ | Print a floating-point number and then terminate the line.
+
+
+ This method behaves as though it invokes and then .
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:95 | void | jakarta.servlet.jsp.JspWriter.println
+
+ (
+ float
+ )
+ throws
+ IOException
+ | If an error occured while writing | true |
+
+ | false |
+
+
+JSP:JAVADOC:96 | void | jakarta.servlet.jsp.JspWriter.println
+
+ (
+ double
+ )
+ | Print a double-precision floating-point number and then terminate the line.
+
+
+ This method behaves as though it invokes and then .
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:97 | void | jakarta.servlet.jsp.JspWriter.println
+
+ (
+ double
+ )
+ throws
+ IOException
+ | If an error occured while writing | true |
+
+ | false |
+
+
+JSP:JAVADOC:98 | void | jakarta.servlet.jsp.JspWriter.println
+
+ (
+ char[]
+ )
+ | Print an array of characters and then terminate the line.
+ This method behaves as though it invokes print(char[]) and then println().
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:99 | void | jakarta.servlet.jsp.JspWriter.println
+
+ (
+ char[]
+ )
+ throws
+ IOException
+ | If an error occured while writing | true |
+
+ | false |
+
+
+JSP:JAVADOC:100 | void | jakarta.servlet.jsp.JspWriter.println
+
+ (
+ String
+ )
+ | Print a String and then terminate the line.
+
+
+ This method behaves as though it invokes and then .
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:101 | void | jakarta.servlet.jsp.JspWriter.println
+
+ (
+ String
+ )
+ throws
+ IOException
+ | If an error occured while writing | true |
+
+ | false |
+
+
+JSP:JAVADOC:102 | void | jakarta.servlet.jsp.JspWriter.println
+
+ (
+ Object
+ )
+ | Print an Object and then terminate the line.
+
+
+ This method behaves as though it invokes and then .
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:103 | void | jakarta.servlet.jsp.JspWriter.println
+
+ (
+ Object
+ )
+ throws
+ IOException
+ | If an error occured while writing | true |
+
+ | false |
+
+
+JSP:JAVADOC:104 | void | jakarta.servlet.jsp.JspWriter.clear
+ | Clear the contents of the buffer.
+ If the buffer has been already been flushed then the clear operation shall throw an IOException to signal the fact that some data has already been irrevocably written to the client response stream.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:105 | void | jakarta.servlet.jsp.JspWriter.clear
+ throws
+ IOException
+ | If an I/O error occurs | true |
+
+ | true |
+
+
+JSP:JAVADOC:106 | void | jakarta.servlet.jsp.JspWriter.clearBuffer
+ | Clears the current contents of the buffer.
+ Unlike clear(), this method will not throw an IOException if the buffer has already been flushed. It merely clears the current content of the buffer and returns.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:107 | void | jakarta.servlet.jsp.JspWriter.clearBuffer
+ throws
+ IOException
+ | If an I/O error occurs | true |
+
+ | false |
+
+
+JSP:JAVADOC:108 | void | jakarta.servlet.jsp.JspWriter.flush
+ | Flush the stream.
+ If the stream has saved any characters from the various write() methods in a buffer, write them immediately to their intended destination. Then, if that destination is another character or byte stream, flush it. Thus one flush() invocation will flush all the buffers in a chain of Writers and OutputStreams. The method may be invoked indirectly if the buffer size is exceeded. Once a stream has been closed, further write() or flush() invocations will cause an IOException to be thrown.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:109 | void | jakarta.servlet.jsp.JspWriter.flush
+ throws
+ IOException
+ | If an I/O error occurs | true |
+
+ | true |
+
+
+JSP:JAVADOC:110 | void | jakarta.servlet.jsp.JspWriter.close
+ | Close the stream, flushing it first.
+ This method needs not be invoked explicitly for the initial JspWriter as the code generated by the JSP container will automatically include a call to close(). Closing a previously-closed stream, unlike flush(), has no effect.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:111 | void | jakarta.servlet.jsp.JspWriter.close
+ throws
+ IOException
+ | If an I/O error occurs | true |
+
+ | false |
+
+
+JSP:JAVADOC:112 | int | jakarta.servlet.jsp.JspWriter.getBufferSize
+ | This method returns the size of the buffer used by the JspWriter.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:113 | int | jakarta.servlet.jsp.JspWriter.getRemaining
+ | This method returns the number of unused bytes in the buffer.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:114 | boolean | jakarta.servlet.jsp.JspWriter.isAutoFlush
+ | This method indicates whether the JspWriter is autoFlushing.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:115 | JspTagException | jakarta.servlet.jsp.JspTagException.JspTagException
+
+ (
+ String
+ )
+ | Constructs a new JspTagException with the specified message.
+ The message can be written to the server log and/or displayed for the user.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:116 | JspTagException | jakarta.servlet.jsp.JspTagException.JspTagException
+ | Constructs a new JspTagException with no message.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:117 | JspTagException | jakarta.servlet.jsp.JspTagException.JspTagException
+
+ (
+ String
+ , Throwable
+ )
+ | Constructs a new JspTagException when the JSP Tag needs to throw an exception and include a message about the "root cause" exception that interfered with its normal operation, including a description message.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:118 | JspTagException | jakarta.servlet.jsp.JspTagException.JspTagException
+
+ (
+ Throwable
+ )
+ | Constructs a new JSP Tag exception when the JSP Tag needs to throw an exception and include a message about the "root cause" exception that interfered with its normal operation.
+ The exception's message is based on the localized message of the underlying exception. This method calls the getLocalizedMessage method on the Throwable exception to get a localized exception message. When subclassing JspTagException, this method can be overridden to create an exception message designed for a specific locale.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:119 | JspFactory | jakarta.servlet.jsp.JspFactory.JspFactory
+ |
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:120 | void | jakarta.servlet.jsp.JspFactory.setDefaultFactory
+
+ (
+ JspFactory
+ )
+ | set the default factory for this implementation.
+ It is illegal for any principal other than the JSP Engine runtime to call this method.
+
+ | true |
+
+ | false |
+
+
+JSP:JAVADOC:121 | JspFactory | jakarta.servlet.jsp.JspFactory.getDefaultFactory
+ | Returns the default factory for this implementation.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:122 | PageContext | jakarta.servlet.jsp.JspFactory.getPageContext
+
+ (
+ Servlet
+ , ServletRequest
+ , ServletResponse
+ , String
+ , boolean
+ , int
+ , boolean
+ )
+ | obtains an instance of an implementation dependent jakarta.servlet.jsp.PageContext abstract class for the calling Servlet and currently pending request and response.
+ This method is typically called early in the processing of the _jspService() method of a JSP implementation class in order to obtain a PageContext object for the request being processed. Invoking this method shall result in the PageContext.initialize() method being invoked. The PageContext returned is properly initialized. All PageContext objects obtained via this method shall be released by invoking releasePageContext().
+
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:123 | void | jakarta.servlet.jsp.JspFactory.releasePageContext
+
+ (
+ PageContext
+ )
+ | called to release a previously allocated PageContext object.
+ Results in PageContext.release() being invoked. This method should be invoked prior to returning from the _jspService() method of a JSP implementation class.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:124 | JspEngineInfo | jakarta.servlet.jsp.JspFactory.getEngineInfo
+ | called to get implementation-specific information on the current JSP engine.
+
+
+ | true |
+
+ | false |
+
+
+JSP:JAVADOC:125 | JspException | jakarta.servlet.jsp.JspException.JspException
+ | Construct a JspException
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:126 | JspException | jakarta.servlet.jsp.JspException.JspException
+
+ (
+ String
+ )
+ | Constructs a new JSP exception with the specified message.
+ The message can be written to the server log and/or displayed for the user.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:127 | JspException | jakarta.servlet.jsp.JspException.JspException
+
+ (
+ String
+ , Throwable
+ )
+ | Constructs a new JSP exception when the JSP needs to throw an exception and include a message about the "root cause" exception that interfered with its normal operation, including a description message.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:128 | JspException | jakarta.servlet.jsp.JspException.JspException
+
+ (
+ Throwable
+ )
+ | Constructs a new JSP exception when the JSP needs to throw an exception and include a message about the "root cause" exception that interfered with its normal operation.
+ The exception's message is based on the localized message of the underlying exception. This method calls the getLocalizedMessage method on the Throwable exception to get a localized exception message. When subclassing JspException, this method can be overridden to create an exception message designed for a specific locale.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:129 | Throwable | jakarta.servlet.jsp.JspException.getRootCause
+ | Returns the exception that caused this JSP exception.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:130 | JspEngineInfo | jakarta.servlet.jsp.JspEngineInfo.JspEngineInfo
+ |
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:131 | String | jakarta.servlet.jsp.JspEngineInfo.getSpecificationVersion
+ | Return the version number of the JSP specification that is supported by this JSP engine.
+ Specification version numbers that consists of positive decimal integers separated by periods ".", for example, "2.0" or "1.2.3.4.5.6.7". This allows an extensible number to be used to represent major, minor, micro, etc versions. The version number must begin with a number.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:132 | JspContext | jakarta.servlet.jsp.JspContext.JspContext
+ |
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:380 | JspWriter | jakarta.servlet.jsp.JspContext.popBody
+ | Return the previous JspWriter 'out' saved by the matching pushBody() and update the value of the 'out' attribute in the page scope attribute namespace of the JspContext.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:381 | JspWriter | jakarta.servlet.jsp.JspContext.pushBody
+
+ (
+ Writer
+ )
+ | Return a new JspWriter object that sends output to the provided writer. | true |
+
+ | true |
+
+
+JSP:JAVADOC:133 | void | jakarta.servlet.jsp.JspContext.setAttribute
+
+ (
+ String
+ , Object
+ )
+ | Register the name and value specified with page scope semantics.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:396 | void | jakarta.servlet.jsp.JspContext.setAttribute
+
+ (
+ String
+ , Object
+ )
+ | If the value passed is null, this has the same effect as calling removeAttribute(name, PageContext.PAGE_SCOPE).
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:134 | void | jakarta.servlet.jsp.JspContext.setAttribute
+
+ (
+ String
+ , Object
+ )
+ throws
+ NullPointerException
+ | if the name is null | true |
+
+ | true |
+
+
+JSP:JAVADOC:135 | void | jakarta.servlet.jsp.JspContext.setAttribute
+
+ (
+ String
+ , Object
+ , int
+ )
+ | register the name and value specified with appropriate scope semantics.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:397 | void | jakarta.servlet.jsp.JspContext.setAttribute
+
+ (
+ String
+ , Object
+ , int
+ )
+ | If the value passed in is null this has the same effect as calling removeAttribute(name, scope).
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:136 | void | jakarta.servlet.jsp.JspContext.setAttribute
+
+ (
+ String
+ , Object
+ , int
+ )
+ throws
+ NullPointerException
+ | if the name is null | true |
+
+ | true |
+
+
+JSP:JAVADOC:398 | void | jakarta.servlet.jsp.JspContext.setAttribute
+
+ (
+ String
+ , Object
+ , int
+ )
+ throws
+ IllegalArgumentException
+ | if the scope is invalid | true |
+
+ | true |
+
+
+JSP:JAVADOC:399 | void | jakarta.servlet.jsp.JspContext.setAttribute
+
+ (
+ String
+ , Object
+ , int
+ )
+ throws
+ IllegalStateException
+ | If the scope is PageContext.SESSION_SCOPE but the page that was requested does not participate in a session or the session has been invalidated. | true |
+
+ | true |
+
+
+JSP:JAVADOC:137 | void | jakarta.servlet.jsp.JspContext.setAttribute
+
+ (
+ String
+ , Object
+ , int
+ )
+ throws
+ IllegalArgumentException
+ | if the scope is invalid | true |
+
+ | true |
+
+
+JSP:JAVADOC:138 | Object | jakarta.servlet.jsp.JspContext.getAttribute
+
+ (
+ String
+ )
+ | Returns the object associated with the name in the page scope or null if not found.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:139 | Object | jakarta.servlet.jsp.JspContext.getAttribute
+
+ (
+ String
+ )
+ throws
+ NullPointerException
+ | if the name is null | true |
+
+ | true |
+
+
+JSP:JAVADOC:141 | Object | jakarta.servlet.jsp.JspContext.getAttribute
+
+ (
+ String
+ , int
+ )
+ | Return the object associated with the name in the specified scope or null if not found.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:142 | Object | jakarta.servlet.jsp.JspContext.getAttribute
+
+ (
+ String
+ , int
+ )
+ throws
+ NullPointerException
+ | if the name is null | true |
+
+ | true |
+
+
+JSP:JAVADOC:143 | Object | jakarta.servlet.jsp.JspContext.getAttribute
+
+ (
+ String
+ , int
+ )
+ throws
+ IllegalArgumentException
+ | if the scope is invalid | true |
+
+ | true |
+
+
+JSP:JAVADOC:390 | Object | jakarta.servlet.jsp.JspContext.getAttribute
+
+ (
+ String
+ , int
+ )
+ throws
+ IllegalStateException
+ | if the scope is PageContext.SESSION_SCOPE but the page that was requested does not participate in a session or the session has been invalidated | true |
+
+ | true |
+
+
+JSP:JAVADOC:144 | Object | jakarta.servlet.jsp.JspContext.findAttribute
+
+ (
+ String
+ )
+ | Searches for the named attribute in page, request, session (if valid), and application scope(s) in order and returns the value associated or null.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:387 | Object | jakarta.servlet.jsp.JspContext.findAttribute
+
+ (
+ String
+ )
+ throws
+ NullPointerException
+ | If the name is null
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:145 | void | jakarta.servlet.jsp.JspContext.removeAttribute
+
+ (
+ String
+ )
+ | Remove the object reference associated with the given name from all scopes. Does nothing if there is no such object.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:391 | void | jakarta.servlet.jsp.JspContext.removeAttribute
+
+ (
+ String
+ )
+ throws
+ NullPointerException
+ | if the name is null
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:146 | void | jakarta.servlet.jsp.JspContext.removeAttribute
+
+ (
+ String
+ , int
+ )
+ | Remove the object reference associated with the specified name in the given scope. Does nothing if there is no such object.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:392 | void | jakarta.servlet.jsp.JspContext.removeAttribute
+
+ (
+ String
+ , int
+ )
+ throws
+ IllegalArgumentException
+ | If the scope is invalid
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:393 | void | jakarta.servlet.jsp.JspContext.removeAttribute
+
+ (
+ String
+ , int
+ )
+ throws
+ NullPointerException
+ | If the name is null
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:394 | void | jakarta.servlet.jsp.JspContext.removeAttribute
+
+ (
+ String
+ , int
+ )
+ throws
+ IllegalStateException
+ | If the scope is PageContext.SESSION_SCOPE but the page that was requested does not particpate in a session or the session has been invalidated.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:147 | int | jakarta.servlet.jsp.JspContext.getAttributesScope
+
+ (
+ String
+ )
+ | Get the scope where a given attribute is defined.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:389 | int | jakarta.servlet.jsp.JspContext.getAttributesScope
+
+ (
+ String
+ )
+ throws
+ NullPointerException
+ | if the name is null
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:148 | Enumeration | jakarta.servlet.jsp.JspContext.getAttributeNamesInScope
+
+ (
+ int
+ )
+ | Enumerate all the attributes in a given scope
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:387 | Enumeration | jakarta.servlet.jsp.JspContext.getAttributeNamesInScope
+
+ (
+ int
+ )
+ throws
+ IllegalArgumentException
+ | if the scope is invalid
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:388 | Enumeration | jakarta.servlet.jsp.JspContext.getAttributeNamesInScope
+
+ (
+ int
+ )
+ throws
+ IllegalStateException
+ | If the scope is PageContext.SESSION_SCOPE but the page that was requested does not participate in a session or the session has been invalidated.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:149 | JspWriter | jakarta.servlet.jsp.JspContext.getOut
+ | The current value of the out object (a JspWriter).
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:150 | ExpressionEvaluator | jakarta.servlet.jsp.JspContext.getExpressionEvaluator
+ | Provides programmatic access to the ExpressionEvaluator.
+ The JSP Container must return a valid instance of an ExpressionEvaluator that can parse EL expressions.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:151 | VariableResolver | jakarta.servlet.jsp.JspContext.getVariableResolver
+ | Returns an instance of a VariableResolver that provides access to the implicit objects specified in the JSP specification using this JspContext as the context object
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:152 | void | jakarta.servlet.jsp.JspPage.jspInit
+ | The jspInit() method is invoked when the JSP page is initialized.
+ It is the responsibility of the JSP implementation (and of the class mentioned by the extends attribute, if present) that at this point invocations to the getServletConfig() method will return the desired value. A JSP page can override this method by including a definition for it in a declaration element. A JSP page should redefine the init() method from Servlet.
+
+ | true |
+
+ | false |
+
+
+JSP:JAVADOC:153 | void | jakarta.servlet.jsp.JspPage.jspDestroy
+ | The jspDestroy() method is invoked when the JSP page is about to be destroyed.
+ A JSP page can override this method by including a definition for it in a declaration element. A JSP page should redefine the destroy() method from Servlet.
+
+ | true |
+
+ | false |
+
+
+JSP:JAVADOC:154 | void | jakarta.servlet.jsp.HttpJspPage._jspService
+
+ (
+ HttpServletRequest
+ , HttpServletResponse
+ )
+ | The _jspService() method corresponds to the body of the JSP page.
+ This method is defined automatically by the JSP container and should never be defined by the JSP page author. If a superclass is specified using the extends attribute, that superclass may choose to perform some actions in its service() method before or after calling the _jspService() method. See using the extends attribute in the JSP_Engine chapter of the JSP specification.
+
+ | true |
+
+ | false |
+
+
+JSP:JAVADOC:155 | void | jakarta.servlet.jsp.HttpJspPage._jspService
+
+ (
+ HttpServletRequest
+ , HttpServletResponse
+ )
+ throws
+ ServletException
+ | Thrown if an error occurred during the processing of the JSP and that the container should take appropriate action to clean up the request. | true |
+
+ | false |
+
+
+JSP:JAVADOC:156 | void | jakarta.servlet.jsp.HttpJspPage._jspService
+
+ (
+ HttpServletRequest
+ , HttpServletResponse
+ )
+ throws
+ IOException
+ | Thrown if an error occurred while writing the response for this page. | true |
+
+ | false |
+
+
+JSP:JAVADOC:157 | ELParseException | jakarta.servlet.jsp.el.ELParseException.ELParseException
+ | Creates an ELParseException with no detail message.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:158 | ELParseException | jakarta.servlet.jsp.el.ELParseException.ELParseException
+
+ (
+ String
+ )
+ | Creates an ELParseException with the provided detail message.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:159 | ELException | jakarta.servlet.jsp.el.ELException.ELException
+ | Creates an ELException with no detail message.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:160 | ELException | jakarta.servlet.jsp.el.ELException.ELException
+
+ (
+ String
+ )
+ | Creates an ELException with the provided detail message.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:161 | ELException | jakarta.servlet.jsp.el.ELException.ELException
+
+ (
+ Throwable
+ )
+ | Creates an ELException with the given root cause
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:162 | ELException | jakarta.servlet.jsp.el.ELException.ELException
+
+ (
+ String
+ , Throwable
+ )
+ | Creates an ELException with the given detail message and root cause.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:163 | Throwable | jakarta.servlet.jsp.el.ELException.getRootCause
+ | Returns the root cause
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:165 | Method | jakarta.servlet.jsp.el.FunctionMapper.resolveFunction
+
+ (
+ String
+ , String
+ )
+ | Resolves the specified local name and prefix into a Java.lang.Method.
+ Returns null if the prefix and local name are not found.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:384 | Object | jakarta.servlet.jsp.el.VariableResolver.resolveVariable
+
+ (
+ String
+ )
+ | Resolves the specified variable.
+ Returns null if the variable is not found.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:167 | Object | jakarta.servlet.jsp.el.VariableResolver.resolveVariable
+
+ (
+ String
+ , Object
+ )
+ throws
+ ELException
+ | if a failure occurred while trying to resolve the given variable | true |
+
+ | false |
+
+
+JSP:JAVADOC:379 | ExpressionEvaluator | jakarta.servlet.jsp.el.ExpressionEvaluator.ExpressionEvaluator
+ | Default constructor. | true |
+
+ | false |
+
+
+JSP:JAVADOC:168 | Expression | jakarta.servlet.jsp.el.ExpressionEvaluator.parseExpression
+
+ (
+ String
+ , Class
+ , FunctionMapper
+ , String
+ )
+ | Prepare an expression for later evaluation. | true |
+
+ | true |
+
+
+JSP:JAVADOC:169 | Expression | jakarta.servlet.jsp.el.ExpressionEvaluator.parseExpression
+
+ (
+ String
+ , Class
+ , FunctionMapper
+ , String
+ )
+ | This method should perform syntactic validation of the expression; if in doing so it detects errors, it should raise an ELParseException.
+
+ | false |
+
+ | false |
+
+
+JSP:JAVADOC:170 | Expression | jakarta.servlet.jsp.el.ExpressionEvaluator.parseExpression
+
+ (
+ String
+ , Class
+ , FunctionMapper
+ , String
+ )
+ throws
+ ELException
+ | Thrown if parsing errors were found. | false |
+
+ | false |
+
+
+JSP:JAVADOC:171 | Object | jakarta.servlet.jsp.el.ExpressionEvaluator.evaluate
+
+ (
+ String
+ , Class
+ , VariableResolver
+ , FunctionMapper
+ , String
+ )
+ | Evaluates an expression. | true |
+
+ | true |
+
+
+JSP:JAVADOC:172 | Object | jakarta.servlet.jsp.el.ExpressionEvaluator.evaluate
+
+ (
+ String
+ , Class
+ , VariableResolver
+ , FunctionMapper
+ , String
+ )
+ | This method may perform some syntactic validation and, if so, it should raise an ELParseException error if it encounters syntactic errors. EL evaluation errors should cause an ELException to be raised. | false |
+
+ | false |
+
+
+JSP:JAVADOC:173 | Object | jakarta.servlet.jsp.el.ExpressionEvaluator.evaluate
+
+ (
+ String
+ , Class
+ , VariableResolver
+ , FunctionMapper
+ , String
+ )
+ throws
+ ELException
+ | Thrown if the expression evaluation failed. | true |
+
+ | true |
+
+
+JSP:JAVADOC:378 | Expression | jakarta.servlet.jsp.el.Expression.Expression
+ | Default constructor | true |
+
+ | false |
+
+
+JSP:JAVADOC:174 | Object | jakarta.servlet.jsp.el.Expression.evaluate
+
+ (
+ VariableResolver
+ )
+ | Evaluates an expression that was previously prepared. | true |
+
+ | true |
+
+
+JSP:JAVADOC:175 | Object | jakarta.servlet.jsp.el.Expression.evaluate
+
+ (
+ VariableResolver
+ )
+ | In some implementations preparing an expression involves full syntactic validation, but others may not do so. Evaluating the expression may raise an ELParseException as well as other ELExceptions due to run-time evaluation.
+
+ | false |
+
+ | false |
+
+
+JSP:JAVADOC:176 | Object | jakarta.servlet.jsp.el.Expression.evaluate
+
+ (
+ VariableResolver
+ )
+ throws
+ ELException
+ | Thrown if the expression evaluation failed. | true |
+
+ | true |
+
+
+JSP:JAVADOC:177 | VariableInfo | jakarta.servlet.jsp.tagext.VariableInfo.VariableInfo
+
+ (
+ String
+ , String
+ , boolean
+ , int
+ )
+ | Constructor These objects can be created (at translation time) by the TagExtraInfo instances.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:178 | String | jakarta.servlet.jsp.tagext.VariableInfo.getVarName
+ | Returns the name of the scripting variable
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:179 | String | jakarta.servlet.jsp.tagext.VariableInfo.getClassName
+ | Returns the type of this variable
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:180 | boolean | jakarta.servlet.jsp.tagext.VariableInfo.getDeclare
+ | Returns whether this is a new variable.
+ If so, in some languages this will require a declaration.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:181 | int | jakarta.servlet.jsp.tagext.VariableInfo.getScope
+ | Returns the lexical scope of the variable.
+
+
+
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:182 | ValidationMessage | jakarta.servlet.jsp.tagext.ValidationMessage.ValidationMessage
+
+ (
+ String
+ , String
+ )
+ | Create a ValidationMessage.
+ The message String should be non-null. The value of id may be null, if the message is not specific to any XML element, or if no jsp:id attributes were passed on. If non-null, the value of id must be the value of a jsp:id attribute for the PageData passed into the validate() method.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:183 | String | jakarta.servlet.jsp.tagext.ValidationMessage.getId
+ | Get the jsp:id.
+ Null means that there is no information available.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:184 | String | jakarta.servlet.jsp.tagext.ValidationMessage.getMessage
+ | Get the localized validation message.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:185 | TagVariableInfo | jakarta.servlet.jsp.tagext.TagVariableInfo.TagVariableInfo
+
+ (
+ String
+ , String
+ , String
+ , boolean
+ , int
+ )
+ | Constructor for TagVariableInfo
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:187 | String | jakarta.servlet.jsp.tagext.TagVariableInfo.getNameGiven
+ | The body of the <name-given> element
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:188 | String | jakarta.servlet.jsp.tagext.TagVariableInfo.getNameFromAttribute
+ | The body of the <name-from-attribute> element.
+ This is the name of an attribute whose (translation-time) value will give the name of the variable. One of or is required.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:189 | String | jakarta.servlet.jsp.tagext.TagVariableInfo.getClassName
+ | The body of the <class-name> element.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:190 | boolean | jakarta.servlet.jsp.tagext.TagVariableInfo.getDeclare
+ | The body of the <declare> element
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:191 | int | jakarta.servlet.jsp.tagext.TagVariableInfo.getScope
+ | The body of the <scope> element
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:193 | TagSupport | jakarta.servlet.jsp.tagext.TagSupport.TagSupport
+ | Default constructor, all subclasses are required to define only a public constructor with the same signature, and to call the superclass constructor.
+ This constructor is called by the code generated by the JSP translator.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:194 | Tag | jakarta.servlet.jsp.tagext.TagSupport.findAncestorWithClass
+
+ (
+ Tag
+ , Class
+ )
+ | Find the instance of a given class type that is closest to a given instance.
+ This method uses the getParent method from the Tag interface. This method is used for coordination among cooperating tags. The current version of the specification only provides one formal way of indicating the observable type of a tag handler: its tag handler implementation class, described in the tag-class subelement of the tag element. This is extended in an informal manner by allowing the tag library author to indicate in the description subelement an observable type. The type should be a subtype of the tag handler implementation class or void. This addititional constraint can be exploited by a specialized container that knows about that specific tag library, as in the case of the JSP standard tag library. When a tag library author provides information on the observable type of a tag handler, client programmatic code should adhere to that constraint. Specifically, the Class passed to findAncestorWithClass should be a subtype of the observable type.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:195 | int | jakarta.servlet.jsp.tagext.TagSupport.doStartTag
+ | Default processing of the start tag, returning SKIP_BODY.
+
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:196 | int | jakarta.servlet.jsp.tagext.TagSupport.doStartTag
+ throws
+ JspException
+ | if an error occurs while processing this tag | true |
+
+ | false |
+
+
+JSP:JAVADOC:197 | int | jakarta.servlet.jsp.tagext.TagSupport.doEndTag
+ | Default processing of the end tag returning EVAL_PAGE.
+
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:198 | int | jakarta.servlet.jsp.tagext.TagSupport.doEndTag
+ throws
+ JspException
+ | if an error occurs while processing this tag | true |
+
+ | false |
+
+
+JSP:JAVADOC:199 | int | jakarta.servlet.jsp.tagext.TagSupport.doAfterBody
+ | Default processing for a body
+
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:200 | int | jakarta.servlet.jsp.tagext.TagSupport.doAfterBody
+ throws
+ JspException
+ | if an error occurs while processing this tag | true |
+
+ | false |
+
+
+JSP:JAVADOC:201 | void | jakarta.servlet.jsp.tagext.TagSupport.release
+ | Release state.
+
+
+ | true |
+
+ | false |
+
+
+JSP:JAVADOC:202 | void | jakarta.servlet.jsp.tagext.TagSupport.setParent
+
+ (
+ Tag
+ )
+ | Set the nesting tag of this tag.
+
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:203 | Tag | jakarta.servlet.jsp.tagext.TagSupport.getParent
+ | The Tag instance most closely enclosing this tag instance.
+
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:204 | void | jakarta.servlet.jsp.tagext.TagSupport.setId
+
+ (
+ String
+ )
+ | Set the id attribute for this tag.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:205 | String | jakarta.servlet.jsp.tagext.TagSupport.getId
+ | The value of the id attribute of this tag; or null.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:206 | void | jakarta.servlet.jsp.tagext.TagSupport.setPageContext
+
+ (
+ PageContext
+ )
+ | Set the page context.
+
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:207 | void | jakarta.servlet.jsp.tagext.TagSupport.setValue
+
+ (
+ String
+ , Object
+ )
+ | Associate a value with a String key.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:208 | Object | jakarta.servlet.jsp.tagext.TagSupport.getValue
+
+ (
+ String
+ )
+ | Get a the value associated with a key.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:209 | void | jakarta.servlet.jsp.tagext.TagSupport.removeValue
+
+ (
+ String
+ )
+ | Remove a value associated with a key.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:210 | Enumeration | jakarta.servlet.jsp.tagext.TagSupport.getValues
+ | Enumerate the keys for the values kept by this tag handler.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:211 | TagLibraryValidator | jakarta.servlet.jsp.tagext.TagLibraryValidator.TagLibraryValidator
+ |
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:212 | void | jakarta.servlet.jsp.tagext.TagLibraryValidator.setInitParameters
+
+ (
+ Map
+ )
+ | Set the init data in the TLD for this validator.
+ Parameter names are keys, and parameter values are the values.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:213 | Map | jakarta.servlet.jsp.tagext.TagLibraryValidator.getInitParameters
+ | Get the init parameters data as an immutable Map.
+ Parameter names are keys, and parameter values are the values.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:214 | ValidationMessage[] | jakarta.servlet.jsp.tagext.TagLibraryValidator.validate
+
+ (
+ String
+ , String
+ , PageData
+ )
+ | Validate a JSP page.
+ This will get invoked once per directive in the JSP page. This method will return null if the page is valid; otherwise the method should return an array of ValidationMessage objects. An array of length zero is also interpreted as no errors.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:386 | ValidationMessage[] | jakarta.servlet.jsp.tagext.TagLibraryValidator.validate
+
+ (
+ String
+ , String
+ , PageData
+ )
+ | Validate a JSP page.
+ This will get invoked once per directive in the JSP page. An array of length greater than zero is interpreted as an error (translation error occurs).
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:215 | void | jakarta.servlet.jsp.tagext.TagLibraryValidator.release
+ | Release any data kept by this instance for validation purposes
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:216 | String | jakarta.servlet.jsp.tagext.TagLibraryInfo.getURI
+ | The value of the uri attribute from the taglib directive for this library.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:218 | String | jakarta.servlet.jsp.tagext.TagLibraryInfo.getPrefixString
+ | The prefix assigned to this taglib from the taglib directive
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:219 | String | jakarta.servlet.jsp.tagext.TagLibraryInfo.getShortName
+ | The preferred short name (prefix) as indicated in the TLD.
+ This may be used by authoring tools as the preferred prefix to use when creating an taglib directive for this library.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:220 | String | jakarta.servlet.jsp.tagext.TagLibraryInfo.getReliableURN
+ | The "reliable" URN indicated in the TLD (the uri element).
+ This may be used by authoring tools as a global identifier to use when creating a taglib directive for this library.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:221 | String | jakarta.servlet.jsp.tagext.TagLibraryInfo.getInfoString
+ | Information (documentation) for this TLD.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:222 | String | jakarta.servlet.jsp.tagext.TagLibraryInfo.getRequiredVersion
+ | A string describing the required version of the JSP container.
+
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:223 | TagInfo[] | jakarta.servlet.jsp.tagext.TagLibraryInfo.getTags
+ | An array describing the tags that are defined in this tag library.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:224 | TagFileInfo[] | jakarta.servlet.jsp.tagext.TagLibraryInfo.getTagFiles
+ | An array describing the tag files that are defined in this tag library.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:225 | TagInfo | jakarta.servlet.jsp.tagext.TagLibraryInfo.getTag
+
+ (
+ String
+ )
+ | Get the TagInfo for a given tag name, looking through all the tags in this tag library.
+ Returns null if no tag is found.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:226 | TagFileInfo | jakarta.servlet.jsp.tagext.TagLibraryInfo.getTagFile
+
+ (
+ String
+ )
+ | Get the TagFileInfo for a given tag name, looking through all the tag files in this tag library.
+ Returns null if no tag file is found.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:227 | FunctionInfo[] | jakarta.servlet.jsp.tagext.TagLibraryInfo.getFunctions
+ | An array describing the functions that are defined in this tag library.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:228 | FunctionInfo | jakarta.servlet.jsp.tagext.TagLibraryInfo.getFunction
+
+ (
+ String
+ )
+ | Get the FunctionInfo for a given function name, looking through all the functions in this tag library.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:229 | TagInfo | jakarta.servlet.jsp.tagext.TagInfo.TagInfo
+
+ (
+ String
+ , String
+ , String
+ , String
+ , TagLibraryInfo
+ , TagExtraInfo
+ , TagAttributeInfo[]
+ )
+ | Constructor for TagInfo from data in the JSP 2.0 format for TLD.
+ This class is to be instantiated only from the TagLibrary code under request from some JSP code that is parsing a TLD (Tag Library Descriptor). Note that, since TagLibibraryInfo reflects both TLD information and taglib directive information, a TagInfo instance is dependent on a taglib directive. This is probably a design error, which may be fixed in the future.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:230 | TagInfo | jakarta.servlet.jsp.tagext.TagInfo.TagInfo
+
+ (
+ String
+ , String
+ , String
+ , String
+ , TagLibraryInfo
+ , TagExtraInfo
+ , TagAttributeInfo[]
+ , String
+ , String
+ , String
+ , TagVariableInfo[]
+ )
+ | Constructor for TagInfo from data in the JSP 1.2 format for TLD.
+ This class is to be instantiated only from the TagLibrary code under request from some JSP code that is parsing a TLD (Tag Library Descriptor). Note that, since TagLibibraryInfo reflects both TLD information and taglib directive information, a TagInfo instance is dependent on a taglib directive. This is probably a design error, which may be fixed in the future.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:231 | TagInfo | jakarta.servlet.jsp.tagext.TagInfo.TagInfo
+
+ (
+ String
+ , String
+ , String
+ , String
+ , TagLibraryInfo
+ , TagExtraInfo
+ , TagAttributeInfo[]
+ , String
+ , String
+ , String
+ , TagVariableInfo[]
+ , boolean
+ )
+ | Constructor for TagInfo from data in the JSP 2.0 format for TLD.
+ This class is to be instantiated only from the TagLibrary code under request from some JSP code that is parsing a TLD (Tag Library Descriptor). Note that, since TagLibibraryInfo reflects both TLD information and taglib directive information, a TagInfo instance is dependent on a taglib directive. This is probably a design error, which may be fixed in the future.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:232 | String | jakarta.servlet.jsp.tagext.TagInfo.getTagName
+ | The name of the Tag.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:233 | TagAttributeInfo[] | jakarta.servlet.jsp.tagext.TagInfo.getAttributes
+ | Attribute information (in the TLD) on this tag.
+ The return is an array describing the attributes of this tag, as indicated in the TLD. or a zero-length array if the tag has no attributes.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:234 | VariableInfo[] | jakarta.servlet.jsp.tagext.TagInfo.getVariableInfo
+
+ (
+ TagData
+ )
+ | Information on the scripting objects created by this tag at runtime.
+ This is a convenience method on the associated TagExtraInfo class. Default is null if the tag has no "id" attribute, otherwise, {"id", Object}
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:235 | boolean | jakarta.servlet.jsp.tagext.TagInfo.isValid
+
+ (
+ TagData
+ )
+ | Translation-time validation of the attributes.
+ This is a convenience method on the associated TagExtraInfo class.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:236 | ValidationMessage[] | jakarta.servlet.jsp.tagext.TagInfo.validate
+
+ (
+ TagData
+ )
+ | Translation-time validation of the attributes.
+ This is a convenience method on the associated TagExtraInfo class.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:237 | void | jakarta.servlet.jsp.tagext.TagInfo.setTagExtraInfo
+
+ (
+ TagExtraInfo
+ )
+ | Set the instance for extra tag information
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:238 | TagExtraInfo | jakarta.servlet.jsp.tagext.TagInfo.getTagExtraInfo
+ | The instance (if any) for extra tag information
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:239 | String | jakarta.servlet.jsp.tagext.TagInfo.getTagClassName
+ | Name of the class that provides the handler for this tag.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:240 | String | jakarta.servlet.jsp.tagext.TagInfo.getBodyContent
+ | The bodycontent information for this tag. If the bodycontent is not defined for thsi tag, the defaul of JSP will be returned.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:241 | String | jakarta.servlet.jsp.tagext.TagInfo.getInfoString
+ | The information string for the tag.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:242 | void | jakarta.servlet.jsp.tagext.TagInfo.setTagLibrary
+
+ (
+ TagLibraryInfo
+ )
+ | Set the TagLibraryInfo property.
+ Note that a TagLibraryInfo element is dependent not just on the TLD information but also on the specific taglib instance used. This means that a fair amount of work needs to be done to construct and initialize TagLib objects. If used carefully, this setter can be used to avoid having to create new TagInfo elements for each taglib directive.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:243 | TagLibraryInfo | jakarta.servlet.jsp.tagext.TagInfo.getTagLibrary
+ | The instance of TabLibraryInfo we belong to.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:244 | String | jakarta.servlet.jsp.tagext.TagInfo.getDisplayName
+ | Get the displayName or null if not defined.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:245 | String | jakarta.servlet.jsp.tagext.TagInfo.getSmallIcon
+ | Get the path to the small icon
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:246 | String | jakarta.servlet.jsp.tagext.TagInfo.getLargeIcon
+ | Get the path to the large icon
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:247 | TagVariableInfo[] | jakarta.servlet.jsp.tagext.TagInfo.getTagVariableInfos
+ | Get TagVariableInfo objects associated with this TagInfo
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:248 | boolean | jakarta.servlet.jsp.tagext.TagInfo.hasDynamicAttributes
+ | Get dynamicAttributes associated with this TagInfo
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:258 | TagFileInfo | jakarta.servlet.jsp.tagext.TagFileInfo.TagFileInfo
+
+ (
+ String
+ , String
+ , TagInfo
+ )
+ | Constructor for TagFileInfo from data in the JSP 2.0 format for TLD.
+ This class is to be instantiated only from the TagLibrary code under request from some JSP code that is parsing a TLD (Tag Library Descriptor). Note that, since TagLibibraryInfo reflects both TLD information and taglib directive information, a TagFileInfo instance is dependent on a taglib directive. This is probably a design error, which may be fixed in the future.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:259 | String | jakarta.servlet.jsp.tagext.TagFileInfo.getName
+ | The unique action name of this tag.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:260 | String | jakarta.servlet.jsp.tagext.TagFileInfo.getPath
+ | Where to find the .tag file implementing this action.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:261 | TagInfo | jakarta.servlet.jsp.tagext.TagFileInfo.getTagInfo
+ | Returns information about this tag, parsed from the directives in the tag file.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:262 | TagExtraInfo | jakarta.servlet.jsp.tagext.TagExtraInfo.TagExtraInfo
+ |
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:263 | VariableInfo[] | jakarta.servlet.jsp.tagext.TagExtraInfo.getVariableInfo
+
+ (
+ TagData
+ )
+ | information on scripting variables defined by the tag associated with this TagExtraInfo instance.
+ Request-time attributes are indicated as such in the TagData parameter.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:264 | boolean | jakarta.servlet.jsp.tagext.TagExtraInfo.isValid
+
+ (
+ TagData
+ )
+ | Translation-time validation of the attributes.
+ Request-time attributes are indicated as such in the TagData parameter. Note that the preferred way to do validation is with the validate() method, since it can return more detailed information.
+
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:265 | ValidationMessage[] | jakarta.servlet.jsp.tagext.TagExtraInfo.validate
+
+ (
+ TagData
+ )
+ | Translation-time validation of the attributes.
+ Request-time attributes are indicated as such in the TagData parameter. Because of the higher quality validation messages possible, this is the preferred way to do validation (although isValid() still works). JSP 2.0 and higher containers call validate() instead of isValid(). The default implementation of this method is to call isValid(). If isValid() returns false, a generic ValidationMessage[] is returned indicating isValid() returned false.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:266 | void | jakarta.servlet.jsp.tagext.TagExtraInfo.setTagInfo
+
+ (
+ TagInfo
+ )
+ | Set the TagInfo for this class.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:267 | TagInfo | jakarta.servlet.jsp.tagext.TagExtraInfo.getTagInfo
+ | Get the TagInfo for this class.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:268 | TagData | jakarta.servlet.jsp.tagext.TagData.TagData
+
+ (
+ Object[][]
+ )
+ | Constructor for TagData.
+ A typical constructor may be static final Object[][] att = {{"connection", "conn0"}, {"id", "query0"}}; static final TagData td = new TagData(att); All values must be Strings except for those holding the distinguished object REQUEST_TIME_VALUE.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:269 | TagData | jakarta.servlet.jsp.tagext.TagData.TagData
+
+ (
+ Hashtable
+ )
+ | Constructor for a TagData.
+ If you already have the attributes in a hashtable, use this constructor.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:270 | String | jakarta.servlet.jsp.tagext.TagData.getId
+ | The value of the tag's id attribute.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:271 | Object | jakarta.servlet.jsp.tagext.TagData.getAttribute
+
+ (
+ String
+ )
+ | The value of the attribute. If a static value is specified for an attribute that accepts a request-time attribute expression then that static value is returned even if the value is provided in the body of an action. The distinguised object REQUEST_TIME_VALUE is only returned if the value is specified as a request-time attribute expression or via the jsp:attribute action with a body that contains dynamic content (scripts, scripting expressions, EL expressions, standard actions, or custom actions). | true |
+
+ | true |
+
+
+JSP:JAVADOC:272 | void | jakarta.servlet.jsp.tagext.TagData.setAttribute
+
+ (
+ String
+ , Object
+ )
+ | Set the value of an attribute.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:273 | String | jakarta.servlet.jsp.tagext.TagData.getAttributeString
+
+ (
+ String
+ )
+ | Get the value for a given attribute.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:274 | String | jakarta.servlet.jsp.tagext.TagData.getAttributeString
+
+ (
+ String
+ )
+ throws
+ ClassCastException
+ | if attribute value is not a String | true |
+
+ | true |
+
+
+JSP:JAVADOC:275 | Enumeration | jakarta.servlet.jsp.tagext.TagData.getAttributes
+ | Enumerates the attributes.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:276 | TagAttributeInfo | jakarta.servlet.jsp.tagext.TagAttributeInfo.TagAttributeInfo
+
+ (
+ String
+ , boolean
+ , String
+ , boolean
+ )
+ | Constructor for TagAttributeInfo.
+ This class is to be instantiated only from the TagLibrary code under request from some JSP code that is parsing a TLD (Tag Library Descriptor).
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:277 | TagAttributeInfo | jakarta.servlet.jsp.tagext.TagAttributeInfo.TagAttributeInfo
+
+ (
+ String
+ , boolean
+ , String
+ , boolean
+ , boolean
+ )
+ | JSP 2.0 Constructor for TagAttributeInfo.
+ This class is to be instantiated only from the TagLibrary code under request from some JSP code that is parsing a TLD (Tag Library Descriptor).
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:278 | String | jakarta.servlet.jsp.tagext.TagAttributeInfo.getName
+ | The name of this attribute.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:279 | String | jakarta.servlet.jsp.tagext.TagAttributeInfo.getTypeName
+ | The type (as a String) of this attribute.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:280 | boolean | jakarta.servlet.jsp.tagext.TagAttributeInfo.canBeRequestTime
+ | Whether this attribute can hold a request-time value.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:281 | boolean | jakarta.servlet.jsp.tagext.TagAttributeInfo.isRequired
+ | Whether this attribute is required.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:282 | TagAttributeInfo | jakarta.servlet.jsp.tagext.TagAttributeInfo.getIdAttribute
+
+ (
+ TagAttributeInfo[]
+ )
+ | Convenience static method that goes through an array of TagAttributeInfo objects and looks for "id".
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:283 | boolean | jakarta.servlet.jsp.tagext.TagAttributeInfo.isFragment
+ | Whether this attribute is of type JspFragment
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:284 | String | jakarta.servlet.jsp.tagext.TagAttributeInfo.toString
+ | Returns a String representation of this TagAttributeInfo, suitable for debugging purposes.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:285 | TagAdapter | jakarta.servlet.jsp.tagext.TagAdapter.TagAdapter
+
+ (
+ SimpleTag
+ )
+ | Creates a new TagAdapter that wraps the given SimeplTag and returns the parent tag when getParent() is called.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:286 | void | jakarta.servlet.jsp.tagext.TagAdapter.setPageContext
+
+ (
+ PageContext
+ )
+ | Must not be called.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:287 | void | jakarta.servlet.jsp.tagext.TagAdapter.setPageContext
+
+ (
+ PageContext
+ )
+ throws
+ UnsupportedOperationException
+ | Must not be called | true |
+
+ | true |
+
+
+JSP:JAVADOC:288 | void | jakarta.servlet.jsp.tagext.TagAdapter.setParent
+
+ (
+ Tag
+ )
+ | Must not be called.
+ The parent of this tag is always getAdaptee().getParent().
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:289 | void | jakarta.servlet.jsp.tagext.TagAdapter.setParent
+
+ (
+ Tag
+ )
+ throws
+ UnsupportedOperationException
+ | Must not be called. | true |
+
+ | true |
+
+
+JSP:JAVADOC:290 | Tag | jakarta.servlet.jsp.tagext.TagAdapter.getParent
+ | Returns the value passed to setParent().
+ This will either be the enclosing Tag (if parent implements Tag), or an adapter to the enclosing Tag (if parent does not implement Tag).
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:291 | JspTag | jakarta.servlet.jsp.tagext.TagAdapter.getAdaptee
+ | Gets the tag that is being adapted to the Tag interface.
+ This should be an instance of SimpleTag in JSP 2.0, but room is left for other kinds of tags in future spec versions.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:292 | int | jakarta.servlet.jsp.tagext.TagAdapter.doStartTag
+ | Must not be called.
+
+ | true |
+
+ | false |
+
+
+JSP:JAVADOC:293 | int | jakarta.servlet.jsp.tagext.TagAdapter.doStartTag
+ throws
+ JspException
+ | never thrown | true |
+
+ | false |
+
+
+JSP:JAVADOC:294 | int | jakarta.servlet.jsp.tagext.TagAdapter.doStartTag
+ throws
+ UnsupportedOperationException
+ | Must not be called | true |
+
+ | false |
+
+
+JSP:JAVADOC:295 | int | jakarta.servlet.jsp.tagext.TagAdapter.doEndTag
+ | Must not be called.
+
+ | true |
+
+ | false |
+
+
+JSP:JAVADOC:296 | int | jakarta.servlet.jsp.tagext.TagAdapter.doEndTag
+ throws
+ JspException
+ | never thrown | true |
+
+ | false |
+
+
+JSP:JAVADOC:297 | int | jakarta.servlet.jsp.tagext.TagAdapter.doEndTag
+ throws
+ UnsupportedOperationException
+ | Must not be called | true |
+
+ | false |
+
+
+JSP:JAVADOC:298 | void | jakarta.servlet.jsp.tagext.TagAdapter.release
+ | Must not be called.
+
+ | true |
+
+ | false |
+
+
+JSP:JAVADOC:299 | void | jakarta.servlet.jsp.tagext.TagAdapter.release
+ throws
+ UnsupportedOperationException
+ | Must not be called | true |
+
+ | false |
+
+
+JSP:JAVADOC:300 | SimpleTagSupport | jakarta.servlet.jsp.tagext.SimpleTagSupport.SimpleTagSupport
+ |
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:301 | void | jakarta.servlet.jsp.tagext.SimpleTagSupport.doTag
+ | Default processing of the tag does nothing.
+
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:302 | void | jakarta.servlet.jsp.tagext.SimpleTagSupport.doTag
+ throws
+ JspException
+ | Subclasses can throw JspException to indicate an error occurred while processing this tag. | true |
+
+ | false |
+
+
+JSP:JAVADOC:303 | void | jakarta.servlet.jsp.tagext.SimpleTagSupport.doTag
+ throws
+ IOException
+ | Subclasses can throw IOException if there was an error writing to the output stream | true |
+
+ | false |
+
+
+JSP:JAVADOC:304 | void | jakarta.servlet.jsp.tagext.SimpleTagSupport.doTag
+ throws
+ SkipPageException
+ | If the page that (either directly or indirectly) invoked this tag is to cease evaluation. A Simple Tag Handler generated from a tag file must throw this exception if an invoked Classic Tag Handler returned SKIP_PAGE or if an invoked Simple Tag Handler threw SkipPageException or if an invoked Jsp Fragment threw a SkipPageException. | true |
+
+ | true |
+
+
+JSP:JAVADOC:305 | void | jakarta.servlet.jsp.tagext.SimpleTagSupport.setParent
+
+ (
+ JspTag
+ )
+ | Sets the parent of this tag, for collaboration purposes.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:306 | JspTag | jakarta.servlet.jsp.tagext.SimpleTagSupport.getParent
+ | Returns the parent of this tag, for collaboration purposes.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:307 | void | jakarta.servlet.jsp.tagext.SimpleTagSupport.setJspContext
+
+ (
+ JspContext
+ )
+ | Stores the provided JSP context in the protected jspContext field.
+
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:308 | JspContext | jakarta.servlet.jsp.tagext.SimpleTagSupport.getJspContext
+ | Returns the page context passed in by the container via setJspContext.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:309 | void | jakarta.servlet.jsp.tagext.SimpleTagSupport.setJspBody
+
+ (
+ JspFragment
+ )
+ | Stores the provided JspFragment.
+
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:310 | JspFragment | jakarta.servlet.jsp.tagext.SimpleTagSupport.getJspBody
+ | Returns the body passed in by the container via setJspBody
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:311 | JspTag | jakarta.servlet.jsp.tagext.SimpleTagSupport.findAncestorWithClass
+
+ (
+ JspTag
+ , Class
+ )
+ | Find the instance of a given class type that is closest to a given instance.
+ This method uses the getParent method from the Tag and/or SimpleTag interfaces. This method is used for coordination among cooperating tags. For every instance of TagAdapter encoutnered will traversing the ancestors the tag handler returned by TagAdapter.getAdatpee() - instead of the TagAdapter itself - is compared to klass. If the tag handler matches it - and not its TagAdapter - is returned. The current version of the specification only provides one formal way of indicating the observable type of a tag handler: its tag handler implementation class, described in the tag-class subelement of the tag element. This is extended in an informal manner by allowing the tag library author to indicate in the description subelement an observable type. The type should be a subtype of the tag handler implementation class or void. This addititional constraint can be exploited by a specialized container that knows about that specific tag library, as in the case of the JSP standard tag library. When a tag library author provides information on the observable type of a tag handler, client programmatic code should adhere to that constraint. Specifically, the Class passed to findAncestorWithClass should be a subtype of the observable type.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:312 | PageData | jakarta.servlet.jsp.tagext.PageData.PageData
+ |
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:313 | InputStream | jakarta.servlet.jsp.tagext.PageData.getInputStream
+ | Returns an input stream on the XML view of a JSP page. The stream is encoded in UTF-8.
+ Recall tht the XML view of a JSP page has the include directives expanded.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:314 | FunctionInfo | jakarta.servlet.jsp.tagext.FunctionInfo.FunctionInfo
+
+ (
+ String
+ , String
+ , String
+ )
+ | Constructor for FunctionInfo.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:315 | String | jakarta.servlet.jsp.tagext.FunctionInfo.getName
+ | The name of the function.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:316 | String | jakarta.servlet.jsp.tagext.FunctionInfo.getFunctionClass
+ | The class of the function.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:317 | String | jakarta.servlet.jsp.tagext.FunctionInfo.getFunctionSignature
+ | The signature of the function.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:318 | BodyTagSupport | jakarta.servlet.jsp.tagext.BodyTagSupport.BodyTagSupport
+ | Default constructor, all subclasses are required to only define a public constructor with the same signature, and to call the superclass constructor.
+ This constructor is called by the code generated by the JSP translator.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:319 | int | jakarta.servlet.jsp.tagext.BodyTagSupport.doStartTag
+ | Default processing of the start tag returning EVAL_BODY_BUFFERED
+
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:320 | int | jakarta.servlet.jsp.tagext.BodyTagSupport.doStartTag
+ throws
+ JspException
+ | if an error occurred while processing this tag | true |
+
+ | false |
+
+
+JSP:JAVADOC:321 | int | jakarta.servlet.jsp.tagext.BodyTagSupport.doEndTag
+ | Default processing of the end tag returning EVAL_PAGE.
+
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:322 | int | jakarta.servlet.jsp.tagext.BodyTagSupport.doEndTag
+ throws
+ JspException
+ | if an error occurred while processing this tag | true |
+
+ | false |
+
+
+JSP:JAVADOC:323 | void | jakarta.servlet.jsp.tagext.BodyTagSupport.setBodyContent
+
+ (
+ BodyContent
+ )
+ | Prepare for evaluation of the body: stash the bodyContent away.
+
+
+
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:324 | void | jakarta.servlet.jsp.tagext.BodyTagSupport.doInitBody
+ | Prepare for evaluation of the body just before the first body evaluation: no action.
+
+
+
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:325 | void | jakarta.servlet.jsp.tagext.BodyTagSupport.doInitBody
+ throws
+ JspException
+ | if an error occurred while processing this tag | true |
+
+ | false |
+
+
+JSP:JAVADOC:326 | int | jakarta.servlet.jsp.tagext.BodyTagSupport.doAfterBody
+ | After the body evaluation: do not reevaluate and continue with the page.
+ By default nothing is done with the bodyContent data (if any).
+
+
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:327 | int | jakarta.servlet.jsp.tagext.BodyTagSupport.doAfterBody
+ throws
+ JspException
+ | if an error occurred while processing this tag | true |
+
+ | false |
+
+
+JSP:JAVADOC:328 | void | jakarta.servlet.jsp.tagext.BodyTagSupport.release
+ | Release state.
+
+
+ | true |
+
+ | false |
+
+
+JSP:JAVADOC:329 | BodyContent | jakarta.servlet.jsp.tagext.BodyTagSupport.getBodyContent
+ | Get current bodyContent.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:330 | JspWriter | jakarta.servlet.jsp.tagext.BodyTagSupport.getPreviousOut
+ | Get surrounding out JspWriter.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:331 | void | jakarta.servlet.jsp.tagext.BodyContent.flush
+ | Redefined flush() so it is not legal.
+ It is not valid to flush a BodyContent because there is no backing stream behind it.
+
+ | true |
+
+ | false |
+
+
+JSP:JAVADOC:332 | void | jakarta.servlet.jsp.tagext.BodyContent.flush
+ throws
+ IOException
+ | always thrown | true |
+
+ | true |
+
+
+JSP:JAVADOC:333 | void | jakarta.servlet.jsp.tagext.BodyContent.clearBody
+ | Clear the body without throwing any exceptions.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:334 | Reader | jakarta.servlet.jsp.tagext.BodyContent.getReader
+ | Return the value of this BodyContent as a Reader.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:335 | String | jakarta.servlet.jsp.tagext.BodyContent.getString
+ | Return the value of the BodyContent as a String.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:336 | void | jakarta.servlet.jsp.tagext.BodyContent.writeOut
+
+ (
+ Writer
+ )
+ | Write the contents of this BodyContent into a Writer.
+ Subclasses may optimize common invocation patterns.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:337 | void | jakarta.servlet.jsp.tagext.BodyContent.writeOut
+
+ (
+ Writer
+ )
+ throws
+ IOException
+ | if an I/O error occurred while writing the contents of this BodyContent to the given Writer | true |
+
+ | false |
+
+
+JSP:JAVADOC:338 | JspWriter | jakarta.servlet.jsp.tagext.BodyContent.getEnclosingWriter
+ | Get the enclosing JspWriter.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:339 | void | jakarta.servlet.jsp.tagext.TryCatchFinally.doCatch
+
+ (
+ Throwable
+ )
+ | Invoked if a Throwable occurs while evaluating the BODY inside a tag or in any of the following methods: Tag.doStartTag(), Tag.doEndTag(), IterationTag.doAfterBody() and BodyTag.doInitBody().
+ This method is not invoked if the Throwable occurs during one of the setter methods. This method may throw an exception (the same or a new one) that will be propagated further up the nest chain. If an exception is thrown, doFinally() will be invoked. This method is intended to be used to respond to an exceptional condition.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:340 | void | jakarta.servlet.jsp.tagext.TryCatchFinally.doCatch
+
+ (
+ Throwable
+ )
+ throws
+ Throwable
+ | Throwable if the exception is to be rethrown further up the next chain | true |
+
+ | false |
+
+
+JSP:JAVADOC:341 | void | jakarta.servlet.jsp.tagext.TryCatchFinally.doFinally
+ | Invoked in all cases after doEndTag() for any class implementing Tag, IterationTag or BodyTag.
+ This method is invoked even if an exception has occurred in the BODY of the tag, or in any of the following methods: Tag.doStartTag(), Tag.doEndTag(), IterationTag.doAfterBody() and BodyTag.doInitBody(). This method is not invoked if the Throwable occurs during one of the setter methods. This method should not throw an Exception. This method is intended to maintain per-invocation data integrity and resource management actions.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:342 | void | jakarta.servlet.jsp.tagext.Tag.setPageContext
+
+ (
+ PageContext
+ )
+ | Set the current page context.
+ This method is invoked by the JSP page implementation object prior to doStartTag(). This value is *not* reset by doEndTag() and must be explicitly reset by a page implementation if it changes between calls to doStartTag().
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:343 | void | jakarta.servlet.jsp.tagext.Tag.setParent
+
+ (
+ Tag
+ )
+ | Set the parent (closest enclosing tag handler) of this tag handler.
+ Invoked by the JSP page implementation object prior to doStartTag(). This value is *not* reset by doEndTag() and must be explicitly reset by a page implementation.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:344 | Tag | jakarta.servlet.jsp.tagext.Tag.getParent
+ | Get the parent (closest enclosing tag handler) for this tag handler.
+ The getParent() method can be used to navigate the nested tag handler structure at runtime for cooperation among custom actions; for example, the findAncestorWithClass() method in TagSupport provides a convenient way of doing this. The current version of the specification only provides one formal way of indicating the observable type of a tag handler: its tag handler implementation class, described in the tag-class subelement of the tag element. This is extended in an informal manner by allowing the tag library author to indicate in the description subelement an observable type. The type should be a subtype of the tag handler implementation class or void. This addititional constraint can be exploited by a specialized container that knows about that specific tag library, as in the case of the JSP standard tag library.
+
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:345 | int | jakarta.servlet.jsp.tagext.Tag.doStartTag
+ | Process the start tag for this instance.
+ This method is invoked by the JSP page implementation object. The doStartTag method assumes that the properties pageContext and parent have been set. It also assumes that any properties exposed as attributes have been set too. When this method is invoked, the body has not yet been evaluated. When a Tag returns EVAL_BODY_INCLUDE the result of evaluating the body (if any) is included into the current "out" JspWriter as it happens and then doEndTag() is invoked.
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:346 | int | jakarta.servlet.jsp.tagext.Tag.doStartTag
+ | Process the start tag for this instance.
+ This method is invoked by the JSP page implementation object. The doStartTag method assumes that the properties pageContext and parent have been set. It also assumes that any properties exposed as attributes have been set too. When this method is invoked, the body has not yet been evaluated. Returning BodyTag.EVAL_BODY_BUFFERED is only valid if the tag handler implements BodyTag.
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:347 | int | jakarta.servlet.jsp.tagext.Tag.doStartTag
+ | Process the start tag for this instance.
+ This method is invoked by the JSP page implementation object. The doStartTag method assumes that the properties pageContext and parent have been set. It also assumes that any properties exposed as attributes have been set too. When this method is invoked, the body has not yet been evaluated. When SKIP_PAGE is returned, the processing of the page will cease and no remainder tag methods, such as doEndTag() will be called within this JSP page implementation object.
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:348 | int | jakarta.servlet.jsp.tagext.Tag.doStartTag
+ | The JSP container will recynchronize the values of any AT_EBING and NESTED variables (defined by the associated TagExtraInfo or TLD) after the invocation of doStartTag() except for a tag handler implementing BodyTag whose doStartTag() method returns BodyTag.EVAL_BODY_BUFFERED. | true |
+
+ | true |
+
+
+JSP:JAVADOC:349 | int | jakarta.servlet.jsp.tagext.Tag.doStartTag
+ throws
+ JspException
+ | if an error occurred while processing this tag | true |
+
+ | false |
+
+
+JSP:JAVADOC:350 | int | jakarta.servlet.jsp.tagext.Tag.doEndTag
+ | Process the end tag for this instance.
+ This method is invoked by the JSP page implementation object on all Tag handlers. This method will be called after returning from doStartTag. The body of the action may or may not have been evaluated, depending on the return value of doStartTag. If this method returns EVAL_PAGE, the rest of the page continues to be evaluated.
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:351 | int | jakarta.servlet.jsp.tagext.Tag.doEndTag
+ | Process the end tag for this instance.
+ This method is invoked by the JSP page implementation object on all Tag handlers. This method will be called after returning from doStartTag. The body of the action may or may not have been evaluated, depending on the return value of doStartTag. If this method returns SKIP_PAGE, the rest of the page is not evaluated, the request is completed, and the doEndTag() methods of enclosing tags are not invoked. If this request was forwarded or included from another page (or Servlet), only the current page evaluation is stopped.
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:352 | int | jakarta.servlet.jsp.tagext.Tag.doEndTag
+ | Process the end tag for this instance.
+ This method is invoked by the JSP page implementation object on all Tag handlers. This method will be called after returning from doStartTag. The body of the action may or may not have been evaluated, depending on the return value of doStartTag. If this method returns EVAL_PAGE, the rest of the page continues to be evaluated. If this method returns SKIP_PAGE, the rest of the page is not evaluated, the request is completed, and the doEndTag() methods of enclosing tags are not invoked. If this request was forwarded or included from another page (or Servlet), only the current page evaluation is stopped. The JSP container will resynchronize any variable values that are indicated as so in TagExtraInfo after the invocation of doEndTag().
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:353 | int | jakarta.servlet.jsp.tagext.Tag.doEndTag
+ | The JSP container will resynchronize the values of any AT_BEGIN and AT_END variables (defined by the assocaited TagExtraInfo or TLD) after the invocation of doEndTag(). | true |
+
+ | true |
+
+
+JSP:JAVADOC:354 | int | jakarta.servlet.jsp.tagext.Tag.doEndTag
+ throws
+ JspException
+ | if an error occurred while processing this tag | true |
+
+ | true |
+
+
+JSP:JAVADOC:355 | void | jakarta.servlet.jsp.tagext.Tag.release
+ | Called on a Tag handler to release state.
+ The page compiler guarantees that JSP page implementation objects will invoke this method on all tag handlers, but there may be multiple invocations on doStartTag and doEndTag in between.
+
+ | true |
+
+ | false |
+
+
+JSP:JAVADOC:356 | void | jakarta.servlet.jsp.tagext.SimpleTag.doTag
+ | Called by the container to invoke this tag.
+ The implementation of this method is provided by the tag library developer, and handles all tag processing, body iteration, etc.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:400 | void | jakarta.servlet.jsp.tagext.SimpleTag.doTag
+ | The JSP container will recynchronize any AT_BEGIN and AT_END variables (defined by the associated tag file TagExtraInfo or TLD) after the invocation of doTag(). | true |
+
+ | true |
+
+
+JSP:JAVADOC:357 | void | jakarta.servlet.jsp.tagext.SimpleTag.doTag
+ throws
+ JspException
+ | If an error occurred while processing this tag. | true |
+
+ | false |
+
+
+JSP:JAVADOC:358 | void | jakarta.servlet.jsp.tagext.SimpleTag.doTag
+ throws
+ IOException
+ | If there was an error writing to the output stream. | true |
+
+ | false |
+
+
+JSP:JAVADOC:359 | void | jakarta.servlet.jsp.tagext.SimpleTag.doTag
+ throws
+ SkipPageException
+ | If the page that (either directly or indirectly) invoked this tag is to cease evaluation. A Simple Tag Handler generated from a tag file must throw this exception if an invoked Classic Tag Handler returned SKIP_PAGE or if an invoked Simple Tag Handler threw SkipPageException or if an invoked Jsp Fragment threw a SkipPageException. | true |
+
+ | true |
+
+
+JSP:JAVADOC:360 | void | jakarta.servlet.jsp.tagext.SimpleTag.setParent
+
+ (
+ JspTag
+ )
+ | Sets the parent of this tag, for collaboration purposes.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:361 | JspTag | jakarta.servlet.jsp.tagext.SimpleTag.getParent
+ | Returns the parent of this tag, for collaboration purposes.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:362 | void | jakarta.servlet.jsp.tagext.SimpleTag.setJspContext
+
+ (
+ JspContext
+ )
+ | Stores the provided JSP context in the protected jspContext field.
+
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:363 | void | jakarta.servlet.jsp.tagext.SimpleTag.setJspBody
+
+ (
+ JspFragment
+ )
+ | Provides the body of this tag as a JspFragment object, able to be invoked zero or more times by the tag handler.
+ This method is invoked by the JSP page implementation object prior to doTag().
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:403 | JspFragment | jakarta.servlet.jsp.tagext.JspFragment.JspFragment
+ |
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:404 | JspContext | jakarta.servlet.jsp.tagext.JspFragment.getJspContext
+ | Returns the JspContext that is bound to this JspFragment. | true |
+
+ | true |
+
+
+JSP:JAVADOC:382 | void | jakarta.servlet.jsp.tagext.JspFragment.invoke
+
+ (
+ Writer
+ )
+ | Executes the fragment and directs all output to the given Writer, or the JspWriter returned by the getOut() method of the JspContext associated with the fragment if out is null. | true |
+
+ | true |
+
+
+JSP:JAVADOC:401 | void | jakarta.servlet.jsp.tagext.JspFragment.invoke
+
+ (
+ Writer
+ )
+ throws
+ JspException
+ | Thrown if an error occured while invoking this fragment. | true |
+
+ | true |
+
+
+JSP:JAVADOC:402 | void | jakarta.servlet.jsp.tagext.JspFragment.invoke
+
+ (
+ Writer
+ )
+ throws
+ IOException
+ | If there was an error writing to the stream. | true |
+
+ | true |
+
+
+JSP:JAVADOC:367 | void | jakarta.servlet.jsp.tagext.JspFragment.invoke
+
+ (
+ Writer
+ )
+ throws
+ SkipPageException
+ | Thrown if the page that (either directly or indirectly) invoked the tag handler that invoked this fragment is to cease evaluation. The container must throw this exception if a Classic Tag Handler returned Tag.SKIP_PAGE or if a Simple Tag Handler threw SkipPageException. | true |
+
+ | true |
+
+
+JSP:JAVADOC:368 | int | jakarta.servlet.jsp.tagext.IterationTag.doAfterBody
+ | Process body (re)evaluation.
+ This method is invoked by the JSP Page implementation object after every evaluation of the body into the BodyEvaluation object. The method is not invoked if there is no body evaluation.
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:369 | int | jakarta.servlet.jsp.tagext.IterationTag.doAfterBody
+ | Process body (re)evaluation.
+ This method is invoked by the JSP Page implementation object after every evaluation of the body into the BodyEvaluation object. If doAfterBody returns EVAL_BODY_AGAIN, a new evaluation of the body will happen (followed by another invocation of doAfterBody).
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:386 | int | jakarta.servlet.jsp.tagext.IterationTag.doAfterBody
+ | Process body (re)evaluation.
+ This method is invoked by the JSP Page implementation object after every evaluation of the body into the BodyEvaluation object. If doAfterBody returns SKIP_PAGE no more body evaluations will occur and the doEndTag method will be invoked.
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:370 | int | jakarta.servlet.jsp.tagext.IterationTag.doAfterBody
+ throws
+ JspException
+ |
+
+ | true |
+
+ | false |
+
+
+JSP:JAVADOC:371 | int | jakarta.servlet.jsp.tagext.IterationTag.doAfterBody
+ |
+ The JSP container will resynchronize the values of any AT_BEGIN and NESTED variables (defined by the associated TagExtraInfo or TLD) after the invocation of doAfterBody().
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:372 | void | jakarta.servlet.jsp.tagext.DynamicAttributes.setDynamicAttribute
+
+ (
+ String
+ , String
+ , Object
+ )
+ | Called when a tag declared to accept dynamic attributes is passed an attribute that is not declared in the Tag Library Descriptor.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:373 | void | jakarta.servlet.jsp.tagext.DynamicAttributes.setDynamicAttribute
+
+ (
+ String
+ , String
+ , Object
+ )
+ throws
+ JspException
+ | if the tag handler wishes to signal that it does not accept the given attribute. The container must not call doStartTag() or doTag() for this tag. | true |
+
+ | false |
+
+
+JSP:JAVADOC:374 | void | jakarta.servlet.jsp.tagext.BodyTag.setBodyContent
+
+ (
+ BodyContent
+ )
+ | Set the bodyContent property.
+ This method is invoked by the JSP page implementation object at most once per action invocation. This method will be invoked before doInitBody. This method will not be invoked for empty tags or for non-empty tags whose doStartTag() method returns SKIP_BODY or EVAL_BODY_INCLUDE. When setBodyContent is invoked, the value of the implicit object out has already been changed in the pageContext object. The BodyContent object passed will have not data on it but may have been reused (and cleared) from some previous invocation. The BodyContent object is available and with the appropriate content until after the invocation of the doEndTag method, at which case it may be reused.
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:375 | void | jakarta.servlet.jsp.tagext.BodyTag.doInitBody
+ | Prepare for evaluation of the body.
+ This method is invoked by the JSP page implementation object after setBodyContent and before the first time the body is to be evaluated.
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:376 | void | jakarta.servlet.jsp.tagext.BodyTag.doInitBody
+ | Prepare for evaluation of the body.
+ This method will not be invoked for empty tags or for non-empty tags whose doStartTag() method returns SKIP_BODY or EVAL_BODY_INCLUDE.
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:377 | void | jakarta.servlet.jsp.tagext.BodyTag.doInitBody
+ | The JSP container will resynchronize the values if AT_BEGIN and NESTED variabled (defined by the associated TagExtraInfo or TLD) after the invfocation of doInitBody(). | true |
+
+ | true |
+
+
+JSP:JAVADOC:378 | void | jakarta.servlet.jsp.tagext.BodyTag.doInitBody
+ throws
+ JspException
+ | If an error occurred while processing this tag | true |
+
+ | false |
+
+
+JSP:JAVADOC:406 | void | jakarta.servlet.jsp.HttpJspPage._jspService
+
+ (
+ HttpServletRequest
+ , HttpServletResponse
+ )
+ | The _jspService()method corresponds to the body of the JSP page.
+ This method is defined automatically by the JSP container and should never be defined by the JSP page author. If a superclass is specified using the extends attribute, that superclass may choose to perform some actions in its service() method before or after calling the _jspService() method. See using the extends attribute in the JSP_Engine chapter of the JSP specification.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:407 | void | jakarta.servlet.jsp.HttpJspPage._jspService
+
+ (
+ HttpServletRequest
+ , HttpServletResponse
+ )
+ throws
+ ServletException
+ | Thrown if an error occurred during the processing of the JSP and that the container should take appropriate action to clean up the request. | true |
+
+ | true |
+
+
+JSP:JAVADOC:408 | void | jakarta.servlet.jsp.HttpJspPage._jspService
+
+ (
+ HttpServletRequest
+ , HttpServletResponse
+ )
+ throws
+ IOException
+ | Thrown if an error occurred while writing the response for this page. | true |
+
+ | true |
+
+
+JSP:JAVADOC:409 | void | jakarta.servlet.jsp.JspApplicationContext.addELContextListener
+
+ (
+ ELContextListener
+ )
+ | Registers a ELContextListeners so that context objects can be added whenever a new ELContext is created.
+
+ At a minimum, the ELContext objects created will contain a reference to the JspContext for this request, which is added by the JSP container. This is sufficient for all the default ELResolvers listed in #addELResolver. Note that JspContext.class is used as the key to ELContext.putContext() for the JspContext object reference. This method is generally used by frameworks and applications that register their own ELResolver that needs context other than JspContext. The listener will typically add the necessary context to the ELContext provided in the event object. Registering a listener that adds context allows the ELResolvers in the stack to access the context they need when they do a resolution.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:410 | void | jakarta.servlet.jsp.JspApplicationContext.addELResolver
+
+ (
+ ELResolver
+ )
+ | Adds an ELResolver to affect the way EL variables and properties are resolved for EL expressions appearing in JSP pages and tag files.
+
+
+
+
+
+
+ For example, in the EL expression ${employee.lastName}, an ELResolver determines what object "employee" references and how to find its "lastName" property. When evaluating an expression, the JSP container will consult a set of standard resolvers as well as any resolvers registered via this method. The set of resolvers are consulted in the following order: jakarta.servlet.jsp.el.ImplicitObjectELResolver ELResolvers registered via this method, in the order in which they are registered. jakarta.el.MapELResolverjakarta.el.ListELResolverjakarta.el.ArrayELResolverjakarta.el.BeanELResolverjakarta.servlet.jsp.el.ScopedAttributeELResolver It is illegal to register an ELResolver after the application has received any request from the client. If an attempt is made to register an ELResolver after that time, an IllegalStateException is thrown. This restriction is in place to allow the JSP container to optimize for the common case where no additional ELResolvers are in the chain, aside from the standard ones. It is permissible to add ELResolvers before or after initialization to a CompositeELResolver that is already in the chain. It is not possible to remove an ELResolver registered with this method, once it has been registered.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:411 | ExpressionFactory | jakarta.servlet.jsp.JspApplicationContext.getExpressionFactory
+ | Returns a factory used to create ValueExpressions and MethodExpressions so that EL expressions can be parsed and evaluated.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:412 | VariableResolver | jakarta.servlet.jsp.JspContext.getVariableResolver
+ | Returns an instance of a VariableResolver that provides access to the implicit objects specified in the JSP specification using this JspContext as the context object.
+
+ | true | true | true |
+
+
+JSP:JAVADOC:413 | JspFactory | jakarta.servlet.jsp.JspFactory.getDefaultFactory
+ | Returns the default factory for this implementation.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:414 | JspEngineInfo | jakarta.servlet.jsp.JspFactory.getEngineInfo
+ | called to get implementation-specific information on the current JSP engine.
+
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:415 | JspApplicationContext | jakarta.servlet.jsp.JspFactory.getJspApplicationContext
+
+ (
+ ServletContext
+ )
+ | Obtains the JspApplicationContext instance associated with the web application for the given ServletContext.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:416 | PageContext | jakarta.servlet.jsp.JspFactory.getPageContext
+
+ (
+ Servlet
+ , ServletRequest
+ , ServletResponse
+ , String
+ , boolean
+ , int
+ , boolean
+ )
+ | obtains an instance of an implementation dependent jakarta.servlet.jsp.PageContext abstract class for the calling Servlet and currently pending request and response.
+ This method is typically called early in the processing of the _jspService() method of a JSP implementation class in order to obtain a PageContext object for the request being processed. Invoking this method shall result in the PageContext.initialize() method being invoked. The PageContext returned is properly initialized. All PageContext objects obtained via this method shall be released by invoking releasePageContext().
+
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:417 | JspFactory | jakarta.servlet.jsp.JspFactory.JspFactory
+ | Sole constructor.
+ (For invocation by subclass constructors, typically implicit.)
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:418 | void | jakarta.servlet.jsp.JspFactory.releasePageContext
+
+ (
+ PageContext
+ )
+ | called to release a previously allocated PageContext object.
+ Results in PageContext.release() being invoked. This method should be invoked prior to returning from the _jspService() method of a JSP implementation class.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:419 | void | jakarta.servlet.jsp.JspFactory.setDefaultFactory
+
+ (
+ JspFactory
+ )
+ | set the default factory for this implementation.
+ It is illegal for any principal other than the JSP Engine runtime to call this method.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:420 | Class | jakarta.servlet.jsp.el.ImplicitObjectELResolver.getCommonPropertyType
+
+ (
+ ELContext
+ , Object
+ )
+ | If the base object is null, returns String.class.
+ Otherwise, returns null.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:421 | Iterator | jakarta.servlet.jsp.el.ImplicitObjectELResolver.getFeatureDescriptors
+
+ (
+ ELContext
+ , Object
+ )
+ | If the base object is null, and the property matches the name of a JSP implicit object, returns an Iterator containing FeatureDescriptor objects with information about each JSP implicit object resolved by this resolver.
+
+
+
+ Otherwise, returns null. The Iterator returned must contain one instance of java.beans.FeatureDescriptor for each of the EL implicit objects defined by the JSP spec. Each info object contains information about a single implicit object, and is initialized as follows: displayName - The name of the implicit object. name - Same as displayName property. shortDescription - A suitable description for the implicit object. Will vary by implementation. expert - false hidden - false preferred - true In addition, the following named attributes must be set in the returned FeatureDescriptors: ELResolver#TYPE - The runtime type of the implicit object. ELResolver#RESOLVABLE_AT_DESIGN_TIME - true.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:422 | Class | jakarta.servlet.jsp.el.ImplicitObjectELResolver.getType
+
+ (
+ ELContext
+ , Object
+ , Object
+ )
+ | If the base object is null, and the property matches the name of a JSP implicit object, returns null to indicate that no types are ever accepted to setValue().
+ The propertyResolved property of the ELContext object must be set to true by this resolver before returning if an implicit object is matched. If this property is not true after this method is called, the caller should ignore the return value.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:423 | Object | jakarta.servlet.jsp.el.ImplicitObjectELResolver.getValue
+
+ (
+ ELContext
+ , Object
+ , Object
+ )
+ | If the base object is null, and the property matches the name of a JSP implicit object, returns the implicit object.
+ The propertyResolved property of the ELContext object must be set to true by this resolver before returning if an implicit object is matched. If this property is not true after this method is called, the caller should ignore the return value.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:424 | ImplicitObjectELResolver | jakarta.servlet.jsp.el.ImplicitObjectELResolver.ImplicitObjectELResolver
+ |
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:425 | boolean | jakarta.servlet.jsp.el.ImplicitObjectELResolver.isReadOnly
+
+ (
+ ELContext
+ , Object
+ , Object
+ )
+ | If the base object is null, and the property matches the name of a JSP implicit object, returns true to indicate that implicit objects cannot be overwritten.
+ The propertyResolved property of the ELContext object must be set to true by this resolver before returning if an implicit object is matched. If this property is not true after this method is called, the caller should ignore the return value.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:426 | void | jakarta.servlet.jsp.el.ImplicitObjectELResolver.setValue
+
+ (
+ ELContext
+ , Object
+ , Object
+ , Object
+ )
+ | If the base object is null, and the property matches the name of a JSP implicit object, throws PropertyNotWritableException to indicate that implicit objects cannot be overwritten.
+ The propertyResolved property of the ELContext object must be set to true by this resolver before returning if an implicit object is matched. If this property is not true after this method is called, the caller should ignore the return value.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:427 | Class | jakarta.servlet.jsp.el.ScopedAttributeELResolver.getCommonPropertyType
+
+ (
+ ELContext
+ , Object
+ )
+ | If the base object is null, returns String.class.
+ Otherwise, returns null.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:428 | Iterator | jakarta.servlet.jsp.el.ScopedAttributeELResolver.getFeatureDescriptors
+
+ (
+ ELContext
+ , Object
+ )
+ | If the base object is null, returns an Iterator containing FeatureDescriptor objects with information about each scoped attribute resolved by this resolver.
+
+
+
+ Otherwise, returns null. The Iterator returned must contain one instance of java.beans.FeatureDescriptor for each scoped attribute found in any scope. Each info object contains information about a single scoped attribute, and is initialized as follows: displayName - The name of the scoped attribute. name - Same as displayName property. shortDescription - A suitable description for the scoped attribute. Should include the attribute's current scope (page, request, session, application). Will vary by implementation. expert - false hidden - false preferred - true In addition, the following named attributes must be set in the returned FeatureDescriptors: ELResolver#TYPE - The current runtime type of the scoped attribute. ELResolver#RESOLVABLE_AT_DESIGN_TIME - true.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:429 | Class | jakarta.servlet.jsp.el.ScopedAttributeELResolver.getType
+
+ (
+ ELContext
+ , Object
+ , Object
+ )
+ | If the base object is null, returns Object.class to indicate that any type is valid to set for a scoped attribute.
+ The propertyResolved property of the ELContext object must be set to true by this resolver before returning if base is null. If this property is not true after this method is called, the caller should ignore the return value.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:430 | Object | jakarta.servlet.jsp.el.ScopedAttributeELResolver.getValue
+
+ (
+ ELContext
+ , Object
+ , Object
+ )
+ | If the base object is null, searches the page, request, session and application scopes for an attribute with the given name and returns it, or null if no attribute exists with the current name.
+ The propertyResolved property of the ELContext object must be set to true by this resolver before returning if base is null. If this property is not true after this method is called, the caller should ignore the return value.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:431 | boolean | jakarta.servlet.jsp.el.ScopedAttributeELResolver.isReadOnly
+
+ (
+ ELContext
+ , Object
+ , Object
+ )
+ | If the base object is null, returns false to indicate that scoped attributes are never read-only.
+ The propertyResolved property of the ELContext object must be set to true by this resolver before returning if base is null. If this property is not true after this method is called, the caller should ignore the return value.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:432 | ScopedAttributeELResolver | jakarta.servlet.jsp.el.ScopedAttributeELResolver.ScopedAttributeELResolver
+ |
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:433 | void | jakarta.servlet.jsp.el.ScopedAttributeELResolver.setValue
+
+ (
+ ELContext
+ , Object
+ , Object
+ , Object
+ )
+ | If the base object is null, sets an existing scoped attribute to the new value, or creates a new scoped attribute if one does not exist by this name.
+ If the provided attribute name matches the key of an attribute in page scope, request scope, session scope, or application scope, the corresponding attribute value will be replaced by the provided value. Otherwise, a new page scope attribute will be created with the given name and value. The propertyResolved property of the ELContext object must be set to true by this resolver before returning if base is null. If this property is not true after this method is called, the caller should ignore the return value.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:434 | void | jakarta.servlet.jsp.tagext.JspIdConsumer.setJspId
+
+ (
+ String
+ )
+ | Called by the container generated code to set a value for the jspId attribute.
+ An unique identification string, relative to this page, is generated at translation time.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:435 | TagAttributeInfo | jakarta.servlet.jsp.tagext.TagAttributeInfo.TagAttributeInfo
+
+ (
+ String
+ , boolean
+ , String
+ , boolean
+ , boolean
+ , String
+ , boolean
+ , boolean
+ , String
+ , String
+ )
+ | JSP 2.1 Constructor for TagAttributeInfo.
+ This class is to be instantiated only from the TagLibrary code under request from some JSP code that is parsing a TLD (Tag Library Descriptor).
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:436 | boolean | jakarta.servlet.jsp.tagext.TagAttributeInfo.isDeferredValue
+ | Returns true if this attribute is to be passed a ValueExpression so that expression evaluation can be deferred.
+ If this method returns true, then getTypeName() must return "jakarta.el.ValueExpression". The getExpectedType() method can be used to retrieve the expected type this value expression will be constructed with.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:437 | boolean | jakarta.servlet.jsp.tagext.TagAttributeInfo.isDeferredMethod
+ | Returns true if this attribute is to be passed a MethodExpression so that expression evaluation can be deferred.
+ If this method returns true, then getTypeName() must return "jakarta.el.MethodExpression". The getMethodSignature() method can be used to retrieve the expected method signature this method expression will be constructed with.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:438 | String | jakarta.servlet.jsp.tagext.TagAttributeInfo.getExpectedTypeName
+ | Returns the name of the expected type (as a String) of this deferred value attribute.
+ This method returns null if isDeferredValue() returns false.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:439 | String | jakarta.servlet.jsp.tagext.TagAttributeInfo.getMethodSignature
+ | Returns the expected method signature of this deferred method attribute.
+ This method returns null if isDeferredMethod() returns false.
+
+ | true |
+
+ | true |
+
+
+JSP:JAVADOC:440 | TagLibraryInfo[] | jakarta.servlet.jsp.tagext.TagLibraryInfo.getTagLibraryInfos
+ | Returns an array of TagLibraryInfo objects representing the entire set of tag libraries (including this TagLibraryInfo) imported by taglib directives in the translation unit that references this TagLibraryInfo.
+ If a tag library is imported more than once and bound to different prefices, only the TagLibraryInfo bound to the first prefix must be included in the returned array.
+
+ | true |
+
+ | true |
+
+
+
+
diff --git a/tck/docs/assertions/JakartaServerPagesSpecAssertions.html b/tck/docs/assertions/JakartaServerPagesSpecAssertions.html
new file mode 100644
index 00000000..21c51430
--- /dev/null
+++ b/tck/docs/assertions/JakartaServerPagesSpecAssertions.html
@@ -0,0 +1,4997 @@
+
+
+
+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 |
+
+
+
+
diff --git a/tck/docs/index.html b/tck/docs/index.html
new file mode 100644
index 00000000..e9f3f134
--- /dev/null
+++ b/tck/docs/index.html
@@ -0,0 +1,83 @@
+
+
+
+ The online version of the JT Harness version 5.0 documentation is
+ available here.
+