The tag handler invoking the fragment is responsible for
@@ -854,7 +849,7 @@ Invocation of a JSP Fragment
In the case of tag files, for each variable declared
in scope AT_BEGIN or NESTED, if a page
scoped attribute exists with the provided name in the tag file, the
- JSP container must generate code to create/update the page scoped
+ Jakarta Pages (JSP) container must generate code to create/update the page scoped
attribute of the provided name in the calling page/tag. If a page
scoped attribute with the provided name does not exist in the tag
file, and a page scoped attribute of the provided name is present in
@@ -916,9 +911,9 @@ Invocation of a JSP Fragment
The following non-normative example is intended to help solidify
-some of the concepts relating to Tag Files, JSP Fragments and Simple
+some of the concepts relating to Tag Files, Jakarta Pages (JSP) Fragments and Simple
Tag Handlers. In the first section, two sample input files are
-presented, a JSP (my.jsp), and a simple tag handler implemented using
+presented, a page (my.jsp), and a simple tag handler implemented using
a tag file (simpletag.tag). One possible output of the translation
process is presented in the second section.
@@ -933,9 +928,9 @@
- "Step T.x" = Annotated step x from "Lifecycle of Simple Tag
Handlers" earlier in this Chapter.
- - "Step C.x" = Annotated step x from "Creation of a JSP Fragment"
+
- "Step C.x" = Annotated step x from "Creation of a Jakarta Pages (JSP) Fragment"
earlier in this Chapter.
- - "Step F.x" = Annotated step x from "Invocation of a JSP Fragment"
+
- "Step F.x" = Annotated step x from "Invocation of a Jakarta Pages (JSP) Fragment"
earlier in this Chapter.
@@ -945,7 +940,7 @@ Sample Source Files
This section presents the sample source files in this scenario,
from which the output files are generated.
-Original JSP (my.jsp)
+Original page (my.jsp)
<%@ taglib prefix="my" tagdir="/WEB-INF/tags" %>
@@ -985,7 +980,7 @@ Original Tag File (/WEB-INF/tags/simpletag.tag)
Sample Generated Files
This section presents sample output files that might be generated
-by a JSP compiler, from the source files presented in the
+by a Jakarta Pages (JSP) compiler, from the source files presented in the
previous section.
Helper class for JspFragment (JspFragmentBase.java)
@@ -1004,7 +999,7 @@ Helper class for JspFragment (JspFragmentBase.java)
}
}
-Relevant Portion of JSP Service Method
+Relevant Portion of Jakarta Pages (JSP) Service Method
// Step T.1 - Initial creation
MySimpleTag _jsp_mySimpleTag = new MySimpleTag();
@@ -1276,9 +1271,9 @@ Tag mapping, Tag name
prefix to it. The TLD associated with the library associates Tag
handler classes (plus other information) with tag names. This
information is used to associate a Tag class, a prefix, and a name
-with each custom action element appearing in a JSP page.
+with each custom action element appearing in a Jakarta Pages (JSP) page.
- At execution time the implementation of a JSP page will use an
+
At execution time the implementation of a Jakarta Pages (JSP) page will use an
available Tag instance with the appropriate property settings and then
follow the protocol described by the interfaces Tag, IterationTag,
BodyTag, SimpleTag, and TryCatchFinally. The implementation guarantees
@@ -1289,8 +1284,8 @@
Tag mapping, Tag name
Scripting Variables
- JSP supports scripting variables that can be declared within a
-scriptlet and can be used in another. JSP actions also can be used to
+
Jakarta Pages (JSP) supports scripting variables that can be declared within a
+scriptlet and can be used in another. Jakarta Pages (JSP) actions also can be used to
define scripting variables so they can used in scripting elements, or
in other actions. This is very useful in some cases; for example, the
jsp:useBean standard action may define an object which
@@ -1313,17 +1308,17 @@
Validation
The TLD file contains several pieces of information that is used
to do syntactic validation at translation-time. It also contains two
extensible validation mechanisms: a TagLibraryValidator
-class can be used to validate a complete JSP page, and a
+class can be used to validate a complete Jakarta Pages (JSP) page, and a
TagExtraInfo class can be used to validate a specific
action. In some cases, additional request-time validation will be done
dynamically within the methods in the Tag instance. If an error is
discovered, an instance of JspTagException can be thrown.
-If uncaught, this object will invoke the errorpage mechanism of JSP.
+If uncaught, this object will invoke the errorpage mechanism of Jakarta Pages (JSP).
The TagLibraryValidator is an addition to the JSP 1.2
specification and is very open ended, being strictly more powerful
-than the TagExtraInfo mechanism. A JSP page is presented via the
-PageData object, which abstracts the XML view of the JSP
+than the TagExtraInfo mechanism. A Jakarta Pages (JSP) page is presented via the
+PageData object, which abstracts the XML view of the Jakarta Pages (JSP)
page.
A PageData instance will provides an InputStream (read-only) on the
@@ -1332,9 +1327,9 @@
Validation
the InputStream and perhaps can be cached for improved performance
(recall the view of the page is just read-only).
- As of JSP 2.0, the JSP container must support a jsp:id attribute to
+
As of JSP 2.0, the Jakarta Pages (JSP) container must support a jsp:id attribute to
provide higher quality validation errors. The
-container will track the JSP pages as passed to the container, and
+container will track the Jakarta Pages (JSP) pages as passed to the container, and
will assign to each element a unique "id", which is passed as the
value of the jsp:id attribute. Each XML element in the XML view
will be extended with this attribute. The
@@ -1353,7 +1348,7 @@
Validation Details
In detail, validation is done as follows:
-
First, the JSP page is parsed using the information in the TLD.
+
First, the Jakarta Pages (JSP) page is parsed using the information in the TLD.
At this stage valid mandatory and optional attributes are checked.
Second, for each unique tag library in the page as determined
diff --git a/jdsol-spec/pom.xml b/jdsol-spec/pom.xml
index af6bceab..1f1b4a8b 100644
--- a/jdsol-spec/pom.xml
+++ b/jdsol-spec/pom.xml
@@ -66,7 +66,7 @@
- JSP dev mailing list
+ Jakarta Pages (JSP) dev mailing list
jsp-dev@eclipse.org
https://accounts.eclipse.org/mailing-list/jsp-dev
https://accounts.eclipse.org/mailing-list/jsp-dev
diff --git a/jdsol-spec/src/main/asciidoc/jdsol.adoc b/jdsol-spec/src/main/asciidoc/jdsol.adoc
index 1c9d3da5..df67e53b 100644
--- a/jdsol-spec/src/main/asciidoc/jdsol.adoc
+++ b/jdsol-spec/src/main/asciidoc/jdsol.adoc
@@ -1054,11 +1054,11 @@ The items of the `SourceDebugExtension_attribute` structure are as follows:
== Example
The example below shows how the process described above would apply to a tiny
-JSP program.
+Jakarta Pages (JSP) program.
=== Input Source
-The input consists of two JSP files, the first is `Hello.jsp`:
+The input consists of two Jakarta Pages (JSP) files, the first is `Hello.jsp`:
[cols="10%,90%",]
|===
@@ -1072,7 +1072,7 @@ The input consists of two JSP files, the first is `Hello.jsp`:
| 8 |` `
|===
-The second JSP file is the included file `greeting.jsp`:
+The second Jakarta Pages (JSP) file is the included file `greeting.jsp`:
[cols="10%,90%"]
|===
@@ -1082,7 +1082,7 @@ The second JSP file is the included file `greeting.jsp`:
=== Language Processor
-When a JSP compiler (the <>) compiles
+When a Jakarta Pages (JSP) compiler (the <>) compiles
these files it will produce two outputs - a Java programming language source
file and a <>. The generated Java programming
language source file is `HelloServlet.java`:
diff --git a/spec/pom.xml b/spec/pom.xml
index 6b1d10f1..64892692 100644
--- a/spec/pom.xml
+++ b/spec/pom.xml
@@ -65,7 +65,7 @@
- JSP dev mailing list
+ Jakarta Pages (JSP) dev mailing list
jsp-dev@eclipse.org
https://accounts.eclipse.org/mailing-list/jsp-dev
https://accounts.eclipse.org/mailing-list/jsp-dev
diff --git a/spec/src/main/asciidoc/images/sp-11.svg b/spec/src/main/asciidoc/images/sp-11.svg
index d18d6d37..6272ad4f 100644
--- a/spec/src/main/asciidoc/images/sp-11.svg
+++ b/spec/src/main/asciidoc/images/sp-11.svg
@@ -46,11 +46,11 @@
Foglio.11
- JSP Page
+ Jakarta Pages (JSP) Page
- JSP Page
+ Jakarta Pages (JSP) Page
Foglio.12
TRANSLATION PHASE
@@ -72,11 +72,11 @@
Foglio.2
- JSP Container
+ Jakarta Pages (JSP) Container
- JSP Container
+ Jakarta Pages (JSP) Container
Foglio.3
diff --git a/spec/src/main/asciidoc/images/sp-4.svg b/spec/src/main/asciidoc/images/sp-4.svg
index 4e822c49..efd09590 100644
--- a/spec/src/main/asciidoc/images/sp-4.svg
+++ b/spec/src/main/asciidoc/images/sp-4.svg
@@ -63,11 +63,11 @@
Foglio.2
- JSP Syntax
+ Jakarta Pages (JSP) Syntax
- JSPJakarta Pages (JSP)Syntax
Foglio.3
@@ -103,11 +103,11 @@
Foglio.11
- JSP Pages
+ Jakarta Pages (JSP) Pages
- JSP Pages
+ Jakarta Pages (JSP) Pages
Foglio.12
TRANSLATION PHASE
@@ -147,11 +147,11 @@
Foglio.143
- JSP Implementation Class
+ Jakarta Pages (JSP) Implementation Class
- JSP Implementation Jakarta Pages (JSP) Implementation Class
Foglio.144
diff --git a/spec/src/main/asciidoc/server-pages-spec-body.adoc b/spec/src/main/asciidoc/server-pages-spec-body.adoc
index 653116ac..a983db1f 100644
--- a/spec/src/main/asciidoc/server-pages-spec-body.adoc
+++ b/spec/src/main/asciidoc/server-pages-spec-body.adoc
@@ -7,7 +7,7 @@
:jsp-chapter: 0
:sectnums!:
-== Jakarta Server Pages Specification, Version 4.1
+== Jakarta Pages Specification, Version 4.1
Copyright (c) 2013, 2026 Oracle and/or its affiliates and others.
All rights reserved.
@@ -17,22 +17,20 @@ is a trademark of the Eclipse Foundation. Oracle and Java are
registered trademarks of Oracle and/or its affiliates. Other names
may be trademarks of their respective owners.
-The Jakarta Server Pages Team - {revdate}
-
+The Jakarta Pages Team - {revdate}
Comments to: jsp-dev@eclipse.org
=== Preface
-This is the Jakarta Server Pages specification
-version 4.1, developed by the Jakarta Server Pages Team under the Eclipse
-Foundation Specification Process. References in this document to JSP refer
-to Jakarta Server Pages unless otherwise noted.
+This is the Jakarta Pages specification
+version 4.1, developed by the Jakarta Pages Team under the Eclipse
+Foundation Specification Process.
==== Who Should Read This Document
-This document is the authoritative JSP 4.1
+This document is the authoritative Jakarta Pages (JSP) 4.1
specification. It is intended to provide requirements for
-implementations of JSP page processing, and support by web containers in
+implementations of Jakarta Pages (JSP) page processing, and support by web containers in
web servers and application servers. As an authoritative document, it
covers material pertaining to a wide audience, including _Page Authors_,
_Tag Library Developers_, _Deployers_, _Container Vendors_, and
@@ -49,13 +47,13 @@ Chapters and Appendices that are organized into 3 parts. In addition,
the document contains a <> (this section) and an <>.
<>
-contains several chapters intended for all JSP Page Authors. These
+contains several chapters intended for all Jakarta Pages (JSP) Page Authors. These
chapters describe the general structure of the language, including the
expression language, fragments, and scripting.
<>
-contains detailed chapters on the JSP container engine and API in full
-detail. The information in this part is intended for advanced JSP users.
+contains detailed chapters on the Jakarta Pages (JSP) container engine and API in full
+detail. The information in this part is intended for advanced Jakarta Pages (JSP) users.
Finally, <> contains all the appendices.
@@ -66,63 +64,63 @@ Community Process as part of JSR 245.
=== Overview
-==== The Jakarta Server Pages Technology
+==== The Jakarta Pages Technology
-Jakarta Server Pages (JSP) is the Jakarta EE technology for building
+Jakarta Pages (JSP) is the Jakarta EE technology for building
applications for generating dynamic web content, such as HTML, DHTML,
-XHTML, and XML. JSP technology enables the easy authoring of web pages
+XHTML, and XML. Jakarta Pages (JSP) technology enables the easy authoring of web pages
that create dynamic content with maximum power and flexibility.
===== General Concepts
-JSP technology provides the means for textual
+Jakarta Pages (JSP) technology provides the means for textual
specification of the creation of a dynamic _response_ to a _request_. The
technology builds on the following concepts:
* _Template Data_ +
A substantial portion of most dynamic content
is fixed or _template_ content. Text or XML fragments are typical
-template data. JSP technology supports natural manipulation of template
+template data. Jakarta Pages (JSP) technology supports natural manipulation of template
data.
* _Addition of Dynamic Data_ +
-JSP technology provides a simple, yet
+Jakarta Pages (JSP) technology provides a simple, yet
powerful, way to add dynamic data to template data.
* _Encapsulation of Functionality_ +
-JSP technology provides two related
+Jakarta Pages (JSP) technology provides two related
mechanisms for the encapsulation of functionality: JavaBeans™ component
architecture, and tag libraries delivering custom actions, functions,
listener classes, and validation.
* _Good Tool Support_ +
Good tool support leads to significantly
-improved productivity. Accordingly, JSP technology has features that
+improved productivity. Accordingly, Jakarta Pages (JSP) technology has features that
enable the creation of good authoring tools.
Careful development of these concepts yields a flexible and powerful
server-side technology.
-===== Benefits of Jakarta Server Pages Technology
+===== Benefits of Jakarta Pages Technology
-JSP technology offers the following benefits:
+Jakarta Pages (JSP) technology offers the following benefits:
* _Write Once, Run Anywhere properties_ +
-JSP technology is platform independent in its
+Jakarta Pages (JSP) technology is platform independent in its
dynamic web pages, its web servers, and its underlying server
-components. JSP pages may be authored on any platform, run on any web
+components. Jakarta Pages (JSP) may be authored on any platform, run on any web
server or web enabled application server, and accessed from any web
browser. Server components can be built on any platform and run on any
server.
* _High quality tool support_ +
-Platform independence allows the JSP user to
+Platform independence allows the Jakarta Pages (JSP) user to
choose best-of-breed tools. Additionally, an explicit goal of the
-Jakarta Server Pages design is to enable the creation of high quality
+Jakarta Pages design is to enable the creation of high quality
portable tools.
* _Separation of Roles_ +
-JSP supports the separation of developer and
+Jakarta Pages (JSP) supports the separation of developer and
author roles. _Developers_ write components that interact with server-side
objects. _Authors_ put static data and dynamic content together to create
presentations suited for their intended audience. +
@@ -136,7 +134,7 @@ engaged in developing reusable components intended to be used by
authors.
* _Reuse of components and tag libraries_ +
-Jakarta Server Pages technology emphasizes the
+Jakarta Pages technology emphasizes the
use of reusable components such as JavaBeans components, Enterprise
JavaBeans™ components, and tag libraries. These components can be used
with interactive tools for component development and page composition,
@@ -145,7 +143,7 @@ provide the cross-platform power and flexibility of the Java programming
language or other scripting languages.
* _Separation of dynamic and static content_ +
-Jakarta Server Pages technology enables the
+Jakarta Pages technology enables the
separation of static content in a template from dynamic content that is
inserted into the static template. This greatly simplifies the creation
of content. The separation is supported by beans specifically designed
@@ -153,7 +151,7 @@ for the interaction with server-side objects, and by the tag extension
mechanism.
* _Support for actions, expressions, and scripting_ +
-Jakarta Server Pages technology supports
+Jakarta Pages technology supports
scripting elements as well as actions. Actions encapsulate useful
functionality in a convenient form that can be manipulated by tools.
Expressions are used to access data. Scripts can be used to glue
@@ -162,16 +160,16 @@ Expressions in the EL
directly express page author concepts like properties in beans and
provide more controlled access to the Web Application data. Functions
defined through the tag library mechanism can be accessed in the EL. +
-Page authors can write actions using the JSP
+Page authors can write actions using the Jakarta Pages (JSP)
technology directly. This greatly increases the ease with which action
abstractions can be created.
* _Web access layer for N-tier enterprise
application architecture(s)_ +
-Jakarta Server Pages technology is an integral
+Jakarta Pages technology is an integral
part of Jakarta EE. The Jakarta EE platform brings Java technology to
enterprise computing. One can now develop powerful middle-tier server
-applications that include a web site using Jakarta Server Pages technology
+applications that include a web site using Jakarta Pages technology
as a front end to Enterprise JavaBeans components in a Jakarta EE compliant
environment.
@@ -180,13 +178,13 @@ environment.
This section introduces basic concepts that
will be defined formally later in the specification.
-===== What Is a JSP Page?
+===== What Is a Jakarta Pages (JSP) Page?
-A JSP page is a text-based document that
+A Jakarta Pages (JSP) page is a text-based document that
describes how to process a _request_ to create a _response_. The description
intermixes template data with dynamic actions and leverages the Java
-Platform. JSP technology supports a number of different paradigms for
-authoring dynamic content. The key features of Jakarta Server Pages are:
+Platform. Jakarta Pages (JSP) technology supports a number of different paradigms for
+authoring dynamic content. The key features of Jakarta Pages are:
* Standard directives
* Standard actions
@@ -201,7 +199,7 @@ from the servlet specification. A web application can be composed of:
* Java Runtime Environment(s) running on the
server (required)
-* JSP page(s) that handle requests and
+* Jakarta Pages (JSP) page(s) that handle requests and
generate dynamic content
* Servlet(s) that handle requests and
generate dynamic content
@@ -210,16 +208,16 @@ encapsulate behavior and state
* Static HTML, DHTML, XHTML, XML, and similar
pages.
-The Jakarta Server Pages specification inherits
+The Jakarta Pages specification inherits
from the servlet specification the concepts of web applications,
servlet contexts, sessions, and requests and responses. See the Jakarta
Servlet 6.2 specification for more details.
===== Components and Containers
-JSP pages and servlet classes are
-collectively referred to as _web components_. JSP pages are delivered to a
-_container_ that provides the services indicated in the _JSP Component
+Jakarta Pages (JSP) and servlet classes are
+collectively referred to as _web components_. Jakarta Pages (JSP) are delivered to a
+_container_ that provides the services indicated in the _Jakarta Pages (JSP) Component
Contract_.
The separation of components from containers
@@ -228,58 +226,58 @@ provided by the container.
===== Translation and Execution Steps
-JSP pages are textual components. They go
+Jakarta Pages (JSP) are textual components. They go
through two phases: a _translation_ phase, and a _request_ phase.
Translation is performed once per page. The request phase is performed once per
request.
-The JSP page is translated to create a
-servlet class, the JSP page implementation class, that is instantiated
-at request time. The instantiated JSP page object handles requests and
+The Jakarta Pages (JSP) page is translated to create a
+servlet class, the Jakarta Pages (JSP) page implementation class, that is instantiated
+at request time. The instantiated Jakarta Pages (JSP) page object handles requests and
creates responses.
-JSP pages may be translated prior to their
+Jakarta Pages (JSP) may be translated prior to their
use, providing the web application with a servlet class that can serve
-as the textual representation of the JSP page.
+as the textual representation of the Jakarta Pages (JSP) page.
-The translation may also be done by the JSP
+The translation may also be done by the Jakarta Pages (JSP)
container at deployment time, or on-demand as the requests reach an
-untranslated JSP page.
+untranslated Jakarta Pages (JSP) page.
===== Deployment Descriptor and Global Information
-The JSP pages delivered in a web application
-may require some JSP configuration information. This information is
-delivered through JSP-specific elements in the `web.xml` deployment
+The Jakarta Pages (JSP) delivered in a web application
+may require some Jakarta Pages (JSP) configuration information. This information is
+delivered through Jakarta Pages (JSP) specific elements in the `web.xml` deployment
descriptor, rooted on the `` element. Configuration
information includes `` elements for mapping of tag libraries and
`` elements used to provide properties of
-collections of JSP files. The properties that can be indicated this way
+collections of Jakarta Pages (JSP) files. The properties that can be indicated this way
include page encoding information, EL evaluation activation, automatic
includes before and after pages, and whether scripting is enabled in a
given page.
===== Role in Jakarta EE
-With a few exceptions, integration of JSP pages within Jakarta EE is inherited
-from the Servlet specification since translation turns JSPs into servlets.
+With a few exceptions, integration of Jakarta Pages (JSP) within Jakarta EE is inherited
+from the Servlet specification since translation turns Jakarta Pages (JSPs) into servlets.
-==== Users of Jakarta Server Pages
+==== Users of Jakarta Pages
There are six classes of users that interact
-with Jakarta Server Pages technology. This section describes each class of
+with Jakarta Pages technology. This section describes each class of
user, enumerates the technologies each must be familiar with, and
identifies which sections of this specification are most relevant to
-each user class. The intent is to ensure that Jakarta Server Pages remains a
+each user class. The intent is to ensure that Jakarta Pages remains a
practical and easy-to-use technology for each class of user, even as the
language continues to grow.
===== Page Authors
Page Authors are application component
-providers that use Jakarta Server Pages to develop the presentation
+providers that use Jakarta Pages to develop the presentation
component of a web application. It is expected that they will not make
-use of the scripting capabilities of Jakarta Server Pages, but rather limit
+use of the scripting capabilities of Jakarta Pages, but rather limit
their use to standard and custom actions. Therefore, it is assumed that
they know the target language, such as HTML or XML, and basic XML
concepts, but they need not know Java at all.
@@ -290,37 +288,37 @@ this class of user:
* <>, except for <> and
<>, which both talk about scripting
* <>
-* <>
+* <>
* <>
* <>
-* <>, except for sections that discuss declarations, scriptlets, expressions, and request-time attributes
+* <>, except for sections that discuss declarations, scriptlets, expressions, and request-time attributes
* <> and <> of <>
* <>
-* Appendices <>, <>, and <>
+* Appendices <>, <>, and <>
===== Advanced Page Authors
Like Page Authors, Advanced Page Authors are
-also application component providers that use Jakarta Server Pages to
+also application component providers that use Jakarta Pages to
develop the presentation component of a web application. These authors
have a better understanding of XML and also know Java. Though they are
recommended to avoid it where possible, these authors do have scripting
-at their disposal and should be able to read and understand JSPs that
+at their disposal and should be able to read and understand Jakarta Pages (JSPs) that
make use of scripting.
The following sections are most relevant to
this class of user:
-* Chapters <>, <>, <>, <> and <>
-* <>
-* <> and <> of <>
+* Chapters <>, <>, <>, <> and <>
+* <>
+* <> and <> of <>
* <> and <<_Overview>> of <>
* <>
-* <> of <>
-* Appendices <>, <>, and <>
+* <> of <>
+* Appendices <>, <>, and <>
Advanced page authors may also wish to look at the Javadoc for the
-`jakarta.servlet.jsp` package and the XML schema for the JSP 4.1
+`jakarta.servlet.jsp` package and the XML schema for the Jakarta Pages (JSP) 4.1
deployment descriptor.
===== Tag Library Developers
@@ -333,13 +331,13 @@ advanced understanding of the target language, XML, and Java.
The following sections are most relevant to
this class of user:
-* Chapters <>, <>, <>, <> and
+* Chapters <>, <>, <>, <> and
<>
-* <>
-* <> and <> of <>
+* <>
+* <> and <> of <>
* <>
* <>
-* <> of <>
+* <> of <>
* All Appendices
Tag library developers may also wish to look at the Javadoc for the
@@ -357,28 +355,28 @@ ability to read deployment descriptors.
The following sections are most relevant to
this class of user:
-* <> and <> of
+* <> and <> of
<>
-* <>
+* <>
* <>
-* <>
+* <>
* All Appendices
===== Container Developers and Tool Vendors
Container Developers develop containers that
-host Jakarta Server Pages. Tool Vendors write development tools to assist
+host Jakarta Pages. Tool Vendors write development tools to assist
Page Authors, Advanced Page Authors, Tag Library Developers, and
Deployers. Both Container Developers and Tool Vendors must know XML and
Java, and must know all the requirements and technical details of
-Jakarta Server Pages. Therefore, this entire specification is relevant to
+Jakarta Pages. Therefore, this entire specification is relevant to
both classes of user.
= Part I
The next chapters form the core of the
-JSP specification. These chapters provide information for Page authors,
+Jakarta Pages (JSP) specification. These chapters provide information for Page authors,
Tag Library developers, deployers and Container and Tool vendors.
The chapters of this part are:
@@ -388,7 +386,7 @@ The chapters of this part are:
* Configuration Information
* Internationalization Issues
* Standard Actions
-* JSP Documents
+* Jakarta Pages (JSP) Documents
* Tag Extensions
* Tag Files
* Scripting
@@ -400,248 +398,248 @@ The chapters of this part are:
== Core Syntax and Semantics{counter2:jsp-chapter}
This chapter describes the core syntax
-and semantics for the Jakarta Server Pages 4.1 specification (JSP 4.1).
+and semantics for the Jakarta Pages (JSP) 4.1 specification.
-=== What Is a JSP Page
+=== What Is a Jakarta Pages (JSP) Page
-A JSP page is a textual document that
+A Jakarta Pages (JSP) page is a textual document that
describes how to create a response object from a request object for a
-given protocol. The processing of the JSP page may involve creating
+given protocol. The processing of the Jakarta Pages (JSP) page may involve creating
and/or using other objects.
-A JSP page defines a JSP page implementation
-class that implements the semantics of the JSP page. This class
+A Jakarta Pages (JSP) page defines a Jakarta Pages (JSP) page implementation
+class that implements the semantics of the Jakarta Pages (JSP) page. This class
implements the `jakarta.servlet.Servlet` interface (see
-<> for details). At request time a
-request intended for the JSP page is delivered to the JSP page
+<> for details). At request time a
+request intended for the Jakarta Pages (JSP) page is delivered to the Jakarta Pages (JSP) page
implementation object for processing.
HTTP is the default protocol for requests and
-responses. Additional request/response protocols may be supported by JSP
+responses. Additional request/response protocols may be supported by Jakarta Pages (JSP)
containers. The default `request` and `response` objects are of type
`HttpServletRequest` and `HttpServletResponse` respectively.
==== Web Containers and Web Components
-A JSP container is a system-level entity that
-provides life-cycle management and runtime support for JSP pages and
-servlet components. Requests sent to a JSP page are delivered by the JSP
-container to the appropriate JSP page implementation object. The term
-web container is synonymous with JSP container.
+A Jakarta Pages (JSP) container is a system-level entity that
+provides life-cycle management and runtime support for Jakarta Pages (JSP) and
+servlet components. Requests sent to a Jakarta Pages (JSP) page are delivered by the Jakarta Pages (JSP)
+container to the appropriate Jakarta Pages (JSP) page implementation object. The term
+web container is synonymous with Jakarta Pages (JSP) container.
-A web component is either a servlet or a JSP
+A web component is either a servlet or a Jakarta Pages (JSP)
page. The `servlet` element in a `web.xml` deployment descriptor is used
-to describe both types of web components. JSP page components are
+to describe both types of web components. Jakarta Pages (JSP) page components are
defined implicitly in the deployment descriptor through the use of an
implicit `.jsp` extension mapping, or explicitly through the use of a
`jsp-group` element.
==== Generating HTML
-A traditional application domain of the JSP
-technology is HTML content. The JSP specification supports well this use
+A traditional application domain of the Jakarta Pages (JSP)
+technology is HTML content. The Jakarta Pages (JSP) specification supports well this use
through a syntax that is friendly to HTML and XML although it is not
HTML-specific; for instance, HTML comments are treated no differently
-than other HTML content. The JSP Standard Tag Library has specific
+than other HTML content. The Jakarta Standard Tag Library has specific
support for HTML though some specific custom actions.
==== Generating XML
An increasingly important application domain
-for JSP technology is dynamic XML content using formats like XHTML, SVG
+for Jakarta Pages (JSP) technology is dynamic XML content using formats like XHTML, SVG
and the Open Office format, and in applications like content publishing,
-data representation and Web Services. The basic JSP machinery (JSP
+data representation and Web Services. The basic Jakarta Pages (JSP) machinery (standard
syntax) can be used to generate XML content, but it is also possible to
-tag a JSP page as a JSP document and get additional benefits.
+tag a Jakarta Pages (JSP) page as a Jakarta Pages (JSP) document and get additional benefits.
-A JSP document is an XML document; this means
-that a JSP document is a well-formed, structured document and that this
-will be validated by the JSP container. Additionally, this structure
-will be available to the JSP validation machinery, the
-TagLibraryValidators. A JSP document is a namespace-aware XML document,
+A Jakarta Pages (JSP) document is an XML document; this means
+that a Jakarta Pages (JSP) document is a well-formed, structured document and that this
+will be validated by the Jakarta Pages (JSP) container. Additionally, this structure
+will be available to the Jakarta Pages (JSP) validation machinery, the
+TagLibraryValidators. A Jakarta Pages (JSP) document is a namespace-aware XML document,
with namespaces reflecting the structure of both content and custom
-actions and with some additional care, a JSP page can reflect quite
-accurately the structure of the resulting content. A JSP document can
+actions and with some additional care, a Jakarta Pages (JSP) document can reflect quite
+accurately the structure of the resulting content. A Jakarta Pages (JSP) document can
also use machinery like entity definitions.
The JSP 1.2 specification made a stronger
-distinction between JSP documents and non-XML JSP pages. For instance
-standard actions like were only available in JSP
+distinction between Jakarta Pages (JSP) documents and non-XML Jakarta Pages (JSP). For instance
+standard actions like were only available in Jakarta Pages (JSP)
documents. The difference proved to be confusing and distracting and the
distinction was relaxed in JSP 2.0 to facilitate the transition
-from the JSP syntax to XML syntax.
+from the standard syntax to XML syntax.
==== Translation and Execution Phases
-A JSP container manages two phases of a JSP
+A Jakarta Pages (JSP) container manages two phases of a Jakarta Pages (JSP)
page’s lifecycle. In the translation phase, the container validates the
-syntactic correctness of the JSP pages and tag files and determines a
-JSP page implementation class that corresponds to the JSP page. In the
+syntactic correctness of the Jakarta Pages (JSP) and tag files and determines a
+Jakarta Pages (JSP) page implementation class that corresponds to the Jakarta Pages (JSP) page. In the
execution phase the container manages one or more instances of this
class in response to requests and other events.
During the translation phase the container
-locates or creates the JSP page implementation class that corresponds to
-a given JSP page. This process is determined by the semantics of the JSP
+locates or creates the Jakarta Pages (JSP) page implementation class that corresponds to
+a given Jakarta Pages (JSP) page. This process is determined by the semantics of the Jakarta Pages (JSP)
page. The container interprets the standard directives and actions, and
the custom actions referencing tag libraries used in the page. A tag
library may optionally provide a validation method acting on the XML
-View of a JSP page, see below, to validate that a JSP page is correctly
+View of a Jakarta Pages (JSP) page, see below, to validate that a Jakarta Pages (JSP) page is correctly
using the library.
-A JSP container has flexibility in the
-details of the JSP page implementation class that can be used to address
-quality-of-service--most notably performance-- issues.
+A Jakarta Pages (JSP) container has flexibility in the
+details of the Jakarta Pages (JSP) page implementation class that can be used to address
+quality-of-service, most notably performance, issues.
-During the execution phase the JSP container
-delivers events to the JSP page implementation object. The container is
+During the execution phase the Jakarta Pages (JSP) container
+delivers events to the Jakarta Pages (JSP) page implementation object. The container is
responsible for instantiating request and response objects and invoking
-the appropriate JSP page implementation object. Upon completion of
+the appropriate Jakarta Pages (JSP) page implementation object. Upon completion of
processing, the response object is received by the container for
-communication to the client. The details of the contract between the JSP
-page implementation class and the JSP container are described in
-<>.
+communication to the client. The details of the contract between the Jakarta Pages (JSP)
+page implementation class and the Jakarta Pages (JSP) container are described in
+<>.
-The translation of a JSP source page into its
+The translation of a Jakarta Pages (JSP) source page into its
implementation class can occur at any time between initial deployment of
-the JSP page into the JSP container and the receipt and processing of a
-client request for the target JSP page. <> describes
+the Jakarta Pages (JSP) page into the Jakarta Pages (JSP) container and the receipt and processing of a
+client request for the target Jakarta Pages (JSP) page. <> describes
how to perform the translation phase ahead of deployment.
-==== Validating JSP pages
+==== Validating Jakarta Pages (JSP)
-All JSP pages, regardless of whether they are
-written in the traditional JSP syntax or the XML syntax of JSP documents,
-have an equivalent XML document, the XML view of a JSP page, that is
+All Jakarta Pages (JSP), regardless of whether they are
+written in the standard syntax or the XML syntax of Jakarta Pages (JSP) documents,
+have an equivalent XML document, the XML view of a Jakarta Pages (JSP) page, that is
presented to tag library validators in the translation phase for
validation.
-The structure of the custom actions in a JSP
+The structure of the custom actions in a Jakarta Pages (JSP)
page is always exposed in the XML view. This means that a tag library
validator can check that, for instance, some custom actions are only
used within others.
-The structure of the content used in a JSP
+The structure of the content used in a Jakarta Pages (JSP)
page is exposed in greater or lesser detail depending on whether the XML
-syntax or the traditional JSP syntax is used. When using XML syntax a
+syntax or the standard syntax is used. When using XML syntax a
tag library validator can use that extra structure to, for example,
check that some actions are only used with some content, or within some
content, and, using knowledge of the semantics of the custom actions,
make assertions on the generated dynamic content.
-==== Events in JSP Pages
+==== Events in Jakarta Pages (JSP)
-A JSP page may indicate how some events are
+A Jakarta Pages (JSP) page may indicate how some events are
to be handled.
As of JSP 1.2 only `init` and `destroy`
-events can be described in the JSP page. When the first request is
-delivered to a JSP page, a `jspInit()` method, if present, will be
-called to prepare the page. Similarly, a JSP container invokes a JSP’s
-`jspDestroy()` method to reclaim the resources used by the JSP page at
+events can be described in the Jakarta Pages (JSP) page. When the first request is
+delivered to a Jakarta Pages (JSP) page, a `jspInit()` method, if present, will be
+called to prepare the page. Similarly, a Jakarta Pages (JSP) container invokes a Jakarta Pages (JSP)’s
+`jspDestroy()` method to reclaim the resources used by the Jakarta Pages (JSP) page at
any time when a request is not being serviced. This is the same
life-cycle as for servlets.
-==== JSP Configuration Information
+==== Jakarta Pages (JSP) Configuration Information
-JSP pages may be extended with configuration
-information that is delivered in the JSP configuration portion of the
-`web.xml` deployment descriptor of the web application. The JSP
+Jakarta Pages (JSP) may be extended with configuration
+information that is delivered in the Jakarta Pages (JSP) configuration portion of the
+`web.xml` deployment descriptor of the web application. The Jakarta Pages (JSP)
configuration information includes interpretation for the tag libraries
-used in the JSP files and different property information for groups of
-JSP files. The property information includes: page encoding information,
+used in the Jakarta Pages (JSP) files and different property information for groups of
+Jakarta Pages (JSP) files. The property information includes: page encoding information,
whether the EL evaluation and the scripting machinery is enabled, and
-prelude and coda automatic inclusions. The JSP configuration information
+prelude and coda automatic inclusions. The Jakarta Pages (JSP) configuration information
can also be used to indicate that some resources in the web application
-are JSP files even if they do not conform to the default `.jsp`
+are Jakarta Pages (JSP) files even if they do not conform to the default `.jsp`
extension, and to modify the default interpretation for `.jspx`.
-==== Naming Conventions for JSP Files
+==== Naming Conventions for Jakarta Pages (JSP) Files
-A JSP page is packaged as one or more JSP
-files, often in a web application, and delivered to a tool like a JSP
-container, a Jakarta EE container, or an IDE. A complete JSP page may be
+A Jakarta Pages (JSP) page is packaged as one or more Jakarta Pages (JSP)
+files, often in a web application, and delivered to a tool like a Jakarta Pages (JSP)
+container, a Jakarta EE container, or an IDE. A complete Jakarta Pages (JSP) page may be
contained in a single file. In other cases, the top file will include
-other files that contain complete JSP pages, or included segments of
+other files that contain complete Jakarta Pages (JSP), or included segments of
pages.
It is common for tools to need to
-differentiate JSP files from other files. In some cases, the tools also
-need to differentiate between top JSP files and included segments. For
-example, a segment may not be a legal JSP page and may not compile
+differentiate Jakarta Pages (JSP) files from other files. In some cases, the tools also
+need to differentiate between top Jakarta Pages (JSP) files and included segments. For
+example, a segment may not be a legal Jakarta Pages (JSP) page and may not compile
properly. Determining the type of file is also very useful from a
documentation and maintenance point of view, as people familiar with the
`.c` and `.h` convention in the C language know.
By default the extension `.jsp` means a
-top-level JSP file. We recommend, but do not mandate, to differentiate
-between top-level JSP files (invoked directly by the client or
+top-level Jakarta Pages (JSP) file. We recommend, but do not mandate, to differentiate
+between top-level Jakarta Pages (JSP) files (invoked directly by the client or
dynamically included by another page or servlet) and statically included
segments so that:
* The `.jsp` extension is used only for
-files corresponding to top level JSP files, forming a JSP page when
+files corresponding to top level Jakarta Pages (JSP) files, forming a Jakarta Pages (JSP) page when
processed.
* Statically included segments use any other
-extension. As included segments were called ‘JSP fragments’ in past
+extension. As included segments were called ‘Jakarta Pages (JSP) fragments’ in past
versions of this specification, the extension `.jspf` was offered as a
suggestion. This extension is still suggested for consistency reasons,
-despite that they are now called ‘JSP segments’.
+despite that they are now called ‘Jakarta Pages (JSP) segments’.
-JSP documents, that is, JSP pages that are
+Jakarta Pages (JSP) documents, that is, Jakarta Pages (JSP) that are
delivered as XML documents, use the extension `.jspx` by default.
The `jsp-property-group` element of `web.xml`
can be used to indicate that some group of files, perhaps not using
-either of the extensions above, are JSP pages, and can also be used to
+either of the extensions above, are Jakarta Pages (JSP), and can also be used to
indicate which ones are delivered as XML documents.
-==== Compiling JSP Pages
+==== Compiling Jakarta Pages (JSP)
-A JSP page may be compiled into its
+A Jakarta Pages (JSP) page may be compiled into its
implementation class plus deployment information during development (a
-JSP page can also be compiled at deployment time). In this way JSP page
-authoring tools and JSP tag libraries may be used for authoring
+Jakarta Pages (JSP) page can also be compiled at deployment time). In this way Jakarta Pages (JSP) page
+authoring tools and Jakarta Pages (JSP) tag libraries may be used for authoring
servlets. The benefits of this approach include:
* Removal of the start-up lag that occurs
-when a container must translate a JSP page upon receipt of the first
+when a container must translate a Jakarta Pages (JSP) page upon receipt of the first
request.
* Reduction of the footprint needed to run a
-JSP container, as the Java compiler is not needed.
+Jakarta Pages (JSP) container, as the Java compiler is not needed.
-Compilation of a JSP page in the context of a
+Compilation of a Jakarta Pages (JSP) page in the context of a
web application provides resolution of relative URL specifications in
include directives and elsewhere, tag library references, and
translation-time actions used in custom actions.
-A JSP page can also be compiled at deployment
+A Jakarta Pages (JSP) page can also be compiled at deployment
time.
-===== JSP Page Packaging
+===== Jakarta Pages (JSP) Page Packaging
-When a JSP page implementation class depends
-on support classes in addition to the JSP 4.1 and Servlet 6.2 classes,
+When a Jakarta Pages (JSP) page implementation class depends
+on support classes in addition to the Jakarta Pages (JSP) 4.1 and Servlet 6.2 classes,
the support classes are included in the packaged WAR, as defined in the
-Servlet 6.2 specification, for portability across JSP containers.
+Servlet 6.2 specification, for portability across Jakarta Pages (JSP) containers.
-<> contains two examples of JSP pages packaged in
+<> contains two examples of Jakarta Pages (JSP) packaged in
WARs:
-. A JSP page delivered in source form (the
+. A Jakarta Pages (JSP) page delivered in source form (the
most common case).
-. A JSP page translated into an
+. A Jakarta Pages (JSP) page translated into an
implementation class plus deployment information. The deployment
information indicates support classes needed and the mapping between the
-original URL path to the JSP page and the URL for the JSP page
+original URL path to the Jakarta Pages (JSP) page and the URL for the Jakarta Pages (JSP) page
implementation class for that page.
-==== Debugging JSP Pages
+==== Debugging Jakarta Pages (JSP)
In the past debugging tools provided by
development environments have lacked a standard format for conveying
source map information allowing the debugger of one vendor to be used
-with the JSP container of another. JSP 4.1 containers must
+with the Jakarta Pages (JSP) container of another. Jakarta Pages (JSP) 4.1 containers must
support the Jakarta Debugging Support for Other Languages Specification.
Details can be found in <>.
@@ -654,7 +652,7 @@ made up of some of the following:
* Java runtime environment(s) running in the
server (required)
-* JSP page(s) that handle requests and
+* Jakarta Pages (JSP) page(s) that handle requests and
generate dynamic content
* Servlet(s) that handle requests and
generate dynamic content
@@ -668,17 +666,17 @@ Web applications are described in more detail
in the Servlet 6.2 specification.
A web application contains a deployment
-descriptor `web.xml` that contains information about the JSP pages,
+descriptor `web.xml` that contains information about the Jakarta Pages (JSP),
servlets, and other resources used in the web application. The
deployment descriptor is described in detail in the Servlet 6.2
specification.
-JSP 4.1 requires that these resources be
+Jakarta Pages (JSP) 4.1 requires that these resources be
implicitly associated with and accessible through a unique
`ServletContext` instance available as the implicit `application` object
(see <>).
-The application to which a JSP page belongs
+The application to which a Jakarta Pages (JSP) page belongs
is reflected in the `application` object, and has impact on the
semantics of the following elements:
@@ -687,9 +685,9 @@ semantics of the following elements:
* The `jsp:include` action element (see <>).
* The `jsp:forward` action (see<>).
-JSP 4.1 supports portable packaging and
+Jakarta Pages (JSP) 4.1 supports portable packaging and
deployment of web applications through the Servlet 6.2 specification.
-The Jakarta Server Pages specification inherits from the servlet
+The Jakarta Pages specification inherits from the servlet
specification the concepts of applications, `ServletContexts`,
`Sessions`, `Requests` and `Responses`.
@@ -702,39 +700,39 @@ not the scheme, nor authority parts. Some examples are:
* A context-relative path is a path that
starts with a slash (/). It is to be interpreted as relative to the
-application to which the JSP page or tag file belongs. That is, its
+application to which the Jakarta Pages (JSP) page or tag file belongs. That is, its
`ServletContext` object provides the base context URL.
* A page relative path is a path that does
not start with a slash (/). It is to be interpreted as relative to the
-current JSP page, or the current JSP file or tag file, depending on
+current Jakarta Pages (JSP) page, or the current Jakarta Pages (JSP) file or tag file, depending on
where the path is being used. For an `include` directive (see
<>) where the path
-is used in a `file` attribute, the interpretation is relative to the JSP
+is used in a `file` attribute, the interpretation is relative to the Jakarta Pages (JSP)
file or tag file. For a `jsp:include` action (see <>)
where the path is used in a
-`page` attribute, the interpretation is relative to the JSP page. In
+`page` attribute, the interpretation is relative to the Jakarta Pages (JSP) page. In
both cases the current page or file is denoted by some path starting
with `/` that is then modified by the new specification to produce a
path starting with `/`. The new path is interpreted through the
-`ServletContext` object. See <> for exact
+`ServletContext` object. See <> for exact
details on this interpretation.
-The JSP specification uniformly interprets
-paths in the context of the web container where the JSP page is
+The Jakarta Pages (JSP) specification uniformly interprets
+paths in the context of the web container where the Jakarta Pages (JSP) page is
deployed. The specification goes through a mapping translation. The
semantics outlined here apply to the translation-time phase and to the
request-time phase.
-=== Syntactic Elements of a JSP Page
+=== Syntactic Elements of a Jakarta Pages (JSP) Page
This section describes the basic syntax rules
-of JSP pages.
+of Jakarta Pages (JSP).
==== Elements and Template Data
-A JSP page has elements and template data. An
-element is an instance of an element type known to the JSP container.
-Template data is everything else; that is, anything that the JSP
+A Jakarta Pages (JSP) page has elements and template data. An
+element is an instance of an element type known to the Jakarta Pages (JSP) container.
+Template data is everything else; that is, anything that the Jakarta Pages (JSP)
translator does not know about.
The type of an element describes its syntax
@@ -751,7 +749,7 @@ elements, scripting elements, and action elements.
_Directives_ +
Directives provide global information that is
conceptually valid independent of any specific request received by the
-JSP page. They provide information for the translation phase.
+Jakarta Pages (JSP) page. They provide information for the translation phase.
Directive elements have a syntax of the form
`<%@ directive\...%>`.
@@ -759,7 +757,7 @@ Directive elements have a syntax of the form
_Actions_ +
Actions provide information for the request
processing phase. The interpretation of an action may, and often will,
-depend on the details of the specific request received by the JSP page.
+depend on the details of the specific request received by the Jakarta Pages (JSP) page.
An Action can either be standard (that is, defined in this
specification), or custom (that is, provided via the portable tag
extension mechanism).
@@ -786,7 +784,7 @@ An element has an element type describing its
tag name, its valid attributes and its semantics. We refer to the type
by its tag name.
-JSP tags are case-sensitive, as in XML and
+Jakarta Pages (JSP) tags are case-sensitive, as in XML and
XHTML.
An action may create objects and may make
@@ -801,7 +799,7 @@ template text and actions.
The Expression Language (EL) can be used to
simplify accessing data from different sources. EL expressions can be
-used in JSP standard and custom actions and template data. EL
+used in Jakarta Pages (JSP) standard and custom actions and template data. EL
expressions use the syntax `${expr}` and `#{expr}`. For example:
[source,jsp]
@@ -886,14 +884,14 @@ As of JSP 2.0, page authors can provide input
in new ways using the `` standard action element.
Based on the configuration of the action being invoked, the body of the
element either specifies a value that is evaluated once, or it specifies
-a “JSP fragment”, which represents the body in a form that makes it
+a “Jakarta Pages (JSP) fragment”, which represents the body in a form that makes it
possible for a tag handler to evaluate it as many times as needed. The
`` action must only be used to specify an attribute value
for standard or custom actions. A translation error must occur if it is
used in any other context, for example to specify the value of template
text that looks like an XML element.
-It is illegal JSP syntax, which must result
+It is illegal standard syntax, which must result
in a translation error, to use both an XML element attribute and a
`` standard action to pass the value of the same
attribute. See <> for more
@@ -978,14 +976,14 @@ with no leading whitespace characters.
This specification follows the whitespace
behavior defined for XML. White space within the body text of a document
is not significant, but is preserved. This default behavior can be
-modified for JSP pages in standard syntax as described in
+modified for Jakarta Pages (JSP) in standard syntax as described in
<>.
-Next are two examples of JSP code with their
+Next are two examples of Jakarta Pages (JSP) code with their
associated output. Note that directives generate no data and apply
-globally to the JSP page.
+globally to the Jakarta Pages (JSP) page.
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
.Example 1 - Input
[cols="20,80",options="header"]
[%breakable]
@@ -998,7 +996,7 @@ globally to the JSP page.
The result is:
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
.Example 1 - Output
[cols="20,80",options="header"]
[%breakable]
@@ -1012,7 +1010,7 @@ The result is:
The next two tables show another example,
with input and output.
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
.Example 2 - Input
[cols="20,80",options="header"]
[%breakable]
@@ -1026,7 +1024,7 @@ with input and output.
The result is:
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
.Example 2 - Output
[cols="20,80",options="header"]
[%breakable]
@@ -1039,18 +1037,17 @@ The result is:
It is possible to have
extraneous whitespaces removed from template text through element
-`trim-directive-whitespaces` of JSP Property Groups (See
+`trim-directive-whitespaces` of Jakarta Pages (JSP) Property Groups (See
<>), or the page and tag file
directive attribute `trimDirectiveWhitespaces` (See
<>, <>).
-[[_JSP_Documents]]
-==== JSP Documents
+==== Jakarta Pages (JSP) Documents
-A JSP page is usually passed directly to a
-JSP container. A JSP document is a JSP page that is also an XML
-document. When a JSP document is encountered by the JSP container, it is
-interpreted as an XML document first and after that as a JSP page. Among
+A Jakarta Pages (JSP) page is usually passed directly to a
+Jakarta Pages (JSP) container. A Jakarta Pages (JSP) document is a Jakarta Pages (JSP) page that is also an XML
+document. When a Jakarta Pages (JSP) document is encountered by the Jakarta Pages (JSP) container, it is
+interpreted as an XML document first and after that as a Jakarta Pages (JSP) page. Among
the consequences of this are:
* The document must be well-formed
@@ -1058,23 +1055,23 @@ the consequences of this are:
* Entity resolution will apply, if indicated
* `<%` style syntax cannot be used
-JSP documents are often a good match for the
+Jakarta Pages (JSP) documents are often a good match for the
generation of dynamic XML content as they can preserve much of the
structure of the generated document.
-The default convention for JSP documents is
+The default convention for Jakarta Pages (JSP) documents is
`.jspx`. There are configuration elements that can be used to indicate
-that a specific file is a JSP document.
+that a specific file is a Jakarta Pages (JSP) document.
-See <> for
-more details on JSP documents, and
-<> for more details on
+See <> for
+more details on Jakarta Pages (JSP) documents, and
+<> for more details on
configuration.
-==== JSP Syntax Grammar
+==== Jakarta Pages (JSP) Syntax Grammar
This section presents a simple EBNF grammar
-for the JSP syntax. The grammar is intended to provide a concise syntax
+for the Jakarta Pages (JSP) syntax. The grammar is intended to provide a concise syntax
overview and to resolve any syntax ambiguities present in this
specification. Other sections may apply further restrictions to this
syntax, for example to restrict what represents a valid attribute value
@@ -1090,8 +1087,7 @@ https://www.w3.org/TR/xml/#sec-notation
In addition, the following notes and rules
apply:
-* The root production for a JSP page is
-`JSPPage`.
+* The root production for a Jakarta Pages (JSP) page is `JSPPage`.
* The prefix `XML::` is used to refer to an
EBNF definition in the XML 1.0 specification. Refer to
`http://www.w3.org/TR/REC-xml`.
@@ -1144,7 +1140,7 @@ match the above:
** `repeat="${ x + y }" name="othername"`
-===== EBNF Grammar for JSP Syntax
+===== EBNF Grammar for Jakarta Pages (JSP) Syntax
[source]
----
@@ -1318,7 +1314,7 @@ XMLExpressionBody ::= ( S? '/>' )
ELExpressionBody ::= ELExpression '}'
|
-ELExpression ::= [See EL spec document, production Expression]
+ELExpression ::= [See EL specification document, production Expression]
ScriptletBody ::= ( Char* - ( Char* '%>' ) ) '%>'
| `
@@ -1535,7 +1531,7 @@ using the syntax `[vc: ValidityConstraint]`, and must be followed:
* `ScriptingEnabled` - The `ScriptlessBody`
production must be followed if scripting is disabled for this
-translation unit. See the `scripting-invalid` JSP Configuration element
+translation unit. See the `scripting-invalid` Jakarta Pages (JSP) Configuration element
(<<_Disabling_Scripting_Elements>>).
* `ScriptlessBody` - The `AllBody`
production cannot be followed if one of the parent nodes in the parse
@@ -1547,15 +1543,15 @@ not followed if expressions are disabled for this translation unit. See
the `isELIgnored` page and tag directive
(See <>) and
<> respectively) and the `el-ignored`
-JSP Configuration element (<<_Deactivating_EL_Evaluation>>).
+Jakarta Pages (JSP) Configuration element (<<_Deactivating_EL_Evaluation>>).
* `TagFileSpecificDirectives` - The
`JSPDirectiveBody` production must be followed if the root production is
-`JSPPage` (i.e. this is a JSP page). The `TagDefDirectiveBody`
+`JSPPage` (i.e. this is a Jakarta Pages (JSP) page). The `TagDefDirectiveBody`
production must be followed if the root production is `JSPTagDef` (i.e.
this is a tag file).
* `TagFileSpecificXMLDirectives` - The
`XMLJSPDirectiveBody` production must be followed if the root production
-is `JSPPage` (i.e. this is a JSP page). The `XMLTagDefDirectiveBody`
+is `JSPPage` (i.e. this is a Jakarta Pages (JSP) page). The `XMLTagDefDirectiveBody`
production must be followed if the root production is `JSPTagDef` (i.e.
this is a tag file).
* `PageDirectiveUniqueAttr` - A translation
@@ -1596,18 +1592,18 @@ directive, or the value of the `name` attribute of an `attribute`
directive in the same translation unit.
* `TagFileSpecificActions` - The `invoke`
and `doBody` standard actions are only matched if the `JSPTagDef`
-production was followed (i.e. if this is a tag file instead of a JSP
+production was followed (i.e. if this is a tag file instead of a Jakarta Pages (JSP)
page).
* `RTAttributeScriptingEnabled` - If the
`RTAttributeValueDouble` or `RTAttributeValueSingle` productions are
visited during parsing and scripting is disabled for this page, a
-translation error must be produced. See the `scripting-invalid` JSP
+translation error must be produced. See the `scripting-invalid` Jakarta Pages (JSP)
Configuration element (<<_Disabling_Scripting_Elements>>).
* `ExpressionBodyContent` - A translation
error will result if the body content minus the closing delimiter (`%>`
, or ``, depending on how the expression started) does
not represent a well-formed expression in the scripting language
-selected for the JSP page.
+selected for the Jakarta Pages (JSP) page.
* `StdActionAttributesValid` - An attribute
is considered “provided” for this standard action if either the
`Attribute` production or the `AttributeBody` production is followed in
@@ -1740,11 +1736,11 @@ are valid. The value in the “Body Production” column specifies a
production name that must be matched for the body of the standard action
to be considered valid. The value in the “Valid Attribute Combinations”
column uses the same syntax as the `attrset` notation described at the
-start of <>, and
+start of <>, and
indicates which attributes can be provided.
[[_Valid_Body_Content_And_Attributes_For_Standard_Actions]]
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
.Valid body content and attributes for Standard Actions
[cols="20,20,60",options="header"]
[%breakable]
@@ -1814,12 +1810,12 @@ compliant implementation.
==== Translation Time Processing Errors
-The translation of a JSP page source into a
-corresponding JSP page implementation class by a JSP container can occur
-at any time between initial deployment of the JSP page into the JSP
+The translation of a Jakarta Pages (JSP) page source into a
+corresponding Jakarta Pages (JSP) page implementation class by a Jakarta Pages (JSP) container can occur
+at any time between initial deployment of the Jakarta Pages (JSP) page into the Jakarta Pages (JSP)
container and the receipt and processing of a client request for the
-target JSP page. If translation occurs prior to the receipt of a client
-request for the target JSP page, error processing and notification is
+target Jakarta Pages (JSP) page. If translation occurs prior to the receipt of a client
+request for the target Jakarta Pages (JSP) page, error processing and notification is
implementation dependent and not covered by this specification. In all
cases, fatal translation failures shall result in the failure of
subsequent client requests for the translation target with the
@@ -1829,25 +1825,25 @@ code `500 (Server Error)` is returned.
==== Request Time Processing Errors
During the processing of client requests,
-errors can occur in either the body of the JSP page implementation
+errors can occur in either the body of the Jakarta Pages (JSP) page implementation
class, or in some other code (Java or other implementation programming
-language) called from the body of the JSP page implementation class.
+language) called from the body of the Jakarta Pages (JSP) page implementation class.
Runtime errors occurring are realized in the page implementation, using
the Java programming language exception mechanism to signal their
occurrence to caller(s) of the offending behavior.
NOTE: This is independent of scripting language. This specification
requires that unhandled errors occurring in a scripting language
-environment used in a JSP container implementation to be signalled to the
-JSP page implementation class via the Java programming language exception
+environment used in a Jakarta Pages (JSP) container implementation to be signalled to the
+Jakarta Pages (JSP) page implementation class via the Java programming language exception
mechanism.
These exceptions may be caught and handled
-(as appropriate) in the body of the JSP page implementation class.
+(as appropriate) in the body of the Jakarta Pages (JSP) page implementation class.
Any uncaught exceptions thrown in the body of
-the JSP page implementation class result in the forwarding of the client
-request and uncaught exception to the errorPage URL specified by the JSP
+the Jakarta Pages (JSP) page implementation class result in the forwarding of the client
+request and uncaught exception to the errorPage URL specified by the Jakarta Pages (JSP)
page (or the implementation default behavior, if none is specified).
Information about the error is passed as
@@ -1855,18 +1851,18 @@ Information about the error is passed as
same attributes as specified by the Servlet specification. Names
starting with the prefixe `jakarta` are reserved by the
different specifications of the Jakarta EE platform. The `jakarta.servlet`
-prefix is reserved and used by the servlet and JSP specifications.
+prefix is reserved and used by the servlet and Jakarta Pages (JSP) specifications.
-==== Using JSPs as Error Pages
+==== Using Jakarta Pages (JSP) as Error Pages
-A JSP is considered an Error Page if it sets
+A Jakarta Pages (JSP) page is considered an Error Page if it sets
the `page` directive’s `isErrorPage` attribute to `true`. If a page has
`isErrorPage` set to `true`, then the “exception” implicit scripting
language variable (see <<_Implicit_Objects_Available_in_Error_Pages>>) of that page is initialized. The variable is
set to the value of the `jakarta.servlet.error.exception request`
attribute value if present, otherwise to the value of the
`jakarta.servlet.jsp.jspException` request attribute value (for backwards
-compatibility for JSP pages pre-compiled with a JSP 1.2 compiler).
+compatibility for Jakarta Pages (JSP) pre-compiled with a JSP 1.2 compiler).
In addition, an `ErrorData` instance must be
initialized based on the error handler `ServletRequest` attributes
@@ -1876,25 +1872,25 @@ to the error information via the Expression Language. For example, an
Error Page can access the status code using the syntax
`${pageContext.errorData.statusCode}`. See the Javadoc for details.
-By default, a JSP error page sets the status
+By default, a Jakarta Pages (JSP) error page sets the status
code of the response to the value of
`${pageContext.errorData.statusCode}` (which is equal to 500 by
default), but may set it to a different value (including 200) as it sees
fit.
-A JSP container must detect if a JSP error
+A Jakarta Pages (JSP) container must detect if a Jakarta Pages (JSP) error
page is self-referencing and throw a translation error.
=== Comments
There are different types of comments
-available in JSP pages in standard syntax and JSP documents (in XML
+available in Jakarta Pages (JSP) in standard syntax and Jakarta Pages (JSP) documents (in XML
syntax).
-==== Comments in JSP Pages in Standard Syntax
+==== Comments in Jakarta Pages (JSP) in Standard Syntax
-There are two types of comments in a JSP
-page: comments to the JSP page itself, documenting what the page is
+There are two types of comments in a Jakarta Pages (JSP)
+page: comments to the Jakarta Pages (JSP) page itself, documenting what the page is
doing; and comments that are intended to appear in the generated
document sent to the client.
@@ -1910,7 +1906,7 @@ comment syntax is used, as follows:
----
These comments are treated as uninterpreted
-template text by the JSP container. Dynamic content that appears within
+template text by the Jakarta Pages (JSP) container. Dynamic content that appears within
HTML/XML comments, such as actions, scriptlets and expressions, is still
processed by the container. If the generated comment is to have dynamic
data, this can be obtained through an expression syntax, as in:
@@ -1920,9 +1916,9 @@ data, this can be obtained through an expression syntax, as in:
----
-===== JSP Comments
+===== Jakarta Pages (JSP) Comments
-A JSP comment is of the form
+A Jakarta Pages (JSP) comment is of the form
[source,jsp]
----
@@ -1931,10 +1927,10 @@ A JSP comment is of the form
The body of the content is ignored
completely. Comments are useful for documentation but also are used to
-“comment out” some portions of a JSP page. Note that JSP comments do not
+“comment out” some portions of a Jakarta Pages (JSP) page. Note that Jakarta Pages (JSP) comments do not
nest.
-An alternative way to place a comment in JSP
+An alternative way to place a comment in Jakarta Pages (JSP)
is to use the comment mechanism of the scripting language. For example:
[source,jsp]
@@ -1942,9 +1938,9 @@ is to use the comment mechanism of the scripting language. For example:
<% /** this is a comment ... **/ %>
----
-==== Comments in JSP Documents
+==== Comments in Jakarta Pages (JSP) Documents
-Comments in JSP documents use the XML syntax,
+Comments in Jakarta Pages (JSP) documents use the XML syntax,
as follows:
[source,jsp]
@@ -1953,18 +1949,18 @@ as follows:
----
The body of the content is ignored
-completely. Comments in JSP documents may be used for documentation
-purposes and for “commenting out” portions of a JSP page.
+completely. Comments in Jakarta Pages (JSP) documents may be used for documentation
+purposes and for “commenting out” portions of a Jakarta Pages (JSP) page.
-Comments in JSP documents do not nest.
+Comments in Jakarta Pages (JSP) documents do not nest.
=== Quoting and Escape Conventions
The following quoting conventions apply to
-JSP pages.
+Jakarta Pages (JSP).
NOTE: The current quoting rules do not allow for quoting special characters
-such as `\n` - the only current way to do this in a JSP is with a Java expression.
+such as `\n` - the only current way to do this in a Jakarta Pages (JSP) is with a Java expression.
_Quoting in EL Expressions_
@@ -2086,19 +2082,19 @@ The next lines are all legal quotations.
_XML Documents_
The quoting conventions are different from
-those of XML. See <>.
+those of XML. See <>.
-=== Overall Semantics of a JSP Page
+=== Overall Semantics of a Jakarta Pages (JSP) Page
-A JSP page implementation class defines a
+A Jakarta Pages (JSP) page implementation class defines a
`_jspService()` method mapping from the request to the response object.
Some details of this transformation are specific to the scripting
language used (see <>). Most details
are not language specific and are described in this chapter.
-The content of a JSP page is devoted largely
+The content of a Jakarta Pages (JSP) page is devoted largely
to describing the data that is written into the output stream of the
-response. (The JSP container usually sends this data back to the
+response. (The Jakarta Pages (JSP) container usually sends this data back to the
client.) The description is based on a `JspWriter` object that is
exposed through the implicit object `out` (see <>).
Its value varies:
@@ -2108,13 +2104,13 @@ object. This object may be different from the stream object returned
from `response.getWriter()`, and may be considered to be interposed on
the latter in order to implement buffering (see <>).
This is the
-initial `out` object. JSP page authors are prohibited from writing
+initial `out` object. Jakarta Pages (JSP) page authors are prohibited from writing
directly to either the `PrintWriter` or `OutputStream` associated with
the `ServletResponse`.
-* The JSP container should not invoke
+* The Jakarta Pages (JSP) container should not invoke
`response.getWriter()` until the time when the first portion of the
content is to be sent to the client. This enables a number of uses of
-JSP, including using JSP as a language to “glue” actions that deliver
+Jakarta Pages (JSP), including using Jakarta Pages (JSP) as a language to “glue” actions that deliver
binary content, or reliably forwarding to a servlet, or change
dynamically the content type of the response before generating content.
See <>.
@@ -2135,15 +2131,15 @@ overflow. If the initial `out` `JspWriter` is unbuffered, then content
written to it will be passed directly through to the `ServletResponse`
output stream.
-A JSP page can also describe what should
-happen when some specific events occur. In JSP 4.1, the only events that
+A Jakarta Pages (JSP) page can also describe what should
+happen when some specific events occur. In Jakarta Pages (JSP) 4.1, the only events that
can be described are the initialization and the destruction of the page.
These events are described using “well-known method names” in
-declaration elements. (See <>).
+declaration elements. (See <>).
=== Objects
-A JSP page can access, create, and modify
+A Jakarta Pages (JSP) page can access, create, and modify
server-side objects. Objects can be made visible to actions, EL
expressions and to scripting elements. An object has a scope describing
what entities can access the object.
@@ -2154,7 +2150,7 @@ the `PageContext` object.
An object exposed through a scripting
variable has a scope within the page. Scripting elements can access some
objects directly via a scripting variable. Some implicit objects are
-visible via scripting variables and EL expressions in any JSP page.
+visible via scripting variables and EL expressions in any Jakarta Pages (JSP) page.
==== Objects and Variables
@@ -2174,13 +2170,13 @@ the JavaScript™ programming language.
The exact rules for the visibility of the
variables are scripting language specific.
-<> defines the rules for when the
+<> defines the rules for when the
`language` attribute of the `page` directive is `java`.
==== Objects and Scopes
-A JSP page can create and/or access some Java
-objects when processing a request. The JSP specification indicates that
+A Jakarta Pages (JSP) page can create and/or access some Java
+objects when processing a request. The Jakarta Pages (JSP) specification indicates that
some objects are created implicitly, perhaps as a result of a directive
(see <>). Other objects
are created explicitly through actions, or created directly using
@@ -2194,14 +2190,14 @@ Each action and declaration defines, as part
of its semantics, what objects it creates, with what scope attribute,
and whether they are available to the scripting elements.
-Objects are created within a JSP page
+Objects are created within a Jakarta Pages (JSP) page
instance that is responding to a request object. There are several
scopes:
* `page` - Objects with `page` scope are
accessible only within the page where 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 forwarded somewhere else.
+the client from the Jakarta Pages (JSP) page or the request is forwarded somewhere else.
References to objects with `page` scope are stored in the `pageContext`
object.
* `request` - Objects with `request` scope
@@ -2229,12 +2225,12 @@ when the runtime environment reclaims the `ServletContext`.
A `name` should refer to a unique object at
all points in the execution; that is, all the different scopes really
-should behave as a single name space. A JSP container implementation may
+should behave as a single name space. A Jakarta Pages (JSP) container implementation may
or may not enforce this rule explicitly for performance reasons.
==== Implicit Objects
-JSP page authors have access to certain
+Jakarta Pages (JSP) page authors have access to certain
implicit objects that are always available for use within scriptlets and
scriptlet expressions through scripting variables that are declared
implicitly at the beginning of the page. All scripting languages are
@@ -2245,11 +2241,11 @@ handlers through the pageContext object, see below.
Each implicit object has a class or interface
type defined in a core Java technology or Jakarta Servlet API package, as
-shown in <<_Implicit_Objects_Available_in_JSP_Pages>>.
+shown in <<_Implicit_Objects_Available_in_Jakarta_Pages>>.
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
-[[_Implicit_Objects_Available_in_JSP_Pages]]
-.Implicit Objects Available in JSP Pages
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
+[[_Implicit_Objects_Available_in_Jakarta_Pages]]
+.Implicit Objects Available in Jakarta Pages (JSP)
[cols="15,45,40",options="header"]
[%breakable]
|===
@@ -2276,7 +2272,7 @@ The request triggering the service invocation. +
|`pageContext`
|`jakarta.servlet.jsp.PageContext`
-|The page context for this JSP page. +
+|The page context for this Jakarta Pages (JSP) page. +
`page` scope.
|`session`
@@ -2301,7 +2297,7 @@ configuration object (as in the call
|`config`
|`jakarta.servlet.ServletConfig`
-|The `ServletConfig` for this JSP page. +
+|The `ServletConfig` for this Jakarta Pages (JSP) page. +
`page` scope.
|`page`
@@ -2320,7 +2316,7 @@ In addition, the `exception` implicit object
can be accessed in an error page, as described in
<<_Implicit_Objects_Available_in_Error_Pages>>.
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[[_Implicit_Objects_Available_in_Error_Pages]]
.Implicit Objects Available in Error Pages
[cols="20,40,40",options="header"]
@@ -2341,7 +2337,7 @@ error page being invoked. +
Object names with prefixes `jsp`, `jsp`,
`jspx` and `jspx`, in any combination of upper and lower case, are
-reserved by the JSP specification.
+reserved by the Jakarta Pages (JSP) specification.
See
<> for some non-normative
@@ -2352,8 +2348,8 @@ conventions for the introduction of new implicit objects.
A `PageContext` is an object that provides a
context to store references to objects used by the page, encapsulates
implementation-dependent features, and provides convenience methods. A
-JSP page implementation class can use a `PageContext` to run unmodified
-in any compliant JSP container while taking advantage of
+Jakarta Pages (JSP) page implementation class can use a `PageContext` to run unmodified
+in any compliant Jakarta Pages (JSP) container while taking advantage of
implementation-specific improvements like high performance `JspWriters`
.
@@ -2368,7 +2364,7 @@ Text is very simple: the template text is passed through to the current
=== Directives
-Directives are messages to the JSP container.
+Directives are messages to the Jakarta Pages (JSP) container.
Directives have this syntax:
[source,jsp]
@@ -2380,7 +2376,7 @@ There may be optional white space after the
`<%@` and before `%>`.
This syntax is easy to type and concise but
-it is not XML-compatible. <>
+it is not XML-compatible. <>
describes equivalent alternative mechanisms that are consistent with XML
syntax.
@@ -2393,13 +2389,13 @@ directive which are described next.
==== The `page` Directive
The `page` directive defines a number of page
-dependent properties and communicates these to the JSP container.
+dependent properties and communicates these to the Jakarta Pages (JSP) container.
This `` element
(<>) describes the same information
following the XML syntax.
-A translation unit (JSP source file and any
+A translation unit (Jakarta Pages (JSP) source file and any
files included via the `include` directive) can contain more than one
instance of the `page` directive, all the attributes will apply to the
complete translation unit (i.e. page directives are position
@@ -2419,7 +2415,7 @@ attribute/value (re)definitions result in a fatal translation error if
the values do not match.
The attribute/value namespace is reserved for
-use by this, and subsequent, JSP specification(s).
+use by this, and subsequent, Jakarta Pages (JSP) specification(s).
Unrecognized attributes or values result in
fatal translation errors.
@@ -2427,11 +2423,11 @@ fatal translation errors.
_Examples_
The following directive provides some
-user-visible information on this JSP page:
+user-visible information on this Jakarta Pages (JSP) page:
[source,jsp]
----
- <%@ page info="my latest JSP Example" %>
+ <%@ page info="my latest Jakarta Pages (JSP) Example" %>
----
The following directive requests no
@@ -2477,7 +2473,7 @@ page_directive_attr_list ::= { language="scriptingLanguage" }
The details of the attributes are as follows:
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
.Page Directive Attributes
[cols="20,80"]
[%breakable]
@@ -2486,9 +2482,9 @@ The details of the attributes are as follows:
|`language`
|Defines the scripting language to be used in
the scriptlets, expression scriptlets, and declarations within the body
-of the translation unit (the JSP page and any files included using the
+of the translation unit (the Jakarta Pages (JSP) page and any files included using the
`include` directive below). +
-In JSP 4.1, the only defined and required
+In Jakarta Pages (JSP) 4.1, the only defined and required
scripting language value for this attribute is `java` (all lowercase,
case-sensitive). +
This specification only describes the
@@ -2500,14 +2496,14 @@ within the translation unit are required to conform to the Java
Programming Language Specification in the way indicated in
<>. +
All scripting languages must provide some
-implicit objects that a JSP page author can use in declarations,
+implicit objects that a Jakarta Pages (JSP) page author can use in declarations,
scriptlets, and expressions. The specific objects that can be used are
defined in <>. +
All scripting languages must support the Java
Runtime Environment (JRE). All scripting languages must expose the Java
technology object model to the script environment, especially implicit
variables, JavaBeans component properties, and public methods. +
-Future versions of the JSP specification may
+Future versions of the Jakarta Pages (JSP) specification may
define additional values for the language attribute and all such values
are reserved. +
It is a fatal translation error for a
@@ -2518,12 +2514,12 @@ Default is `java`.
|`extends`
|The value is a fully qualified Java
programming language class name, that names the superclass of the class
-to which this JSP page is transformed (see <>). +
+to which this Jakarta Pages (JSP) page is transformed (see <>). +
This attribute should not be used without
-careful consideration as it restricts the ability of the JSP container
+careful consideration as it restricts the ability of the Jakarta Pages (JSP) container
to provide specialized superclasses that may improve on the quality of
rendered service. See <> for an
-alternate way to introduce objects into a JSP page that does not have
+alternate way to introduce objects into a Jakarta Pages (JSP) page that does not have
this drawback.
|`import`
@@ -2533,11 +2529,11 @@ import declaration in the Java programming language, a (comma separated)
list of either a fully qualified Java programming language type name
denoting that type, or of a package name followed by the `.\*` string,
denoting all the public types declared in that package. The import list
-shall be imported by the translated JSP page implementation and is thus
+shall be imported by the translated Jakarta Pages (JSP) page implementation and is thus
available to the scripting and EL environments. +
Packages `java.lang.*`, `jakarta.servlet.\*`,
`jakarta.servlet.jsp.*`, and `jakarta.servlet.http.*` are imported implicitly
-by the JSP container. No other packages may be part of this implicitly
+by the Jakarta Pages (JSP) container. No other packages may be part of this implicitly
imported list. Page authors may use the include-prelude feature (see <>) in order
to have additional packages imported transparently into their pages. +
This attribute is currently only defined when
@@ -2551,7 +2547,7 @@ variable named `session` of type `jakarta.servlet.http.HttpSession`
references the current/new session for the page. +
If `false` then the page does not participate
in a session; the `session` implicit variable is unavailable, and any
-reference to it within the body of the JSP page is illegal and shall
+reference to it within the body of the Jakarta Pages (JSP) page is illegal and shall
result in a fatal translation error. +
Default is `true`.
@@ -2570,7 +2566,7 @@ attribute, the contents of this buffer is either automatically flushed,
or an exception is raised, when overflow would occur. +
The default is buffered with an
implementation buffer size of not less than `8kb`. +
-The corresponding JSP configuration element
+The corresponding Jakarta Pages (JSP) configuration element
is buffer (see <>).
|`autoFlush`
@@ -2586,24 +2582,24 @@ incorporated into the translated page, that can subsequently be obtained
from the page’s implementation of `Servlet.getServletInfo` method.
|`isErrorPage`
-|Indicates if the current JSP page is intended
-to be the URL target of another JSP page’s `errorPage`. +
+|Indicates if the current Jakarta Pages (JSP) page is intended
+to be the URL target of another Jakarta Pages (JSP) page’s `errorPage`. +
If `true`, then the implicit script language
variable `exception` is defined and its value is a reference to the
-offending Throwable from the source JSP page in error. +
+offending Throwable from the source Jakarta Pages (JSP) page in error. +
If `false` then the `exception` implicit
variable is unavailable, and any reference to it within the body of the
-JSP page is illegal and shall result in a fatal translation error. +
+Jakarta Pages (JSP) page is illegal and shall result in a fatal translation error. +
Default is `false.`
|`errorPage`
|Defines a URL to 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 provided URL spec is as in
+The provided URL specification is as in
<>. +
-If the URL names another JSP page then, when
-invoked that JSP page’s `exception` implicit script variable shall
+If the URL names another Jakarta Pages (JSP) page then, when
+invoked that Jakarta Pages (JSP) page’s `exception` implicit script variable shall
contain a reference to the originating uncaught `Throwable`. +
The default URL is implementation dependent. +
Note the `Throwable` object is transferred by
@@ -2613,7 +2609,7 @@ the `setAttribute` method, with a name of
`jakarta.servlet.jsp.jspException` (for
backwards-compatibility) and also `jakarta.servlet.error.exception` (for
compatibility with the servlet specification). See
-<> for more
+<> for more
details). +
Note: if `autoFlush=true` then if the
contents of the initial `JspWriter` has been flushed to the
@@ -2625,38 +2621,38 @@ If the page defines an error page via the
|`contentType`
|Defines the MIME type and the character
-encoding for the response of the JSP page, and is also used in
-determining the character encoding of the JSP page. +
+encoding for the response of the Jakarta Pages (JSP) page, and is also used in
+determining the character encoding of the Jakarta Pages (JSP) page. +
Values are either of the form “`TYPE`” or “`TYPE;charset=CHARSET`” with an
optional white space after the “`;`”.
“`TYPE`” is a MIME type, see the IANA registry at
`http://www.iana.org/assignments/media-types/index.html` for useful
values. “`CHARSET`”, if present, must be the IANA name for a character
encoding. +
-The default value for “`TYPE`” is “`text/html`” for JSP pages in standard
+The default value for “`TYPE`” is “`text/html`” for Jakarta Pages (JSP) in standard
syntax, or “`text/xml`” for
-JSP documents in XML syntax. If “`CHARSET`” is not specified, the
+Jakarta Pages (JSP) documents in XML syntax. If “`CHARSET`” is not specified, the
response character encoding is determined as described in
<>. +
-The corresponding JSP configuration element
+The corresponding Jakarta Pages (JSP) configuration element
is default-content-type (see <>). See
<> for complete details on
character encodings.
|`pageEncoding`
-|Describes the character encoding for the JSP
+|Describes the character encoding for the Jakarta Pages (JSP)
page. The value is of the form “`CHARSET`”, which must be the IANA
-name for a character encoding. For JSP pages in standard syntax, the
-character encoding for the JSP page is the charset given by the
+name for a character encoding. For Jakarta Pages (JSP) in standard syntax, the
+character encoding for the Jakarta Pages (JSP) page is the charset given by the
`pageEncoding` attriute if it is present, otherwise the charset given by
the `contentType` attribute if it is present, otherwise “`ISO-8859-1`”. +
-For JSP documents in XML syntax, the
-character encoding for the JSP page is determined as described in
+For Jakarta Pages (JSP) documents in XML syntax, the
+character encoding for the Jakarta Pages (JSP) page is determined as described in
section 4.3.3 and appendix F.1 of the XML specification. The
`pageEncoding` attribute is not needed for such documents. It is a
translation-time error if a document names different encodings in its
XML prolog / text declaration and in the `pageEncoding` attribute. The
-corresponding JSP configuration element is `page-encoding` (see
+corresponding Jakarta Pages (JSP) configuration element is `page-encoding` (see
<>). +
See <> for
complete details on character encodings.
@@ -2667,7 +2663,7 @@ recognized for this page and translation unit. If `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. The corresponding JSP configuration element is `el-ignored`
+attributes. The corresponding Jakarta Pages (JSP) configuration element is `el-ignored`
(see <<_Deactivating_EL_Evaluation>>). The default value
varies depending on the `web.xml` version - see
<>.
@@ -2675,7 +2671,7 @@ varies depending on the `web.xml` version - see
|`errorOnELNotFound`
|Defines whether a `PropertyNotFoundException` is thrown when an EL expression
contains an identifier that the EL machinery cannot resolve. The corresponding
-JSP configuration element is `error-on-el-not-found`
+Jakarta Pages (JSP) configuration element is `error-on-el-not-found`
(see <<_Unknown_EL_Identifiers>>)
|`deferredSyntax-` +
@@ -2684,7 +2680,7 @@ JSP configuration element is `error-on-el-not-found`
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. The
-corresponding JSP configuration element is
+corresponding Jakarta Pages (JSP) configuration element is
`deferred-syntax-allowed-as-literal` (see
<>). See
<> for more information.
@@ -2695,24 +2691,24 @@ corresponding JSP configuration element is
should be handled. If true, template text that contains only whitespaces
is removed from the output. The default is not to trim whitespaces. This
attribute is useful to remove the extraneous whitespaces from the end of
-a directive that is not followed by template text. The corresponding JSP
+a directive that is not followed by template text. The corresponding Jakarta Pages (JSP)
configuration element is `trim-directive-whitespaces` (see
<>). The attribute is ignored by
-JSP documents (XML syntax).
+Jakarta Pages (JSP) documents (XML syntax).
|===
==== The `taglib` Directive
-The set of significant tags a JSP container
+The set of significant tags a Jakarta Pages (JSP) container
interprets can be extended through a tag library.
-The `taglib` directive in a JSP page declares
+The `taglib` directive in a Jakarta Pages (JSP) page declares
that the page uses a tag library, uniquely identifies the tag library
using a URI and associates a tag prefix that will distinguish usage of
the actions in the library.
-If a JSP container implementation cannot
+If a Jakarta Pages (JSP) container implementation cannot
locate a tag library description, a fatal translation error shall
result.
@@ -2721,7 +2717,7 @@ It is a fatal translation error for the
prefix.
A tag library may include a validation method
-that will be consulted to determine if a JSP page is correctly using the
+that will be consulted to determine if a Jakarta Pages (JSP) page is correctly using the
tag library functionality.
See <> for more specification details. And see
@@ -2757,7 +2753,7 @@ _Syntax_
where the attributes are:
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
.{blank}
[cols="20,80"]
[%breakable]
@@ -2794,7 +2790,7 @@ the specification, and must result in a translation error. +
|===
A fatal translation-time error will result if
-the JSP page translator encounters a tag with name `prefix: Name` using
+the Jakarta Pages (JSP) page translator encounters a tag with name `prefix: Name` using
a prefix that is introduced using the taglib directive, and `Name` is
not recognized by the corresponding tag library.
@@ -2802,22 +2798,22 @@ not recognized by the corresponding tag library.
==== The `include` Directive
The `include` directive is used to substitute
-text and/or code at JSP page translation-time. The `<%@ include
+text and/or code at Jakarta Pages (JSP) page translation-time. The `<%@ include
file="relativeURLspec" %>` directive inserts the text of the specified
resource into the page or tag file. The included file is subject to the
-access control available to the JSP container. The `file` attribute is
+access control available to the Jakarta Pages (JSP) container. The `file` attribute is
as in <>.
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
-<>.
+<>.
-A JSP container can include a mechanism for
+A Jakarta Pages (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 4.1 specification does not have
-a way of directing the JSP container that included files have changed.
+recompile the Jakarta Pages (JSP) page. However, the Jakarta Pages (JSP) 4.1 specification does not have
+a way of directing the Jakarta Pages (JSP) container that included files have changed.
The `` element (<>)
describes the same information following the XML syntax.
@@ -2842,11 +2838,11 @@ _Syntax_
==== Implicit Includes
-Many JSP pages start with a list of taglib
+Many Jakarta Pages (JSP) start with a list of taglib
directives that activate the use of tag libraries within the page. In
some cases, these are the only tag libraries that are supposed to be
-used by the JSP page authors. These, and other common conventions are
-greately facilitated by two JSP configuration elements:
+used by the Jakarta Pages (JSP) page authors. These, and other common conventions are
+greately facilitated by two Jakarta Pages (JSP) configuration elements:
`include-prelude` and `include-coda`. A full description of the
mechanism is in <>.
@@ -2854,18 +2850,18 @@ 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
-<>.
+<>.
-==== Including Data in JSP Pages
+==== Including Data in Jakarta Pages (JSP)
Including data is a significant part of the
-tasks in a JSP page. Accordingly, the JSP 4.1 specification has two
+tasks in a Jakarta Pages (JSP) page. Accordingly, the Jakarta Pages (JSP) 4.1 specification has two
include mechanisms suited to different tasks. A summary of their
-semantics is shown in <<_Summary_of_Include_Mechanisms_in_JSP_4.1>>.
+semantics is shown in <<_Summary_of_Include_Mechanisms_in_Jakarta_Pages_4.1>>.
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
-[[_Summary_of_Include_Mechanisms_in_JSP_4.1]]
-.Summary of Include Mechanisms in JSP 4.1
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
+[[_Summary_of_Include_Mechanisms_in_Jakarta_Pages_4.1]]
+.Summary of Include Mechanisms in Jakarta Pages (JSP) 4.1
[cols="28,15,12,25,20",options="header"]
[%breakable]
|===
@@ -2881,7 +2877,7 @@ semantics is shown in <<_Summary_of_Include_Mechanisms_in_JSP_4.1>>.
|`<%@ include file=\... %>`
|file-relative
|static
-|Content is parsed by JSP container.
+|Content is parsed by Jakarta Pages (JSP) container.
|<>
5+^|*Include Action - Request-time*
@@ -2895,36 +2891,36 @@ semantics is shown in <<_Summary_of_Include_Mechanisms_in_JSP_4.1>>.
|===
The Spec column describes what type of
-specification is valid to appear in the given element. The JSP
+specification is valid to appear in the given element. The Jakarta Pages (JSP)
specification requires a relative URL spec. The reference is resolved by
the web/application server and its URL map is involved. Include
-directives are interpreted relative to the current JSP file;
-`jsp:include` actions are interpreted relative to the current JSP page.
+directives are interpreted relative to the current Jakarta Pages (JSP) file;
+`jsp:include` actions are interpreted relative to the current Jakarta Pages (JSP) page.
An include directive regards a resource like
-a JSP page as a static object; i.e. the text in the JSP page is
-included. An include action regards a resource like a JSP page as a
+a Jakarta Pages (JSP) page as a static object; i.e. the text in the Jakarta Pages (JSP) page is
+included. An include action regards a resource like a Jakarta Pages (JSP) page as a
dynamic object; i.e. the request is sent to that object and the result
of processing it is included.
Implicit include directives can also be
requested for a collection of pages through the use of the
-`` and `` elements of the JSP
+`` and `` elements of the Jakarta Pages (JSP)
configuration section of `web.xml`.
For translation-time includes, included
content can use either the same syntax as the including page, or a
-different syntax. For example, a JSP file written in the standard JSP
-syntax can include a JSP file written using the XML syntax. The
+different syntax. For example, a Jakarta Pages (JSP) file written in the standard Jakarta Pages (JSP)
+syntax can include a Jakarta Pages (JSP) file written using the XML syntax. The
following semantics for translation-time includes apply:
-* The JSP container must detect the syntax
-for each JSP file individually and parse each JSP file according to the
+* The Jakarta Pages (JSP) container must detect the syntax
+for each Jakarta Pages (JSP) file individually and parse each Jakarta Pages (JSP) file according to the
syntax in which it is written.
-* A JSP file written using the XML syntax
+* A Jakarta Pages (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.
-* When including a JSP document (written in
+* When including a Jakarta Pages (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
@@ -2936,12 +2932,12 @@ to the `` element of the resulting XML View of the translation
unit.
* 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
+defined in the current scope (by a Jakarta Pages (JSP) segment in either syntax), a
translation error must occur unless that prefix is being redefined to
the same namespace URI.
See <> for
-examples of how these semantics are applied to actual JSP pages and
+examples of how these semantics are applied to actual Jakarta Pages (JSP) and
documents.
==== Additional Directives for Tag Files
@@ -2957,7 +2953,7 @@ and in attribute values. EL expressions are defined in more detail in
<>.
EL expressions can be disabled through the
-use of JSP configuration elements and page directives; see
+use of Jakarta Pages (JSP) configuration elements and page directives; see
<> and
<<_Deactivating_EL_Evaluation>>.
@@ -2986,7 +2982,7 @@ element in the web.xml deployment descriptor (see
There are three other classes of scripting
elements: declarations, scriptlets and expressions. The scripting
language used in the current page is given by the value of the
-`language` directive (see <>). In JSP 4.1, the only
+`language` directive (see <>). In Jakarta Pages (JSP) 4.1, the only
value defined is `java`.
Declarations are used to declare scripting
@@ -2994,12 +2990,12 @@ language constructs that are available to all other scripting elements.
Scriptlets are used to describe actions to be performed in response to
some request. Scriptlets that are program fragments can also be used to
do things like iterations and conditional execution of other elements in
-the JSP page. Expressions are complete expressions in the scripting
+the Jakarta Pages (JSP) page. Expressions are complete expressions in the scripting
language that get evaluated at response time; commonly, the result is
converted into a string and inserted into the output stream.
-All JSP containers must support scripting
-elements based on the Java programming language. Additionally, JSP
+All Jakarta Pages (JSP) containers must support scripting
+elements based on the Java programming language. Additionally, Jakarta Pages (JSP)
containers may also support other scripting languages. All such
scripting languages must support:
@@ -3036,14 +3032,14 @@ scripting elements are described in
==== Declarations
Declarations are used to declare variables
-and methods in the scripting language used in a JSP page. A declaration
+and methods in the scripting language used in a Jakarta Pages (JSP) page. A declaration
must be a complete declarative statement, or sequence thereof, according
to the syntax of the scripting language specified.
Declarations do not produce any output into
the current `out` stream.
-Declarations are initialized when the JSP
+Declarations are initialized when the Jakarta Pages (JSP)
page is initialized and are made available to other declarations,
scriptlets, and expressions.
@@ -3095,7 +3091,7 @@ depends on the code in the scriptlet. Scriptlets can have side-effects,
modifying the objects visible to them.
When all scriptlet fragments in a given
-translation unit are combined in the order they appear in the JSP page,
+translation unit are combined in the order they appear in the Jakarta Pages (JSP) page,
they must yield a valid statement, or sequence of statements, in the
specified scripting language.
@@ -3142,7 +3138,7 @@ _Syntax_
==== Expressions
-An expression element in a JSP page is a
+An expression element in a Jakarta Pages (JSP) page is a
scripting language expression that is evaluated and the result is
coerced to a `String`. The result is subsequently emitted into the
current `out` `JspWriter` object.
@@ -3155,7 +3151,7 @@ the coercion cannot be detected during translation, a
A scripting language may support side-effects
in expressions when the expression is evaluated. Expressions are
-evaluated left-to-right in the JSP page. If an expression appears in
+evaluated left-to-right in the Jakarta Pages (JSP) page. If an expression appears in
more than one run-time attribute, they are evaluated left-to-right in
the tag. An expression might change the value of the `out` object,
although this is not something to be done lightly.
@@ -3192,10 +3188,10 @@ _Syntax_
Actions may affect the current `out` stream
and use, modify and/or create objects. Actions may depend on the details
-of the specific request object received by the JSP page.
+of the specific request object received by the Jakarta Pages (JSP) page.
-The JSP specification includes some actions
-that are standard and must be implemented by all conforming JSP
+The Jakarta Pages (JSP) specification includes some actions
+that are standard and must be implemented by all conforming Jakarta Pages (JSP)
containers; these actions are described in
<>.
@@ -3216,7 +3212,7 @@ may be applicable; the rules for them are described in
<>.
Many values are fixed translation-time
-values, but JSP 4.1 also provides a mechanism for describing values that
+values, but Jakarta Pages (JSP) 4.1 also provides a mechanism for describing values that
are computed at request time, the rules are described in
<>.
@@ -3298,7 +3294,7 @@ in the table.
A conversion failure leads to an error,
whether at translation time or request-time.
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[[_Conversion_from_string_values_to_target_type]]
.Conversions from string values to target type
[cols="20,80",options="header"]
@@ -3381,29 +3377,29 @@ document must be followed.
== Expression Language{counter2:jsp-chapter}
Please consult the Jakarta Expression Language 6.1 specification document
-for details on the Expression Language supported by JSP 4.1.
+for details on the Expression Language supported by Jakarta Pages (JSP) 4.1.
-The addition of the EL to the JSP technology
-facilitates the writing of scriptless JSP pages. These pages can
+The addition of the EL to the Jakarta Pages (JSP) technology
+facilitates the writing of scriptless Jakarta Pages (JSP). These pages can
use EL expressions but can’t use Java scriptlets, Java expressions, or
Java declaration elements. This usage pattern can be enforced through
-the `scripting-invalid` JSP configuration element.
+the `scripting-invalid` Jakarta Pages (JSP) configuration element.
The EL is available in attribute values for
standard and custom actions and within template text.
This chapter describes how the expression
-language is integrated within the JSP 4.1 environment.
+language is integrated within the Jakarta Pages (JSP) 4.1 environment.
-=== Syntax of Expressions in JSP Pages: ${} vs #{}
+=== Syntax of Expressions in Jakarta Pages (JSP): ${} vs #{}
There are two constructs to represent EL
expressions: `${expr}` and `\#{expr}`. While the EL parses and
evaluates `${}` and `#{}` the same way, additional restrictions are
-placed on the usage of these delimiters in JSP pages.
+placed on the usage of these delimiters in Jakarta Pages (JSP).
An EL expression that is evaluated
-immediately is represented in JSP with the syntax `${}`, while an EL
+immediately is represented in Jakarta Pages (JSP) with the syntax `${}`, while an EL
expression whose evaluation is deferred is represented with the syntax
`#{}`.
@@ -3420,8 +3416,8 @@ expressions in template text. A translation error will result if `\#{}`
is used in template text unless `#{}` is turned off via a backwards
compatibility mechanism.
-All EL expressions in JSP template text are
-evaluated as Strings, and are evaluated by the JSP engine immediately
+All EL expressions in Jakarta Pages (JSP) template text are
+evaluated as Strings, and are evaluated by the Jakarta Pages (JSP) engine immediately
when the page response is rendered.
The semantics of an EL expression are the
@@ -3463,7 +3459,7 @@ is less than 3.
----
-Note that the normal JSP coercion mechanism
+Note that the normal Jakarta Pages (JSP) coercion mechanism
already allows for:
[source,jsp]
@@ -3578,7 +3574,7 @@ type=java.lang.ValueExpression`
The following tags would yield the following
results:
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[cols="50,05",options="header"]
[%breakable]
.Examples of Using ${} and #{}
@@ -3620,7 +3616,7 @@ results:
=== Implicit Objects
There are several implicit objects that are
-available to EL expressions used in JSP pages. These objects are always
+available to EL expressions used in Jakarta Pages (JSP). These objects are always
available under these names:
* `pageContext` - the `PageContext` object
@@ -3659,7 +3655,7 @@ initialization parameter names to their `String` parameter value
The following table shows some examples of
using these implicit objects:
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[cols="50,50",options="header"]
[%breakable]
.Examples of Using Implicit Objects
@@ -3689,7 +3685,7 @@ parameter, or `null` if not found
=== Deactivating EL Evaluation
Since the syntactic patterns `${ expr }`
-and `#{ expr }` were not reserved in the JSP specifications before
+and `#{ expr }` were not reserved in the Jakarta Pages (JSP) specifications before
JSP 2.0, there may be situations where such patterns appear but the
intention is not to activate EL expression evaluation but rather to pass
through the pattern verbatim. To address this, the EL evaluation
@@ -3698,7 +3694,7 @@ machinery can be deactivated as indicated in
=== Disabling Scripting Elements
-With the addition of the EL, some JSP page
+With the addition of the EL, some Jakarta Pages (JSP) page
authors, or page authoring groups, may want to follow a methodology
where scripting elements are not allowed. See
<<_Disabling_Scripting_Elements>> for more details.
@@ -3713,7 +3709,7 @@ can be changed as indicated in
=== Invalid EL Expressions
-JSP containers are required to produce a
+Jakarta Pages (JSP) containers are required to produce a
translation error when a syntactically invalid EL expression is
encountered in an attribute value or within template text. The syntax of
an EL expression is described in detail in the EL specification
@@ -3721,23 +3717,23 @@ document.
=== Errors, Warnings, Default Values
-JSP pages are mostly used in presentation,
+Jakarta Pages (JSP) are mostly used in presentation,
and in that usage, experience suggests that it is most important to be
able to provide as good a presentation as possible, even when there are
simple errors in the page. To meet this requirement, the EL does not
provide warnings, just default values and errors. Default values are
type-correct values that are assigned to a subexpression when there is
some problem. An error is an exception thrown (to be handled by the
-standard JSP machinery).
+standard Jakarta Pages (JSP) machinery).
=== Resolution of Variables and their Properties
The EL API provides a generalized mechanism,
-an `ELResolver`, implemented by the JSP container and which defines the
+an `ELResolver`, implemented by the Jakarta Pages (JSP) container and which defines the
rules that govern the resolution of variables and object properties.
-The `ELResolver` shown in <<_JSP_Resolver_Hierarchy>> is passed to
-all EL expressions that appear in a JSP page or tag file. It is an
+The `ELResolver` shown in <<_Jakarta_Pages_Resolver_Hierarchy>> is passed to
+all EL expressions that appear in a Jakarta Pages (JSP) page or tag file. It is an
instance of `jakarta.el.CompositeELResolver` that contains the following
component ``ELResolver``s, in order:
@@ -3779,16 +3775,16 @@ or static import.
. `jsp.NotFoundELResolver` +
Always resolves the requested value, returning `null`
-[[_JSP_Resolver_Hierarchy]]
-.*Figure JSP.2-1* JSP Resolver Hierarchy
+[[_Jakarta_Pages_Resolver_Hierarchy]]
+.*Figure Jakarta Pages (JSP).2-1* Jakarta Pages (JSP) Resolver Hierarchy
image:sp-2.svg[image]
=== Functions
The EL has qualified functions, reusing the
notion of qualification from XML namespaces (and attributes), XSL
-functions, and JSP custom actions. Functions are mapped to public static
-methods in Java classes. In JSP, the map is specified in the TLD.
+functions, and Jakarta Pages (JSP) custom actions. Functions are mapped to public static
+methods in Java classes. In Jakarta Pages (JSP), the map is specified in the TLD.
Function mapping information is bound into
the `ValueExpression` or `MethodExpression` at parse-time and is
@@ -3809,7 +3805,7 @@ The prefix `ns` must match the prefix of a
tag library that contains a function whose name and signature matches
the function being invoked (`f`), or a translation error must occur.
If the prefix is omitted, the tag library associated with the default
-namespace is used (this is only possible in JSP documents).
+namespace is used (this is only possible in Jakarta Pages (JSP) documents).
In the following standard syntax example,
`func1` is associated with `some-taglib` :
@@ -3820,7 +3816,7 @@ In the following standard syntax example,
${some:func1(true)}
----
-In the following JSP document example, both
+In the following Jakarta Pages (JSP) document example, both
`func2` and `func3` are associated with `default-taglib` :
[source,jsp]
@@ -3920,28 +3916,28 @@ to validate functions without a prefix at translation time.
// Table, figure numbering etc
:table-number: 0
-== JSP Configuration{counter2:jsp-chapter}
+== Jakarta Pages (JSP) Configuration{counter2:jsp-chapter}
-This chapter describes the JSP
+This chapter describes the Jakarta Pages (JSP)
configuration information, which is specified in the Web Application
Deployment Descriptor in `WEB-INF/web.xml`. For Servlet 6.2, the Web
Application Deployment Descriptor is defined using XML Schema, and
-imports the elements described in the XML Schema for JSP 4.1 Deployment
-Descriptor. See the XML Schema for the details on how to specify JSP
+imports the elements described in the XML Schema for Jakarta Pages (JSP) 4.1 Deployment
+Descriptor. See the XML Schema for the details on how to specify Jakarta Pages (JSP)
configuration information in a Web Application.
-=== JSP Configuration Information in web.xml
+=== Jakarta Pages (JSP) Configuration Information in web.xml
-A Web Application can include general JSP
+A Web Application can include general Jakarta Pages (JSP)
configuration information in its `web.xml` file that is to be used by
-the JSP container. The information is described through the `jsp-config`
+the Jakarta Pages (JSP) container. The information is described through the `jsp-config`
element and its subelements.
The `jsp-config` element is a subelement of
`web-app` that is used to provide global configuration information
-for the JSP files in a Web Application. A `jsp-config` has two
+for the Jakarta Pages (JSP) files in a Web Application. A `jsp-config` has two
subelements: `taglib` and `jsp-property-group`, defining the taglib
-mapping and groups of JSP files respectively.
+mapping and groups of Jakarta Pages (JSP) files respectively.
=== Taglib Map
@@ -3951,7 +3947,7 @@ elements in the Web Application Deployment descriptor.
The `taglib` element is a subelement of
`jsp-config` that can be used to provide information on a tag library
-that is used by a JSP page within the Web Application. The `taglib`
+that is used by a Jakarta Pages (JSP) page within the Web Application. The `taglib`
element has two subelements: `taglib-uri` and `taglib-location`.
A `taglib-uri` element describes a URI
@@ -3965,26 +3961,26 @@ resource location (as indicated in <>) of
the Tag Library Description File for
the tag library.
-=== JSP Property Groups
+=== Jakarta Pages (JSP) Property Groups
-A JSP property group is a collection of
-properties that apply to a set of files that represent JSP pages. These
+A Jakarta Pages (JSP) property group is a collection of
+properties that apply to a set of files that represent Jakarta Pages (JSP). These
properties are defined in one or more `jsp-property-group` elements in
the Web Application deployment descriptor.
-Most properties defined in a JSP property
-group apply to an entire translation unit, that is, the requested JSP
+Most properties defined in a Jakarta Pages (JSP) property
+group apply to an entire translation unit, that is, the requested Jakarta Pages (JSP)
file that is matched by its URL pattern and all the files it includes
via the include directive. The exceptions are the `page-encoding` and
-`is-xml` properties, which apply separately to each JSP file matched by
+`is-xml` properties, which apply separately to each Jakarta Pages (JSP) file matched by
the URL pattern.
-The applicability of a JSP property group is
+The applicability of a Jakarta Pages (JSP) property group is
defined through one or more URL patterns. URL patterns use the same
syntax as defined in Chapter SRV.12 of the Servlet 6.2 specification,
but are bound at translation time. All the properties in the group apply
to the resources in the Web Application that match any of the URL
-patterns. There is an implicit property: that of being a JSP file. JSP
+patterns. There is an implicit property: that of being a Jakarta Pages (JSP) file. Jakarta Pages (JSP)
Property Groups do not affect tag files.
If a resource matches a URL pattern in both a
@@ -3993,26 +3989,26 @@ most specific applies (following the same rules as in the Servlet
specification). If the URL patterns are identical, the
`` takes precedence over the ``.
If at least one `` contains the most specific
-matching URL pattern, the resource is considered to be a JSP file, and
+matching URL pattern, the resource is considered to be a Jakarta Pages (JSP) file, and
the properties in that `` apply. In addition, if a
-resource is considered to be a JSP file, all `include-prelude` and
+resource is considered to be a Jakarta Pages (JSP) file, all `include-prelude` and
`include-coda` properties apply from all the ``
elements with matching URL patterns (see <>).
-[[_JSP_Property_Groups]]
-==== JSP Property Groups
+[[_Jakarta_Pages_Property_Groups]]
+==== Jakarta Pages (JSP) Property Groups
A `jsp-property-group` is a subelement of
`jsp-config`. The properties that can currently be described in a
`jsp-property-group` include:
-* Indicate that a resource is a JSP file
+* Indicate that a resource is a Jakarta Pages (JSP) file
(implicit).
* Control disabling of EL evaluation.
* Control disabling of Scripting elements.
* Indicate page Encoding information.
* Prelude and Coda automatic includes.
-* Indicate that a resource is a JSP document.
+* Indicate that a resource is a Jakarta Pages (JSP) document.
* Indicate that the deferred syntax
(initiated by the character sequence `#{`) is allowed as a String
literal.
@@ -4021,30 +4017,30 @@ text.
* Indicate response ContentType information.
* Indicate response buffer size.
* Control handling of undeclared namespaces
-in a JSP page.
+in a Jakarta Pages (JSP) page.
[[_Deactivating_EL_Evaluation]]
==== Deactivating EL Evaluation
Since the syntactic pattern `${expr}` was
-not reserved in the JSP specifications before JSP 2.0, and the syntactic
+not reserved in the Jakarta Pages (JSP) specifications before JSP 2.0, and the syntactic
pattern `#{expr}` was not reserved before JSP 2.1, there may be
situations where such patterns appear but the intention is not to
activate EL expression evaluation but rather to pass through the pattern
verbatim. To address this, the EL evaluation machinery can be
deactivated as indicated in this section.
-Each JSP page has a default setting as to
+Each Jakarta Pages (JSP) page has a default setting as to
whether to ignore EL expressions. When ignored, the expression is passed
through verbatim. The default setting does not apply to tag files, which
always default to evaluating expressions.
-The default mode for JSP pages in a Web
+The default mode for Jakarta Pages (JSP) in a Web
Application delivered using a `web.xml` using the Servlet 2.3 or earlier
format is to ignore EL expressions; this provides for backward
compatibility.
-The default mode for JSP pages in a Web
+The default mode for Jakarta Pages (JSP) in a Web
Application delivered using a `web.xml` using the Servlet 2.4 or later format is
to evaluate EL expressions with the ${} syntax. Expressions using the
#{} are evaluated starting with JSP 2.1. See
@@ -4053,11 +4049,11 @@ for more details on the evaluation of #{} expressions.
The default mode can be explicitly changed by
setting the value of the `el-ignored` element. The `el-ignored` element
-is a subelement of `jsp-property-group` (see <<_JSP_Property_Groups>>)
+is a subelement of `jsp-property-group` (see <<_Jakarta_Pages_Property_Groups>>)
It has no subelements. Its valid values are `true` and `false`.
For example, the following `web.xml` fragment
-defines a group that deactivates EL evaluation for all JSP pages
+defines a group that deactivates EL evaluation for all Jakarta Pages (JSP)
delivered using the `.jsp` extension:
[source,xml]
@@ -4073,17 +4069,17 @@ through the `isELIgnored` attribute of the page directive. For tag
files, there is no default, but the `isELIgnored` attribute of the tag
directive can be used to control the EL evaluation settings.
-<<_EL_Evaluation_Settings_for_JSP_Pages>> summarizes the EL evaluation settings for JSP
+<<_EL_Evaluation_Settings_for_Jakarta_Pages>> summarizes the EL evaluation settings for Jakarta Pages (JSP)
pages, and their meanings:
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
-[[_EL_Evaluation_Settings_for_JSP_Pages]]
-.EL Evaluation Settings for JSP Pages
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
+[[_EL_Evaluation_Settings_for_Jakarta_Pages]]
+.EL Evaluation Settings for Jakarta Pages (JSP)
[cols="30,30,40",options="header"]
[%breakable]
|===
-|JSP Configuration
+|Jakarta Pages (JSP) Configuration
|Page Directive isELIgnored
|EL Encountered
@@ -4111,7 +4107,7 @@ pages, and their meanings:
<<_EL_Evaluation_Settings_for_Tag_Files>> summarizes the EL evaluation settings for tag files, and their meanings:
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[[_EL_Evaluation_Settings_for_Tag_Files]]
.EL Evaluation Settings for Tag Files
[cols="50,50",options="header"]
@@ -4134,32 +4130,32 @@ pages, and their meanings:
The EL evaluation setting for a translation
unit also affects whether the `\$` and `\\#` quote sequences are enabled
-for template text and attribute values in a JSP page, document, or tag
+for template text and attribute values in a Jakarta Pages (JSP) page, document, or tag
file. When EL evaluation is disabled, `\$` and `\#` will not be
recognized as quotes, whereas when EL evaluation is enabled, `\$` and
`\\#` will be recognized as quotes for `$` and `#` respectively. See
-<> and <>
+<> and <>
for details.
[[_Disabling_Scripting_Elements]]
==== Disabling Scripting Elements
-With the addition of the EL, some JSP page
+With the addition of the EL, some Jakarta Pages (JSP) page
authors, or page authoring groups, may want to follow a methodology
-where scripting elements are not allowed. Previous versions of JSP
+where scripting elements are not allowed. Previous versions of Jakarta Pages (JSP)
enabled this through the notion of a `TagLibraryValidator` that would
verify that the elements are not present. JSP 2.0 made this slightly
-easier through a JSP configuration element.
+easier through a Jakarta Pages (JSP) configuration element.
The `scripting-invalid` element is a
-subelement of `jsp-property-group` (see <<_JSP_Property_Groups>>). It
+subelement of `jsp-property-group` (see <<_Jakarta_Pages_Property_Groups>>). It
has no subelements. Its valid values are
`true` and `false`. Scripting is enabled by default. Disabling
scripting elements can be done by setting the `scripting-invalid`
-element to `true` in the JSP configuration.
+element to `true` in the Jakarta Pages (JSP) configuration.
For example, the following `web.xml` fragment
-defines a group that disables scripting elements for all JSP pages
+defines a group that disables scripting elements for all Jakarta Pages (JSP)
delivered using the `.jsp` extension:
[source,xml]
@@ -4172,14 +4168,14 @@ delivered using the `.jsp` extension:
<<_Scripting_Settings>> summarizes the scripting settings and their meanings:
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[[_Scripting_Settings]]
.Scripting Settings
[cols="50,50",options="header"]
[%breakable]
|===
-|JSP Configuration
+|Jakarta Pages (JSP) Configuration
|Scripting Encountered
|unspecified
@@ -4203,11 +4199,11 @@ can be changed as indicated in this section.
The default behaviour can be explicitly changed by setting the value of the
`error-on-el-not-found` element. The `error-on-el-not-found` element is a
-subelement of `jsp-property-group` (see <<_JSP_Property_Groups>>)
+subelement of `jsp-property-group` (see <<_Jakarta_Pages_Property_Groups>>)
It has no subelements. Its valid values are `true` and `false`.
For example, the following `web.xml` fragment defines a group that configures
-all JSP pages delivered using the `.jsp` extension to throw a
+all Jakarta Pages (JSP) delivered using the `.jsp` extension to throw a
`PropertyNotFoundException` if an EL expression contains an unknown identifier.:
[source,xml]
@@ -4222,17 +4218,17 @@ Page authors can override the default mode through the `errorOnELNotFound`
attribute of the page directive and the `errorOnELNotFound` attribute of the tag
directive can.
-<<_EL_Unknown_Identifier_Settings_for_JSP_Pages>> summarizes the EL unknown
-identifier settings for JSP pages, and their meanings:
+<<_EL_Unknown_Identifier_Settings_for_Jakarta_Pages>> summarizes the EL unknown
+identifier settings for Jakarta Pages (JSP), and their meanings:
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
-[[_EL_Unknown_Identifier_Settings_for_JSP_Pages]]
-.EL Evaluation Unknown Identifier for JSP Pages
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
+[[_EL_Unknown_Identifier_Settings_for_Jakarta_Pages]]
+.EL Evaluation Unknown Identifier for Jakarta Pages (JSP)
[cols="30,30,40",options="header"]
[%breakable]
|===
-|JSP Configuration
+|Jakarta Pages (JSP) Configuration
|Page Directive errorOnELNotFound
|Unknown Identifier Encountered
@@ -4261,7 +4257,7 @@ identifier settings for JSP pages, and their meanings:
<<_EL_Unknown_Identifier_Settings_for_Tag_Files>> summarizes the EL unknown
identifier settings for tag files, and their meanings:
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[[_EL_Unknown_Identifier_Settings_for_Tag_Files]]
.EL Unknown Identifier Settings for Tag Files
[cols="50,50",options="header"]
@@ -4284,26 +4280,26 @@ identifier settings for tag files, and their meanings:
==== Declaring Page Encodings
-The JSP configuration element `page-encoding`
-can be used to easily set the `pageEncoding` property of a group of JSP
+The Jakarta Pages (JSP) configuration element `page-encoding`
+can be used to easily set the `pageEncoding` property of a group of Jakarta Pages (JSP)
pages defined using the `jsp-property-group` element. This is only
needed for pages in standard syntax, since for documents in XML syntax
the page encoding is determined as described in section 4.3.3 and
appendix F.1 of the XML specification.
The `page-encoding` element is a subelement
-of `jsp-property-group` (see <<_JSP_Property_Groups>>). It has no subelements. Its valid values are those of
+of `jsp-property-group` (see <<_Jakarta_Pages_Property_Groups>>). It has no subelements. Its valid values are those of
the `pageEncoding` page directive. 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 matching the
+directive of a Jakarta Pages (JSP) page and in a Jakarta Pages (JSP) configuration element matching the
page. It is also a translation-time error to name different encodings in
-the prolog / text declaration of the document in XML syntax and in a JSP
+the prolog / text declaration of the document in XML syntax and in a Jakarta Pages (JSP)
configuration element matching the document. It is legal to name the
same encoding through multiple mechanisms.
For example, the following `web.xml` fragment
-defines a group that explicitly assigns `Shift_JIS` to all JSP pages and
-included JSP segments in the `/ja` subdirectory of the web application:
+defines a group that explicitly assigns `Shift_JIS` to all Jakarta Pages (JSP) and
+included Jakarta Pages (JSP) segments in the `/ja` subdirectory of the web application:
[source,xml]
----
@@ -4320,11 +4316,11 @@ subelement of `jsp-property-group`. It has no subelements. Its value is
a context-relative path that must correspond to an element in the Web
Application. When the element is present, the given path will be
automatically included (as in an `include` directive) at the beginning
-of the JSP page in the `jsp-property-group`. When there is more than
+of the Jakarta Pages (JSP) page in the `jsp-property-group`. When there is more than
one `include-prelude` element in a group, they are to be included in the
order they appear. When more than one `jsp-property-group` applies to a
-JSP page, the corresponding include-prelude elements will be processed
-in the same order as they appear in the JSP configuration section of
+Jakarta Pages (JSP) page, the corresponding include-prelude elements will be processed
+in the same order as they appear in the Jakarta Pages (JSP) configuration section of
`web.xml`.
The `include-coda` element is an optional
@@ -4332,16 +4328,16 @@ subelement of `jsp-property-group`. It has no subelements. Its value is
a context-relative path that must correspond to an element in the Web
Application. When the element is present, the given path will be
automatically included (as in an `include` directive) at the end of the
-JSP page in the `jsp-property-group`. When there is more than one
+Jakarta Pages (JSP) page in the `jsp-property-group`. When there is more than one
`include-coda` element in a group, they are to be included in the order
-they appear. When more than one `jsp-property-group` applies to a JSP
+they appear. When more than one `jsp-property-group` applies to a Jakarta Pages (JSP)
page, the corresponding `include-coda` elements will be processed in the
-same order as they appear in the JSP configuration section of `web.xml`
+same order as they appear in the Jakarta Pages (JSP) configuration section of `web.xml`
. Note that these semantics are in contrast to the way `url-pattern` s
are matched for other configuration elements.
Preludes and codas follow the same rules as
-statically included JSP segments. In particular, start tags and end tags
+statically included Jakarta Pages (JSP) segments. In particular, start tags and end tags
must appear in the same file (see <>).
For example, the following `web.xml` fragment
@@ -4369,24 +4365,24 @@ that order, while other `.jsp` files only have
==== Denoting XML Documents
-The JSP configuration element `is-xml` can be
-used to denote that a group of files are JSP documents, and thus must be
+The Jakarta Pages (JSP) configuration element `is-xml` can be
+used to denote that a group of files are Jakarta Pages (JSP) documents, and thus must be
interpreted as XML documents.
The `is-xml` element is a subelement of
-`jsp-property-group` (see <<_JSP_Property_Groups>>). It has no subelements.
+`jsp-property-group` (see <<_Jakarta_Pages_Property_Groups>>). It has no subelements.
Its valid values are `true` and
`false`. When `false`, the files in the associated property group are
-assumed to not be JSP documents, unless there is another property group
-that indicates otherwise. The files are still considered to be JSP pages
+assumed to not be Jakarta Pages (JSP) documents, unless there is another property group
+that indicates otherwise. The files are still considered to be Jakarta Pages (JSP)
due to the implicit property given by the ``
element.
For example, the following `web.xml` fragment
defines two groups. The first one indicates that those files with
-extension `.jspx`, which is the default extension for JSP documents,
-are instead just plain JSP pages. The last group indicates that files
-with extension `.svg` are actually JSP documents (which most likely are
+extension `.jspx`, which is the default extension for Jakarta Pages (JSP) documents,
+are instead just plain Jakarta Pages (JSP). The last group indicates that files
+with extension `.svg` are actually Jakarta Pages (JSP) documents (which most likely are
generating SVG files).
[source,xml]
@@ -4412,11 +4408,11 @@ where jsp-version is 2.1+).
The `deferred-syntax-allowed-as-literal`
element is a subelement of `jsp-property-group` (See
-<<_JSP_Property_Groups>>). It has no
+<<_Jakarta_Pages_Property_Groups>>). It has no
subelements. Its valid values are `true` and `false`, and it is
disabled (`false`) by default. 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
+`deferred-syntax-allowed-as-literal` element to `true` in the Jakarta Pages (JSP)
configuration.
Page authors can override the default value
@@ -4427,7 +4423,7 @@ for more information.
==== Removing Whitespaces from Template Text
-Whitespaces in template text of a JSP page
+Whitespaces in template text of a Jakarta Pages (JSP) page
are preserved by default (See <>). Unfortunately, this means that unwanted extraneous whitespaces
often make it into the response output.
@@ -4447,10 +4443,10 @@ would generate the following output:
Hello World!
-For JSP pages (standard syntax), the JSP
+For Jakarta Pages (JSP) (standard syntax), the Jakarta Pages (JSP)
configuration element `trim-directive-whitespaces` can be used to
indicate that template text containing only whitespaces must be removed
-from the response output. It has no effect on JSP documents (XML
+from the response output. It has no effect on Jakarta Pages (JSP) documents (XML
syntax). In the example above, the first `` represents template text
that contains only whitespaces and would therefore be removed. ``
HelloWorld! `` represents template text that does not contain only
@@ -4460,11 +4456,11 @@ whitespaces and would therefore be preserved as-is.
Hello World!
The `trim-directive-whitespaces` element is a
-subelement of `jsp-property-group` (See <<_JSP_Property_Groups>>). It has
+subelement of `jsp-property-group` (See <<_Jakarta_Pages_Property_Groups>>). It has
no subelements. Its valid values are
`true` and `false`, and it is disabled (`false`) by default. Enabling
the trimming of whitespaces can be done by setting the
-`trim-directive-whitespaces` element to `true` in the JSP configuration.
+`trim-directive-whitespaces` element to `true` in the Jakarta Pages (JSP) configuration.
Page authors can override the default value
through the `trimDirectiveWhitespaces` attribute of the page directive
@@ -4472,9 +4468,9 @@ through the `trimDirectiveWhitespaces` attribute of the page directive
==== Declaring Default Content Type
-The JSP configuration element
+The Jakarta Pages (JSP) configuration element
`default-content-type` can be used to specify the default `contentType`
-property of a group of JSP pages defined using the `jsp-property-group`
+property of a group of Jakarta Pages (JSP) defined using the `jsp-property-group`
element.
The valid values for the `default-content-type`
@@ -4484,9 +4480,9 @@ not include a `contentType` attribute.
==== Setting Default Buffer Size
-The JSP configuration element buffer can be
+The Jakarta Pages (JSP) configuration element buffer can be
used to specify the default buffering model for the initial out
-JspWriter for a group of JSP pages defined using the the
+JspWriter for a group of Jakarta Pages (JSP) defined using the the
jsp-property-group element.
The valid values for the buffer element are
@@ -4497,10 +4493,10 @@ so, the size of the buffer to use.
==== Raising Errors for Undeclared Namespaces
The default behavior when a tag with unknown
-namespace is used in a JSP page is to silently ignore it. For most page
+namespace is used in a Jakarta Pages (JSP) page is to silently ignore it. For most page
authors, this is often a source of errors. To make the mistakes obvious,
-this JSP configuration element can be used to force an error when an
-unknown namespace is used in a JSP page, as is already the case for JSP
+this Jakarta Pages (JSP) configuration element can be used to force an error when an
+unknown namespace is used in a Jakarta Pages (JSP) page, as is already the case for Jakarta Pages (JSP)
documents (XML syntax).
The `error-on-undeclared-namespace` element is
@@ -4509,20 +4505,20 @@ values are `true` and `false`, with false being the default.
If it is set to `true`, then an error must be
raised during the translation time, when an undeclared tag is used in a
-JSP page.
+Jakarta Pages (JSP) page.
=== Backwards Compatibility
==== General
-JSP containers are required to support tag library descriptors from version 2.1 onwards.
-JSP containers are required to support web application descriptors from version 4.0 onwards.
+Jakarta Pages (JSP) containers are required to support tag library descriptors from version 2.1 onwards.
+Jakarta Pages (JSP) containers are required to support web application descriptors from version 4.0 onwards.
-JSP contains may, but are not required, to support earlier versions of these descriptors.
+Jakarta Pages (JSP) containers may, but are not required, to support earlier versions of these descriptors.
==== Backwards Compatibility with JSP 2.0
-This section only applies to JSP containers that opt to support descriptors from Java EE 1.4 onwards.
+This section only applies to Jakarta Pages (JSP) containers that opt to support descriptors from Java EE 1.4 onwards.
As of JSP 2.1, the character sequence `#{` was reserved for EL expressions.
@@ -4531,20 +4527,20 @@ 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.
-When used in template text in a JSP page, the `\#{` character sequence triggers a
+When used in template text in a Jakarta Pages (JSP) page, the `\#{` character sequence triggers a
translation error, unless specifically allowed through a configuration setup. This
-is because the `#{}` syntax is associated exclusively with deferred-evaluation in JSP
+is because the `#{}` syntax is associated exclusively with deferred-evaluation in Jakarta Pages (JSP)
2.1 and does not make sense in the context of template text (only immediate
evaluation using the `${expr}` syntax makes sense in template text).
In a tag file, `\#{expr}` in template text is handled according to the tag file’s
-JSP version. If the tag file’s JSP version is 2.0 or less, `#{expr}` in template
-text will not cause any error. If the tag file’s JSP version is equal to or greater
+Jakarta Pages (JSP) version. If the tag file’s Jakarta Pages (JSP) version is 2.0 or less, `#{expr}` in template
+text will not cause any error. If the tag file’s Jakarta Pages (JSP) version is equal to or greater
than 2.1, `#{expr}` in template text must cause an error, unless it has been
escaped or the tag file contains a `deferredSyntaxAllowedAsLiteral` tag directive
attribute set to `TRUE`.
See <>, and <>,
-for how the JSP version of a tag file is determined.
+for how the Jakarta Pages (JSP) version of a tag file is determined.
// Table, figure numbering etc
@@ -4552,12 +4548,12 @@ for how the JSP version of a tag file is determined.
== Internationalization Issues{counter2:jsp-chapter}
This chapter describes requirements for
-internationalization with Jakarta Server Pages.
+internationalization with Jakarta Pages.
-The JSP specification by itself does not
+The Jakarta Pages (JSP) specification by itself does not
provide a complete platform for internationalization. It is complemented
by functionality provided by the underlying Java
-platform, the Servlet APIs, and by tag libraries such as the JSP
+platform, the Servlet APIs, and by tag libraries such as the Jakarta
Standard Tag Library (JSTL) with its collection of internationalization
and formatting actions. For complete information, see the respective
specifications.
@@ -4575,7 +4571,7 @@ encodings. Any Java runtime must support the Unicode transformations
UTF-8, UTF-16BE, and UTF-16LE as well as the ISO-8859-1 (Latin-1) and
US-ASCII character encodings, but most implementations support many more.
-In JSP pages and in JSP configuration
+In Jakarta Pages (JSP) and in Jakarta Pages (JSP) configuration
elements, character encodings are named using the names defined in the
IANA charset registry:
@@ -4584,29 +4580,29 @@ http://www.iana.org/assignments/character-sets
=== Page Character Encoding
The page character encoding is the character
-encoding in which the JSP page or tag file itself is encoded. The
+encoding in which the Jakarta Pages (JSP) page or tag file itself is encoded. The
character encoding is determined for each file separately, even if one
file includes another using the include directive
(<>). A detailed
-algorithm for determining the page character encoding of a JSP page or
+algorithm for determining the page character encoding of a Jakarta Pages (JSP) page or
tag file can be found in <>.
==== Standard Syntax
-For JSP pages in standard syntax, the page
+For Jakarta Pages (JSP) in standard syntax, the page
character encoding is determined from the following sources:
* A byte order mark (BOM)
-* A JSP configuration element `page-encoding`
+* A Jakarta Pages (JSP) configuration element `page-encoding`
value whose URL pattern matches the page.
* The `pageEncoding` attribute of the `page`
directive of the page. 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 whose URL pattern matches the
+encodings in the `pageEncoding` attribute of the page directive of a Jakarta Pages (JSP)
+page and in a Jakarta Pages (JSP) configuration element whose URL pattern matches the
page.
* 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
+character encoding if neither a Jakarta Pages (JSP) configuration element
`page-encoding` nor the `pageEncoding` attribute are provided.
* If none of the above is provided,
ISO-8859-1 is used as the default character encoding.
@@ -4625,7 +4621,7 @@ byte order and encoding form of unmarked plaintext files.
The exact byte representation of the BOM
depends on the particular encoding of the text file, as follows:
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[cols="50,50",options="header"]
[%breakable]
.Byte representations of the BOM
@@ -4652,7 +4648,7 @@ depends on the particular encoding of the text file, as follows:
|===
The above byte sequences have been reserved
-to identify a BOM at the beginning of JSP pages in standard syntax, and
+to identify a BOM at the beginning of Jakarta Pages (JSP) in standard syntax, and
will not appear in the page's output.
The `pageEncoding` and `contentType`
@@ -4663,59 +4659,59 @@ directive appears at the beginning of the page or tag file and if the
character encoding is an extension of ASCII, that is, if byte values 0
to 127 have the same meaning as in ASCII, at least until the attributes
are found. For character encodings where this is not the case (including
-`UTF-16` and `EBCDIC` -based encodings), the JSP configuration element
+`UTF-16` and `EBCDIC` -based encodings), the Jakarta Pages (JSP) configuration element
`page-encoding` or a BOM should be used.
When using a BOM, it is legal to describe the
-character encoding in a JSP configuration element page-encoding or a
+character encoding in a Jakarta Pages (JSP) configuration element page-encoding or a
pageEncoding attribute of the page directive of the page, as long as
they are consistent.
==== XML Syntax
-For JSP documents and tag files in XML
+For Jakarta Pages (JSP) documents and tag files in XML
syntax, the page character encoding is determined as described in
section 4.3.3 and appendix F.1 of the XML specification.
-For JSP documents in XML syntax, it is legal
-to also describe the character encoding in a JSP configuration element
+For Jakarta Pages (JSP) documents in XML syntax, it is legal
+to also describe the character encoding in a Jakarta Pages (JSP) configuration element
`page-encoding` or a `pageEncoding` attribute of the page directive of
the document, as long as they are consistent. It is a translation-time
error to name different encodings in two or more of the following: the
-XML prolog / text declaration of a JSP document, the `pageEncoding`
-attribute of the page directive of the JSP document, and in a JSP
+XML prolog / text declaration of a Jakarta Pages (JSP) document, the `pageEncoding`
+attribute of the page directive of the Jakarta Pages (JSP) document, and in a Jakarta Pages (JSP)
configuration element whose URL pattern matches the document.
Note that for tag files in XML syntax, it is
illegal for the tag directive to include a pageEncoding attribute: the
encoding is inferred solely by using the conventions for XML documents.
-A JSP container must raise a translation-time
+A Jakarta Pages (JSP) container must raise a translation-time
error if an unsupported page character encoding is requested.
=== Response Character Encoding
The response character encoding is the
-character encoding of the response generated from a JSP page, if that
+character encoding of the response generated from a Jakarta Pages (JSP) page, if that
response is in the form of text. It is primarily managed as the
`jakarta.servlet.ServletResponse` object’s `characterEncoding` property.
-{empty}The JSP container determines an
+{empty}The Jakarta Pages (JSP) container determines an
initial response character encoding along with the initial content type
-for a JSP page and calls `ServletResponse.setContentType()` with this
-information before processing the page. JSP pages can set initial
+for a Jakarta Pages (JSP) page and calls `ServletResponse.setContentType()` with this
+information before processing the page. Jakarta Pages (JSP) can set initial
content type and initial response character encoding using the
-`contentType` attribute of the page directive. The JSP configuration
+`contentType` attribute of the page directive. The Jakarta Pages (JSP) configuration
element default-content-type can also be used to set the default initial
content type and default initial response chrarcter encoding of a group
-of JSP pages using the jsp-property-group element. See
+of Jakarta Pages (JSP) using the jsp-property-group element. See
<>.
The initial response content type is set to
the `TYPE` value of the `contentType` attribute of the page directive.
If the page doesn’t provide this attribute, the initial content type is
-“`text/html`” for JSP pages in standard syntax and “`text/xml`” for
-JSP documents in XML syntax.
+“`text/html`” for Jakarta Pages (JSP) in standard syntax and “`text/xml`” for
+Jakarta Pages (JSP) documents in XML syntax.
The initial response character encoding is
set to the `CHARSET` value of the `contentType` attribute of the page
@@ -4725,9 +4721,9 @@ is determined as follows:
* For documents in XML syntax, it is `UTF-8`
.
-* For JSP pages in standard syntax, it is the
+* For Jakarta Pages (JSP) in standard syntax, it is the
character encoding specified by the BOM, by the `pageEncoding` attribute
-of the page directive, or by a JSP configuration element `page-encoding`
+of the page directive, or by a Jakarta Pages (JSP) configuration element `page-encoding`
whose URL pattern matches the page. Only the character encoding
specified for the requested page is used; the encodings of files
included via the include directive are not taken into consideration. If
@@ -4736,7 +4732,7 @@ passed to `ServletResponse.setContentType()` - the `ServletResponse`
object’s default, `ISO-8859-1`, is used.
After the initial response character encoding
-has been set, the JSP page’s content can dynamically modify it by
+has been set, the Jakarta Pages (JSP) page’s content can dynamically modify it by
calling the `ServletResponse` object’s `setCharacterEncoding` and
`setLocale` methods directly or indirectly. A number of JSTL
internationalization and formatting actions call
@@ -4747,8 +4743,8 @@ Note that the response character encoding can
only be changed until the response is committed. Data is sent to the
response stream on buffer flushes for buffered pages, or on encountering
the first content (beware of whitespace) on unbuffered pages. Whitespace
-is notoriously tricky for JSP Pages in JSP syntax, but much more
-manageable for JSP documents in XML syntax.
+is notoriously tricky for Jakarta Pages (JSP) in standard syntax, but much more
+manageable for Jakarta Pages (JSP) documents in XML syntax.
=== Request Character Encoding
@@ -4757,15 +4753,15 @@ character encoding in which parameters in an incoming request are
interpreted. It is primarily managed as the `ServletRequest` object’s
`characterEncoding` property.
-The JSP specification doesn’t provide
+The Jakarta Pages (JSP) specification doesn’t provide
functionality to handle the request character encoding directly. To
-control the request character encoding from JSP pages without embedded
+control the request character encoding from Jakarta Pages (JSP) without embedded
Java code, the JSTL `` can be used.
=== XML View Character Encoding
The XML view character encoding is the
-character encoding used for externalizing the XML view of a JSP page or
+character encoding used for externalizing the XML view of a Jakarta Pages (JSP) page or
tag file.
The XML view character encoding is always
@@ -4773,16 +4769,16 @@ The XML view character encoding is always
=== Delivering Localized Content
-The JSP specification does not mandate any
+The Jakarta Pages (JSP) specification does not mandate any
specific approach for structuring localized content, and different
approaches are possible. Two common approaches are to use a template
taglib and pull localized strings from a resource repository, or to
-use-per-locale JSP pages. Each approach has benefits and drawbacks. The
+use-per-locale Jakarta Pages (JSP). Each approach has benefits and drawbacks. The
JSTL internationalization and formatting actions provide support for
retrieving localized content from resource bundles and thus support the
-first approach. Some users have been using transformations on JSP
+first approach. Some users have been using transformations on Jakarta Pages (JSP)
documents to do simple replacement of elements by localized strings,
-thus maintaining JSP syntax with no performance cost at run-time.
+thus maintaining Jakarta Pages (JSP) syntax with no performance cost at run-time.
Combinations of these approaches also make sense.
@@ -4791,11 +4787,10 @@ Combinations of these approaches also make sense.
:table-number: 0
== Standard Actions{counter2:jsp-chapter}
-This chapter describes the standard
-actions of Jakarta Server Pages 4.1 (JSP 4.1). Standard actions are
+This chapter describes the standard actions of Jakarta Pages 4.1. Standard actions are
represented using XML elements with a prefix of `jsp` (though that
prefix can be redefined in the XML syntax). A translation error will
-result if the JSP prefix is used for an element that is not a standard
+result if the `jsp` prefix is used for an element that is not a standard
action.
[[jsp:useBean]]
@@ -4818,7 +4813,7 @@ is not found it will attempt to create the object using the other
attributes.
It is also possible to use this action to
-give a local name to an object defined elsewhere, as in another JSP page
+give a local name to an object defined elsewhere, as in another Jakarta Pages (JSP) page
or in a servlet. This can be done by using the `type` attribute and not
providing `class` or `beanName` attributes.
@@ -4841,17 +4836,17 @@ expression.
_The id Attribute_
The `id="name"` attribute/value tuple in a
-`jsp:useBean` action has special meaning to a JSP container, at page
+`jsp:useBean` action has special meaning to a Jakarta Pages (JSP) container, at page
translation time and at client request processing time. In particular:
* the `name` must be unique within the
translation unit, and identifies the particular element in which it
-appears to the JSP container and page.
+appears to the Jakarta Pages (JSP) container and page.
+
Duplicate `id` ’s found in the same
translation unit shall result in a fatal translation error.
-* The JSP container will associate an object
+* The Jakarta Pages (JSP) container will associate an object
(a JavaBean component) with the named value and accessed via that name
in various contexts through the `pagecontext` object described later in
this specification.
@@ -5043,7 +5038,7 @@ The `` tag has the following
attributes:
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[cols="20,80"]
[%breakable]
.jsp:useBean Attributes
@@ -5184,7 +5179,7 @@ The `` action has the
following attributes:
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[cols="20,80"]
[%breakable]
.jsp:setProperty Attributes
@@ -5248,7 +5243,7 @@ obtained from the `pageContext` object through its `findAttribute`
method.
The object named by the name must have been
-“introduced” to the JSP processor using either the `jsp:useBean` action
+“introduced” to the Jakarta Pages (JSP) processor using either the `jsp:useBean` action
or a custom action with an associated `VariableInfo` entry for this
name. If the object was not introduced in this manner, the container
implementation is recommended (but not required) to raise a translation
@@ -5260,7 +5255,7 @@ in, say, the session by a front component are not automatically visible to
jsp:setProperty and jsp:getProperty actions in that page unless a
jsp:useBean action, or some other action, makes them visible.
-If the JSP processor can ascertain that there
+If the Jakarta Pages (JSP) processor can ascertain that there
is an alternate way guaranteed to access the same object, it can use
that information. For example it may use a scripting variable, but it
must guarantee that no intervening code has invalidated the copy held by
@@ -5283,7 +5278,7 @@ _Syntax_
The attributes are:
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[cols="20,80"]
[%breakable]
.jsp:getProperty Attributes
@@ -5302,7 +5297,7 @@ the property is obtained.
A `` action provides for
the inclusion of static and dynamic resources in the same context as the
-current page. See <> for a summary of include facilities.
+current page. See <> for a summary of include facilities.
Inclusion is into the current value of `out`. The resource is specified
using a `relativeURLspec` that is
@@ -5310,8 +5305,8 @@ interpreted in the context of the web application (i.e. it is mapped).
The `page` attribute of both the
`jsp:include` and the `jsp:forward` actions are interpreted relative to
-the current JSP page, while the `file` attribute in an include directive
-is interpreted relative to the current JSP file. See below for some
+the current Jakarta Pages (JSP) page, while the `file` attribute in an include directive
+is interpreted relative to the current Jakarta Pages (JSP) file. See below for some
examples of combinations of this.
An included page cannot change the response
@@ -5324,7 +5319,7 @@ A `jsp:include` action may have `jsp:param`
subelements that can provide values for some parameters in the request
to be used for the inclusion.
-Request processing resumes in the calling JSP
+Request processing resumes in the calling Jakarta Pages (JSP)
page, once the inclusion is completed.
The `flush` attribute controls flushing. If
@@ -5346,7 +5341,7 @@ It is likely a static object, but it could be mapped into, for instance,
a servlet via `web.xml`.
For an example of a more complex set of
-inclusions, consider the following four situations built using four JSP
+inclusions, consider the following four situations built using four Jakarta Pages (JSP)
files: `A.jsp`, `C.jsp`, `dir/B.jsp` and `dir/C.jsp` :
* `A.jsp` says `<%@ include file="dir/B.jsp"%>` and `dir/B.jsp`
@@ -5388,7 +5383,7 @@ used to augment the request for the purposes of the inclusion.
The valid attributes are:
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[cols="20,80"]
[%breakable]
.jsp:include Atrributes
@@ -5397,7 +5392,7 @@ The valid attributes are:
|`page`
|The URL is a relative `urlSpec` as in
<>. Relative
-paths are interpreted relative to the current JSP page. +
+paths are interpreted relative to the current Jakarta Pages (JSP) page. +
Accepts a request-time attribute value (which
must evaluate to a String that is a relative URL specification).
@@ -5412,7 +5407,7 @@ must evaluate to a String that is a relative URL specification).
A `` action
allows the runtime dispatch of the current request to a static resource,
-a JSP page or a servlet in the same context as the current
+a Jakarta Pages (JSP) page or a servlet in the same context as the current
page. A `jsp:forward` effectively terminates the execution of the
current page. The relative `urlSpec` is as in
<>.
@@ -5466,7 +5461,7 @@ This tag allows the page author to cause the
current request processing to be affected by the specified attributes as
follows:
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[cols="20,80"]
[%breakable]
.jsp:forward Attributes
@@ -5475,7 +5470,7 @@ follows:
| `page`
|The URL is a relative `urlSpec` as in
<>.
-Relative paths are interpreted relative to the current JSP page. +
+Relative paths are interpreted relative to the current Jakarta Pages (JSP) page. +
Accepts a request-time attribute value
(which must evaluate to a String that is a relative URL specification).
|===
@@ -5505,7 +5500,7 @@ request shall have `A=bar,foo`. Note that the new `param` has
precedence.
The parameter names and values specified
-should be left unencoded by the page author. The JSP container must
+should be left unencoded by the page author. The Jakarta Pages (JSP) container must
encode the parameter names and values using the character encoding from
the request object when necessary. For example, if the container chooses
to append the parameters to the URL in the dispatched request, both the
@@ -5535,7 +5530,7 @@ The action must only appear as a subelement of a standard or custom
action. An attempt to use it otherwise must result in a translation
error. For example, it cannot be used to specify the value of an
attribute for XML elements that are template text. For custom action
-invocations, JSP containers must support the use of ``
+invocations, Jakarta Pages (JSP) containers must support the use of ``
for both Classic and Simple Tag Handlers.
The behavior of the ``
@@ -5570,7 +5565,7 @@ container must pass in an instance of `String`.
that accept a request-time expression value, the Container must evaluate
the body of the `` action and use the result of this
evaluation as the value of the attribute. The body of the attribute
-action can be any JSP content in this case. If the type of the attribute
+action can be any Jakarta Pages (JSP) content in this case. If the type of the attribute
is not `String`, the standard type conversion rules are applied, as per
<>.
* For standard or custom action attributes
@@ -5629,12 +5624,12 @@ This would produce the following output:
-See <> for the formal syntax definition of the
+See <> for the formal syntax definition of the
`` standard action.
The attributes are:
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[cols="20,80"]
[%breakable]
.Attributes for the `` standard action
@@ -5662,7 +5657,7 @@ generated element.
`false`. If `true`, the whitespace, including spaces, carriage
returns, line feeds, and tabs, that appears at the beginning and at the
end of the body of the `` action will be ignored by the
-JSP compiler. If `false` the whitespace is not ignored. Defaults to
+Jakarta Pages (JSP) compiler. If `false` the whitespace is not ignored. Defaults to
`true`.
|`omit`
@@ -5699,7 +5694,7 @@ The body standard action accepts no attributes.
The `` standard action can only
be used in tag files (see <>),
-and must result in a translation error if used in a JSP. It takes the
+and must result in a translation error if used in a Jakarta Pages (JSP). It takes the
name of an attribute that is a fragment, and invokes the fragment,
sending the output of the result to the `JspWriter`, or to a scoped
attribute that can be examined and manipulated. If the fragment
@@ -5763,12 +5758,12 @@ The following is an example of using `var` or
==== Providing a Fragment Access to Variables
-JSP fragments have access to the same page
+Jakarta Pages (JSP) fragments have access to the same page
scope variables as the page or tag file in which they were defined (in
addition to variables in the request, session, and application scopes).
Tag files have access to a local page scope, separate from the page
scope of the calling page. When a tag file invokes a fragment that
-appears in the calling page, the JSP container provides a way to
+appears in the calling page, the Jakarta Pages (JSP) container provides a way to
synchronize variables between the local page scope in the tag file and
the page scope of the calling page. For each variable that is to be
synchronized, the tag file author must declare the variable with a scope
@@ -5792,12 +5787,12 @@ providing a fragment access to a variable:
A translation error shall result if the
`` action contains a non-empty body.
-See <> for the formal syntax definition of the ``
+See <> for the formal syntax definition of the ``
standard action.
The attributes are:
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[cols="20,80"]
[%breakable]
.Attributes for the `` standard action
@@ -5838,7 +5833,8 @@ calling page does not participate in a session. Defaults to `page`.
===
The `` standard action can
-only be used in tag files (see <>), and must result in a translation error if used in a JSP. It
+only be used in tag files (see <>), and must result in a
+translation error if used in a Jakarta Pages (JSP) page. It
invokes the body of the tag, sending the output of the result to the
`JspWriter`, or to a scoped attribute that can be examined and
manipulated.
@@ -5860,12 +5856,12 @@ handler as a `JspFragment` object.
A translation error shall result if the
`` action contains a non-empty body.
-See <> for the formal syntax definition of the ``
+See <> for the formal syntax definition of the ``
standard action.
The attributes are:
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[cols="20,80"]
[%breakable]
.Attributes for the `` standard action
@@ -5904,7 +5900,7 @@ calling page does not participate in a session. Defaults to `page`.
The `jsp:element` action is used to
dynamically define the value of the tag of an XML element. This action
-can be used in JSP pages, tag files and JSP documents. This action has
+can be used in Jakarta Pages (JSP), tag files and Jakarta Pages (JSP) documents. This action has
an optional body; the body can use the `jsp:attribute and jsp:body
actions.`
@@ -5970,7 +5966,7 @@ be specified using `` This is because ``
has a special meaning when used in the body of ``. See
<> for more details..
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[cols="20,80"]
[%breakable]
.Attributes for the `` standard action
@@ -5978,7 +5974,7 @@ has a special meaning when used in the body of ``. See
|`name`
|(required) The value of name is that of the
-element generated. The name can be a QName; JSP 4.1 places no
+element generated. The name can be a QName; Jakarta Pages (JSP) 4.1 places no
constraints on this value: it is accepted as is. A request-time
attribute value may be used for this attribute.
@@ -5988,7 +5984,7 @@ attribute value may be used for this attribute.
===
A `jsp:text` action can be used to enclose
-template data in a JSP page, a JSP document, or a tag file. A `jsp:text`
+template data in a Jakarta Pages (JSP) page, a Jakarta Pages (JSP) document, or a tag file. A `jsp:text`
action has no attributes and can appear anywhere that template data can.
Its syntax is:
@@ -6004,7 +6000,7 @@ element.
_Examples_
The following example is a fragment that
-could be in both a JSP page or a JSP document.
+could be in both a Jakarta Pages (JSP) page or a Jakarta Pages (JSP) document.
[source,jsp]
----
@@ -6035,10 +6031,10 @@ translation error.
----
-When within a JSP document, of course, the
+When within a Jakarta Pages (JSP) document, of course, the
body content needs to additionally conform to the constraints of being a
well-formed XML document, so the following example, although valid in a
-JSP page is invalid in a JSP document:
+Jakarta Pages (JSP) page is invalid in a Jakarta Pages (JSP) document:
[source,jsp]
----
@@ -6051,7 +6047,7 @@ The same example can be made legal, with no
semantic changes, by using `gt` instead of `>` in the expression; i.e.
`${foo.content gt 3}`.
-In an JSP document, CDATA sections can also
+In an Jakarta Pages (JSP) document, CDATA sections can also
be used to quote, uninterpreted, content, as in the following example:
[source,jsp]
@@ -6079,10 +6075,10 @@ the form:
===
The `jsp:output` action can only be used in
-JSP documents and in tag files in XML syntax, and a translation error
-must result if used in a standard syntax JSP or tag file. This action is
-used to modify some properties of the output of a JSP document or a tag
-file. In JSP 4.1 there are four properties that can be specified, all of
+Jakarta Pages (JSP) documents and in tag files in XML syntax, and a translation error
+must result if used in a standard syntax Jakarta Pages (JSP) page or tag file. This action is
+used to modify some properties of the output of a Jakarta Pages (JSP) document or a tag
+file. In Jakarta Pages (JSP) 4.1 there are four properties that can be specified, all of
which affect the output of the XML prolog.
The `omit-xml-declaration` property allows
@@ -6098,8 +6094,8 @@ the XSLT specification: if a value of "yes" or "true" is given, the
container will not add an XML declaration; if a value of "no" or "false"
is given, the container will add an XML declaration.
-The default value for a JSP document that has
-a `jsp:root` element is "yes". The default value for JSP documents
+The default value for a Jakarta Pages (JSP) document that has
+a `jsp:root` element is "yes". The default value for Jakarta Pages (JSP) documents
without a `jsp:root` element is "no".
The default value for a tag file in XML
@@ -6120,7 +6116,7 @@ The `doctype-root-element`, `doctype-system`
and `doctype-public` properties allow the page author to specify that a
DOCTYPE be automatically generated in the XML prolog of the output.
Without these properties, the DOCTYPE would need to be output manually
-via a `` element before the root element of the JSP document,
+via a `` element before the root element of the Jakarta Pages (JSP) document,
which is inconvenient.
A DOCTYPE must be automatically output if and
@@ -6164,8 +6160,8 @@ as per the XML specification (see
_Examples_
-The following JSP document (with an extension
-of `.jspx` or with `` set to `true` in the JSP configuration):
+The following Jakarta Pages (JSP) document (with an extension
+of `.jspx` or with `` set to `true` in the Jakarta Pages (JSP) configuration):
[source,jsp]
----
@@ -6181,7 +6177,7 @@ generates an XML document as follows:
----
-The following JSP document is like the
+The following Jakarta Pages (JSP) document is like the
previous one, except that the XML declaration is omited. A typical use
would be where the XML fragment is to be included within another
document.
@@ -6196,7 +6192,7 @@ document.
----
-The following JSP document is equivalent but
+The following Jakarta Pages (JSP) document is equivalent but
uses `jsp:root` instead of `jsp:output`.
[source,jsp]
@@ -6207,7 +6203,7 @@ uses `jsp:root` instead of `jsp:output`.
----
-The following JSP document specifies both a
+The following Jakarta Pages (JSP) document specifies both a
`doctype-public` and a `doctype-system` :
[source,jsp]
@@ -6233,7 +6229,7 @@ and generates and XML document as follows:
Example XHTML Document
----
-The following JSP document omits the
+The following Jakarta Pages (JSP) document omits the
`doctype-public` and explicitly omits the XML declaration:
[source,jsp]
@@ -6274,7 +6270,7 @@ doctypeDecl ::= ( doctype-root-element="rootElement"
The following are the valid attributes of
jsp:output:
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[cols="30,70"]
[%breakable]
.Attribute for the `` standard action
@@ -6305,9 +6301,9 @@ generated DOCTYPE.
=== Other Standard Actions
-<> defines several other standard actions that are either
-convenient or needed to describe JSP pages with an XML document, some of
-which are available in all JSP pages. They are:
+<> defines several other standard actions that are either
+convenient or needed to describe Jakarta Pages (JSP) with an XML document, some of
+which are available in all Jakarta Pages (JSP). They are:
* ``, defined in <>.
* ``, defined in <<_Scripting_Elements>>.
@@ -6317,25 +6313,25 @@ which are available in all JSP pages. They are:
// Table, figure numbering etc
:table-number: 0
-[[JSP_Documents]]
-== JSP Documents{counter2:jsp-chapter}
+[[Jakarta_Pages_Documents]]
+== Jakarta Pages (JSP) Documents{counter2:jsp-chapter}
This chapter introduces two concepts
-related to XML and JSP: JSP documents and XML views. This chapter
+related to XML and Jakarta Pages (JSP): Jakarta Pages (JSP) documents and XML views. This chapter
provides a brief overview of the two concepts and their relationship and
-also provides the details of JSP documents. The details of the XML view
-of a JSP document are described in <>.
+also provides the details of Jakarta Pages (JSP) documents. The details of the XML view
+of a Jakarta Pages (JSP) document are described in <>.
-=== Overview of JSP Documents and of XML Views
+=== Overview of Jakarta Pages (JSP) Documents and of XML Views
-A _JSP document_ is a JSP page written using
-XML syntax. JSP documents need to be described as such, either
-implicitly or explicitly, to the JSP container, which will then process
+A _Jakarta Pages (JSP) document_ is a Jakarta Pages (JSP) page written using
+XML syntax. Jakarta Pages (JSP) documents need to be described as such, either
+implicitly or explicitly, to the Jakarta Pages (JSP) container, which will then process
them as XML documents, checking for well-formedness and applying
-requests like entity declarations, if present. JSP documents are used to
-generate dynamic content using the standard JSP semantics.
+requests like entity declarations, if present. Jakarta Pages (JSP) documents are used to
+generate dynamic content using the standard Jakarta Pages (JSP) semantics.
-Here is a simple JSP document:
+Here is a simple Jakarta Pages (JSP) document:
[source,jsp]
----
@@ -6349,132 +6345,132 @@ Here is a simple JSP document:
----
This well-formed, namespace-aware XML
-document generates, using the JSP standard tag library, an XML document
+document generates, using the Jakarta Standard Tag Library, an XML document
that has `` as the root element. That element has 3 ``
subelements containing values `1`, `2` and `3`. See
-<> for more
+<> for more
details of this and other examples.
-The design of JSP documents is focused on the
-generation of dynamic XML content, in any of its many uses, but JSP
+The design of Jakarta Pages (JSP) documents is focused on the
+generation of dynamic XML content, in any of its many uses, but Jakarta Pages (JSP)
documents can be used to generate any dynamic content.
Some of the syntactic elements described in
<> are not
legal XML; this chapter describes alternative syntaxes for those
elements that are aligned with the XML syntax. The alternative syntaxes
-can be used in JSP documents; most of them (`jsp:output` and `jsp:root`
-are exceptions) can also be used in JSP pages in JSP syntax. As it will
+can be used in Jakarta Pages (JSP) documents; most of them (`jsp:output` and `jsp:root`
+are exceptions) can also be used in Jakarta Pages (JSP) in standard syntax. As it will
be described later, the alternative syntax is also used in the XML view
-of JSP pages.
+of Jakarta Pages (JSP).
-JSP documents can be used in a number of
+Jakarta Pages (JSP) documents can be used in a number of
ways, including:
-* JSP documents can be passed directly to the
-JSP container; this is becoming more important as more and more content
+* Jakarta Pages (JSP) documents can be passed directly to the
+Jakarta Pages (JSP) container; this is becoming more important as more and more content
is authored as XML, be it in an XML-based languages like XHTML or SVG,
or for the exchange of documents in applications like Web Services. The
generated content may be sent directly to a client, or it may be part of
some XML processing pipeline.
-* JSP documents can be manipulated by
+* Jakarta Pages (JSP) documents can be manipulated by
XML-aware tools.
-* A JSP document can be generated from a
+* A Jakarta Pages (JSP) document can be generated from a
textual representation by applying an XML transformation, like XSLT.
-* A JSP document can be generated
+* A Jakarta Pages (JSP) document can be generated
automatically, say by serializing some objects.
Tag files can also be authored using XML
-syntax. The rules are very similar to that of JSP documents; see
+syntax. The rules are very similar to that of Jakarta Pages (JSP) documents; see
<> for more details.
-The _XML view of a JSP page_ is an XML
-document that is derived from the JSP page following a mapping defined
-later in this chapter. The XML view of a JSP page is intended to be used
-for validating the JSP page against some description of the set of valid
-pages. Validation of the JSP page is supported in the JSP 4.1
+The _XML view of a Jakarta Pages (JSP) page_ is an XML
+document that is derived from the Jakarta Pages (JSP) page following a mapping defined
+later in this chapter. The XML view of a Jakarta Pages (JSP) page is intended to be used
+for validating the Jakarta Pages (JSP) page against some description of the set of valid
+pages. Validation of the Jakarta Pages (JSP) page is supported in the Jakarta Pages (JSP) 4.1
specification through a `TagLibraryValidator` class associated with a
tag library. The validator class acts on a PageData object that
-represents the XML view of the JSP page (see, for example,
+represents the XML view of the Jakarta Pages (JSP) page (see, for example,
<>)
-<<_Relationship_between_JSP_Pages_and_XML_views_of_JSP_pages>> below depicts the relationship between the concepts of JSP pages, JSP documents and XML
-views. Two phases are involved: the Translation phase, where JSP pages,
+<<_Relationship_between_Jakarta_Pages_and_XML_views_of_Jakarta_Pages>> below depicts the relationship between the concepts of Jakarta Pages (JSP), Jakarta Pages (JSP) documents and XML
+views. Two phases are involved: the Translation phase, where Jakarta Pages (JSP),
in either syntax, are exposed to Tag Library Validators, via their XML
view, and the Request Processing phase, where requests are processed to
produce responses.
-[[_Relationship_between_JSP_Pages_and_XML_views_of_JSP_pages]]
-.*Figure JSP.{jsp-chapter}-1* Relationship between JSP Pages and XML views of JSP pages
+[[_Relationship_between_Jakarta_Pages_and_XML_views_of_Jakarta_Pages]]
+.*Figure Jakarta Pages (JSP).{jsp-chapter}-1* Relationship between Jakarta Pages (JSP) and XML views of Jakarta Pages (JSP)
image:sp-4.svg[image]
-JSP documents are used by JSP page authors.
+Jakarta Pages (JSP) documents are used by Jakarta Pages (JSP) page authors.
They can be authored directly, using a text editor, through an XML
-editing tool, or through a JSP page authoring tool that is aware of the
-XML syntax. Any JSP page author that is generating XML content should
-consider the use of JSP documents. In contrast, the XML view of a JSP
-page is a concept internal to the JSP container and is of interest only
-to Tag Library Authors and to implementors of JSP containers.
+editing tool, or through a Jakarta Pages (JSP) page authoring tool that is aware of the
+XML syntax. Any Jakarta Pages (JSP) page author that is generating XML content should
+consider the use of Jakarta Pages (JSP) documents. In contrast, the XML view of a Jakarta Pages (JSP)
+page is a concept internal to the Jakarta Pages (JSP) container and is of interest only
+to Tag Library Authors and to implementors of Jakarta Pages (JSP) containers.
-=== JSP Documents
+=== Jakarta Pages (JSP) Documents
-A JSP document is a JSP page that is a
-namespace-aware XML document and that is identified as a JSP document to
-the JSP container.
+A Jakarta Pages (JSP) document is a Jakarta Pages (JSP) page that is a
+namespace-aware XML document and that is identified as a Jakarta Pages (JSP) document to
+the Jakarta Pages (JSP) container.
-==== Identifying JSP Documents
+==== Identifying Jakarta Pages (JSP) Documents
-A JSP document can be identified as such in
+A Jakarta Pages (JSP) document can be identified as such in
three ways:
* If there is a `` that
explicitly indicates, through the `` element, whether a given
-file is a JSP document, then that indication overrides any other
+file is a Jakarta Pages (JSP) document, then that indication overrides any other
determination. Otherwise,
* If this web application is using a version 2.4 or later web application
-descriptor, and if the extension is . `jspx`, then the file is a JSP
+descriptor, and if the extension is . `jspx`, then the file is a Jakarta Pages (JSP)
document. Otherwise,
* If the file is explicitly or implicitly
-identified as a JSP page and the top element is a `jsp:root` element
-then the file is identified as a JSP document. This behavior provides
+identified as a Jakarta Pages (JSP) page and the top element is a `jsp:root` element
+then the file is identified as a Jakarta Pages (JSP) document. This behavior provides
backwards compatibility with JSP 1.2.
It is a translation-time error for a file
-that is identified as a JSP document to not be a well-formed,
+that is identified as a Jakarta Pages (JSP) document to not be a well-formed,
namespace-aware, XML document.
See <> for details on identifying tag files in XML syntax.
-==== Overview of Syntax of JSP Documents
+==== Overview of Syntax of Jakarta Pages (JSP) Documents
-A JSP document may or not have a ``
+A Jakarta Pages (JSP) document may or not have a ``
as its top element; `` was mandatory in JSP 1.2, but we expect
-most JSP documents in JSP 4.1 not to use it.
+most Jakarta Pages (JSP) documents in Jakarta Pages (JSP) 4.1 not to use it.
-JSP documents identify standard actions
+Jakarta Pages (JSP) documents identify standard actions
through the use of a well-defined URI in its namespace; although in this
chapter the prefix `jsp` is used for the standard actions, any prefix is
-valid as long as the correct URI identifying JSP 4.1 standard actions is
+valid as long as the correct URI identifying Jakarta Pages (JSP) 4.1 standard actions is
used. Custom actions are identified using the URI that identifies their
tag library; `taglib` directives are not required and cannot appear in a
-JSP document.
+Jakarta Pages (JSP) document.
-A JSP document can use XML elements as
+A Jakarta Pages (JSP) document can use XML elements as
template data; these elements may have qualified names (and thus be in a
namespace), or be unqualified.
The `` element can be used to
define some template data verbatim.
-Since a JSP document must be a valid XML
-document, there are some JSP elements that can’t be used in a JSP
+Since a Jakarta Pages (JSP) document must be a valid XML
+document, there are some Jakarta Pages (JSP) elements that can’t be used in a Jakarta Pages (JSP)
document. The elements that can be used are:
-* JSP directives and scripting elements in
+* Jakarta Pages (JSP) directives and scripting elements in
XML syntax.
* EL expressions in the body of elements and
in attribute values.
-* All JSP standard actions described in
+* All Jakarta Pages (JSP) standard actions described in
<>.
* The jsp:root, jsp:text, and jsp:output
elements.
@@ -6485,15 +6481,15 @@ elements.
fragments.
Scriptlet expressions used to specify
-request-time attribute values use a slightly different syntax in JSP
-documents than in non JSP documents; rather than using `<%= expr %>`,
+request-time attribute values use a slightly different syntax in Jakarta Pages (JSP)
+documents than in non Jakarta Pages (JSP) documents; rather than using `<%= expr %>`,
they use `%= expr %`. The white space around `expr` is not needed, and
note the missing `<` and `>`. The `expr`, after any applicable quoting
as in any other XML document, is an expression to be evaluated as in
<>.
The mechanisms that enable scripting and EL
-evaluation in a JSP page apply also when the page is a JSP document.
+evaluation in a Jakarta Pages (JSP) page apply also when the page is a Jakarta Pages (JSP) document.
Just as in the standard syntax, the `$` in an EL expression can be
quoted using `\$` in both attribute values and template text. Recall,
however, that `\\` is not an escape sequence in XML attributes so
@@ -6501,7 +6497,7 @@ whereas within an attribute in standard syntax `\\${1+1}` would result
in `\2` (assuming EL is enabled) or `\${1+1}` (assuming EL is ignored),
in XML syntax `\\${1+1}` always results in `\${1+1}`.
-It should be noted that the equivalent JSP
+It should be noted that the equivalent Jakarta Pages (JSP)
document form of +
``, where ’a’ is not a custom action, is:
@@ -6511,16 +6507,16 @@ document form of +
]]>
----
-In the JSP document element ``, `"%= url %"` does not represent a request-time attribute value.
That syntax only applies for custom action elements. This is in contrast
to ``, where "`${url}`" represents an EL
-expression in both JSP pages and JSP documents.
+expression in both Jakarta Pages (JSP) and Jakarta Pages (JSP) documents.
==== Semantic Model
-The semantic model of a JSP document is
-unchanged from that of a JSP page in JSP syntax: JSP pages generate a
+The semantic model of a Jakarta Pages (JSP) document is
+unchanged from that of a Jakarta Pages (JSP) page in Jakarta Pages (JSP) syntax: Jakarta Pages (JSP) generate a
response stream of characters from template data and dynamic elements.
Template data can be described explicitly through a `jsp:text` element,
or implicitly through an XML fragment. Dynamic elements are EL
@@ -6529,27 +6525,27 @@ Scripting elements are represented as XML elements with the exception of
request-time attribute expressions, which are represented through
special attribute syntax.
-The first step in processing a JSP document
+The first step in processing a Jakarta Pages (JSP) document
is to process it as an XML document, checking for well-formedness,
processing entity resolution and, if applicable, performing validation
-as described in <>. As part of the processing XML quoting will be performed,
-and JSP quoting will not be performed later.
+as described in <>. As part of the processing XML quoting will be performed,
+and Jakarta Pages (JSP) quoting will not be performed later.
-After these steps, the JSP document will be
-passed to the JSP container which will then interpret it as a JSP page.
+After these steps, the Jakarta Pages (JSP) document will be
+passed to the Jakarta Pages (JSP) container which will then interpret it as a Jakarta Pages (JSP) page.
-The JSP processing step for a JSP document is
-as for any other JSP page except that namespaces are used to identify
+The Jakarta Pages (JSP) processing step for a Jakarta Pages (JSP) document is
+as for any other Jakarta Pages (JSP) page except that namespaces are used to identify
standard actions and custom action tag libraries and that run time
expressions in attributes use the slightly different syntax. Note that
-all the JSP elements that are described in this chapter are valid in all
-JSP pages, be they identified as JSP documents or not. This is a
+all the Jakarta Pages (JSP) elements that are described in this chapter are valid in all
+Jakarta Pages (JSP), be they identified as Jakarta Pages (JSP) documents or not. This is a
backward compatible change from the behavior in JSP 1.2 to enable
-gradual introduction of XML syntax in existing JSP pages.
+gradual introduction of XML syntax in existing Jakarta Pages (JSP).
To clearly explain the processing of
whitespace, we follow the structure of the XSLT specification. The first
-step in processing a JSP document is to identify the nodes of the
+step in processing a Jakarta Pages (JSP) document is to identify the nodes of the
document. Then, all textual nodes that have only white space are dropped
from the document; the only exception are nodes in a `jsp:text` element,
which are kept verbatim. The resulting nodes are interpreted as
@@ -6565,22 +6561,22 @@ The container will add, in some conditions,
an XML declaration to the output; the rules for this depend on the use
of jsp:root and jsp:output; see <>.
-==== JSP Document Validation
+==== Jakarta Pages (JSP) Document Validation
-A JSP document with a DOCTYPE declaration
+A Jakarta Pages (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 <>.
-JSP 4.1 requires only DTD validation for JSP
+Jakarta Pages (JSP) 4.1 requires only DTD validation for Jakarta Pages (JSP)
Documents; containers should not perform validation based on other types
of schemas, such as XML schema.
-If an author wishes to have the JSP document
+If an author wishes to have the Jakarta Pages (JSP) document
framed by the root element of a vocabulary outside the
http://java.sun.com/JSP/Page namespace, and they wish to be able to
-validate the JSP document according to a DTD, then they should be aware
-that the DTD must make explicit provision for elements from the JSP
+validate the Jakarta Pages (JSP) document according to a DTD, then they should be aware
+that the DTD must make explicit provision for elements from the Jakarta Pages (JSP)
namespace, and the namespace prefix to which they are bound.
For example, the following XML document:
@@ -6599,23 +6595,23 @@ on the root element, and also for elements with a "jsp" namespace
prefix. Even if the DTD provides for this, you must bind the
namespace to the prefix that the DTD has chosen.
-=== Syntactic Elements in JSP Documents
+=== Syntactic Elements in Jakarta Pages (JSP) Documents
-This section describes the elements in a JSP
+This section describes the elements in a Jakarta Pages (JSP)
document.
[[Namespaces_Standard_Actions_and_Tag_Libraries]]
==== Namespaces, Standard Actions, and Tag Libraries
-JSP documents and tag files in XML syntax use
+Jakarta Pages (JSP) documents and tag files in XML syntax use
XML namespaces to identify the standard actions, the directives, and the
-custom actions. JSP pages and tags in the JSP syntax cannot use XML
+custom actions. Jakarta Pages (JSP) and tags in the standard syntax cannot use XML
namespaces and instead must use the taglib directive.
Though the prefix "`jsp`" is used
throughout this specification, it is the namespace
`http://java.sun.com/JSP/Page` and not the prefix "`jsp`" that
-identifies the JSP standard actions.
+identifies the Jakarta Pages (JSP) standard actions.
An `xmlns` attribute for a custom tag library
of the form _xml:prefix='uri'_ identifies the tag library through the
@@ -6644,12 +6640,12 @@ uninterpreted.
==== The jsp:root Element
The `jsp:root` element can only appear as the
-root element in a JSP document or in a tag file in XML syntax; otherwise
-a translation error shall occur. JSP documents and tag files in XML
+root element in a Jakarta Pages (JSP) document or in a tag file in XML syntax; otherwise
+a translation error shall occur. Jakarta Pages (JSP) documents and tag files in XML
syntax need not have a `jsp:root` element as its root element.
The `jsp:root` element has two main uses. One
-is to indicate that the JSP file is in XML syntax, without having to use
+is to indicate that the Jakarta Pages (JSP) file is in XML syntax, without having to use
configuration group elements nor using the .jspx extension. The other
use of the `jsp:root` element is to accomodate the generation of content
that is not a single XML document: either a sequence of XML documents or
@@ -6658,12 +6654,12 @@ some non-XML content.
A `jsp:root` element can be used to provide
zero or more `xmlns` attributes that correspond to namespaces for the
standard actions, for custom actions or for generated template text.
-Unlike in JSP 1.2, not all tag libraries used within the JSP document
+Unlike in JSP 1.2, not all tag libraries used within the Jakarta Pages (JSP) document
need to be introduced on the root; tag libraries can be incorporated as
needed inside the document using additional `xmlns` attributes.
The jsp:root element has one mandatory
-element, the version of the JSP spec that the page is using.
+element, the version of the Jakarta Pages (JSP) specification that the page is using.
When `jsp:root` is used, the container will,
by default, not insert an XML declaration; the default can be changed
@@ -6707,17 +6703,17 @@ element.
----
The one valid, mandatory, attribute of
-jsp:root is the version of the JSP specification used:
+jsp:root is the version of the Jakarta Pages (JSP) specification used:
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[cols="20,80"]
[%breakable]
.Attributes for the `` standard action
|===
|`version`
-|(required) The version of the JSP specification used in this page.
+|(required) The version of the Jakarta Pages (JSP) specification used in this page.
Valid values are "1.2", "2.0", "2.1", "2.2", "2.3", "3.0", "3.1", "4.0" and "4.1".
It is a translation error if the container does not support the specified version.
@@ -6725,14 +6721,14 @@ It is a translation error if the container does not support the specified versio
==== The jsp:output Element
-The jsp:output element can be used in JSP
+The jsp:output element can be used in Jakarta Pages (JSP)
documents and in tag files in XML syntax. The jsp:output element is
described in detail in <>.
==== The jsp:directive.page Element
The `jsp:directive.page` element defines a
-number of page dependent properties and communicates these to the JSP
+number of page dependent properties and communicates these to the Jakarta Pages (JSP)
container. This element must be a child of the root element. Its syntax
is:
@@ -6746,13 +6742,13 @@ described in <>.
The interpretation of a `jsp:directive.page`
element is as described in <>, and its scope is the
-JSP document and any fragments included through an include directive.
+Jakarta Pages (JSP) document and any fragments included through an include directive.
==== The jsp:directive.include Element
The `jsp:directive.include` element is used to
-substitute text and/or code at JSP page translation-time. This element
-can appear anywhere within a JSP document. Its syntax is:
+substitute text and/or code at Jakarta Pages (JSP) page translation-time. This element
+can appear anywhere within a Jakarta Pages (JSP) document. Its syntax is:
[source,jsp]
----
@@ -6762,7 +6758,7 @@ can appear anywhere within a JSP document. Its syntax is:
The interpretation of a
`jsp:directive.include` element is as in <>.
-The XML view of a JSP page does not contain
+The XML view of a Jakarta Pages (JSP) page does not contain
`jsp:directive.include` elements, rather the included file is expanded
in-place. This is done to simplify validation.
@@ -6779,8 +6775,8 @@ XML view (see <<_The_tag_Directive>>,
==== Scripting Elements
The usual scripting elements: declarations,
-scriptlets and expressions, can be used in JSP documents, but the only
-valid forms for these elements in a JSP document are the XML syntaxes;
+scriptlets and expressions, can be used in Jakarta Pages (JSP) documents, but the only
+valid forms for these elements in a Jakarta Pages (JSP) document are the XML syntaxes;
i.e. those using the elements `jsp:declaration`, `jsp:scriptlet` and
`jsp:expression`.
@@ -6823,17 +6819,17 @@ syntax is:
The standard actions of
<> use a syntax that is
-consistent with XML syntax and they can be used in JSP documents and in
+consistent with XML syntax and they can be used in Jakarta Pages (JSP) documents and in
tag files in XML syntax.
==== Template Content
-A JSP page has no structure on its template
+A Jakarta Pages (JSP) page has no structure on its template
content, and, correspondingly, imposes no constraints on that content.
-On the other hand, JSP documents have structure and some constraints are
+On the other hand, Jakarta Pages (JSP) documents have structure and some constraints are
needed.
-JSP documents can generate unconstrained
+Jakarta Pages (JSP) documents can generate unconstrained
content using `jsp:text`, as defined in <>. `jsp:text` can be used to generate totally fixed content but
it can also be used to generate some dynamic content, as described in
<> below.
@@ -6841,15 +6837,15 @@ it can also be used to generate some dynamic content, as described in
Fixed structured content can be generated
using XML fragments. A template XML element, an element that represents
neither a standard action nor a custom action, can appear anywhere where
-a `jsp:text` may appear in a JSP document. The interpretation of such an
+a `jsp:text` may appear in a Jakarta Pages (JSP) document. The interpretation of such an
XML element is to pass its textual representation to the current value
of `out`, after the whitespace processing described in
<>.
For example, if the variable i has the value
-3, and the JSP document is of the form. :
+3, and the Jakarta Pages (JSP) document is of the form:
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[cols="20,80",options="header"]
[%breakable]
.Example 1 - Input
@@ -6880,7 +6876,7 @@ For example, if the variable i has the value
The result is:
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[cols="20,80",options="header"]
[%breakable]
.Example 1 - Output
@@ -6900,7 +6896,7 @@ The result is:
==== Dynamic Template Content
Custom actions can be used to generate any
-content, both structured and unstructured. Future versions of the JSP
+content, both structured and unstructured. Future versions of the Jakarta Pages (JSP)
specification may allow for custom actions to check constraints on the
generated content (see <>) but the current specification has no standards
support for any such constraints.
@@ -6923,7 +6919,7 @@ Further details of jsp:element, jsp:attribute and jsp:body are given in
In some cases, the dynamic content that is
generated can be described as simple substitutions on otherwise static
-templates. JSP documents can have XML templates where EL expressions are
+templates. Jakarta Pages (JSP) documents can have XML templates where EL expressions are
used as the values of the body or of attributes. For instance, the next
example uses the expression `table.indent` as the value of an attribute,
and the expression `table.value` as that for the body of an element:
@@ -6935,16 +6931,16 @@ and the expression `table.value` as that for the body of an element:
----
-=== Examples of JSP Documents
+=== Examples of Jakarta Pages (JSP) Documents
The following sections provide several
-annotated examples of JSP documents.
+annotated examples of Jakarta Pages (JSP) documents.
-==== Example: A Simple JSP Document
+==== Example: A Simple Jakarta Pages (JSP) Document
-This simple JSP document generates a table
-with 3 rows with numeric values 1, 2, 3. The JSP document uses template
-XML elements intermixed with actions from the JSP Standard Tag Library.
+This simple Jakarta Pages (JSP) document generates a table
+with 3 rows with numeric values 1, 2, 3. The Jakarta Pages (JSP) document uses template
+XML elements intermixed with actions from the Jakarta Standard Tag Library.
[source,jsp]
----
@@ -6961,7 +6957,7 @@ Some comments:
* The XML template elements are and
. The custom action element is
-* The JSP standard tag library is introduced
+* The Jakarta Standard Tag Library is introduced
through the use of its URI namespace and the specific prefix used, c in
this case, is irrelevant. The prefix is introduced in a non-root
element, and the top element of the document is still .
@@ -6971,13 +6967,13 @@ the template element.
equally good, but an expression is used for expository reasons) is used
within the value of an attribute in both the XML template element
and in the custom action element .
-* The JSP document does not have an xml
+* The Jakarta Pages (JSP) document does not have an xml
declaration - we are assuming the encoding of the file did not require
it, e.g. it used UTF-8, - but the output will include an xml declaration
due to the defaulting rules and to the absence of jsp:output element
directing the container to do otherwise.
-The JSP document above does not generate an
+The Jakarta Pages (JSP) document above does not generate an
XML document that uses namespaces, but the next example does.
==== Example: Generating Namespace-aware Documents
@@ -7002,10 +6998,10 @@ element The namespace applies to the unqualified elements: and
custom action, then the elements so effected would be interpreted as
invocations on custom actions or tags.
-Although the JSP container understands that
-this document is a namespace-aware document, the JSP 4.1 container does
+Although the Jakarta Pages (JSP) container understands that
+this document is a namespace-aware document, the Jakarta Pages (JSP) 4.1 container does
not really understand that the generated content is a well-formed XML
-document and, as the next example shows, a JSP document can generate
+document and, as the next example shows, a Jakarta Pages (JSP) document can generate
other types of content.
==== Example: Generating non-XML documents
@@ -7025,14 +7021,14 @@ other types of content.
This example just generates 123. There is no
xml declaration generated because there is no element to
-modify the default rule for when a JSP document has . No
+modify the default rule for when a Jakarta Pages (JSP) document has . No
additional whitespace is introduced because there is none within the
element.
-The previous example used elements in the JSP
-namespace. That example used the jsp prefix, but, unlike with JSP pages
-in JSP syntax, the name of the prefix is irrelevant (although highly
-convenient) in JSP documents: the JSP URI is the only important
+The previous example used elements in the Jakarta Pages (JSP)
+namespace. That example used the jsp prefix, but, unlike with Jakarta Pages (JSP)
+in standard syntax, the name of the prefix is irrelevant (although highly
+convenient) in Jakarta Pages (JSP) documents: the Jakarta Pages (JSP) URI is the only important
indicative and the corrent URI should be used, and introduced via a
namespace attribute.
@@ -7054,7 +7050,7 @@ generated with the following modification of the previous example:
On the other hand, although the following
example uses the jsp prefix the URI used in the namespace attribute is
-not the JSP URI and the JSP document will generate as output an XML
+not the Jakarta Pages (JSP) URI and the Jakarta Pages (JSP) document will generate as output an XML
document with root using the URI
`http://johnsonshippingproducts.com`.
@@ -7071,14 +7067,14 @@ document with root using the URI
----
-Finally, note that, since a JSP document is a
+Finally, note that, since a Jakarta Pages (JSP) document is a
well-formed, namespace-aware document, prefixes, including jsp cannot be
used without being introduced through a namespace attribute.
==== Example: Using Custom Actions and Tag Files
Custom actions are frequently used within a
-JSP document to generate portions of XML content. The JSP specification
+Jakarta Pages (JSP) document to generate portions of XML content. The Jakarta Pages (JSP) specification
treats this content as plain text, with no intepretation nor constraints
imposed on it. Good practice, though, suggests abstractions that
organize the content along well-formed fragments.
@@ -7141,7 +7137,7 @@ where pageCharSet is a variable with a value as iso-8859-1.
----
-Note that this tag is a JSP document (because
+Note that this tag is a Jakarta Pages (JSP) document (because
of the jsp:root declaration), and, as such, it is validated by the
container. Also note that the content that is generated in this case is
not using QNames, which means that the interpretation of the generated
@@ -7149,35 +7145,35 @@ elements can be ’captured’ based on the invocation context. That is the
case here, as there is a default namespace active (that of XHTML) where
the tag is being invoked.
-=== Possible Future Directions for JSP documents
+=== Possible Future Directions for Jakarta Pages (JSP) Documents
This section is non-normative. Two features
are sketched briefly here to elicit input that could be used on future
-versions of the JSP specification.
+versions of the Jakarta Pages (JSP) specification.
==== Generating XML Content Natively
-All JSP 4.1 content is textual, even when
-using JSP documents to generate XML content. This is quite acceptable,
+All Jakarta Pages (JSP) 4.1 content is textual, even when
+using Jakarta Pages (JSP) documents to generate XML content. This is quite acceptable,
and even ideal, for some applications, but in some other applications
XML documents are the main data type being manipulated. For example, the
data source may be an XML document repository, perhaps queried using
-XQuery, some of the manipulation on this data internal to the JSP page
+XQuery, some of the manipulation on this data internal to the Jakarta Pages (JSP) page
will use XML concepts (XPath, XSTL operations), and the generated XML
document may be part of some XML pipeline.
In one such application, it is appealing not
to transform back and forth between a stream of characters (text) and a
-parsed representation of the XML document. The JSP expert group has
+parsed representation of the XML document. The Jakarta Pages (JSP) expert group has
explored different approaches on how such XML-awareness could be added,
-and a future version of JSP could support this functionality.
+and a future version of Jakarta Pages (JSP) could support this functionality.
==== Schema and XInclude Support
The current specification only requires DTD
-validation support for JSP documents. A more flexible schema language,
+validation support for Jakarta Pages (JSP) documents. A more flexible schema language,
like XML Schema, could be useful and could be explored by a future
-version of the JSP specification.
+version of the Jakarta Pages (JSP) specification.
Similarly, future versions of the
specification may also consider support for XInclude.
@@ -7187,12 +7183,12 @@ specification may also consider support for XInclude.
== Tag Extensions{counter2:jsp-chapter}
This chapter describes the tag library
-facility for introducing new actions into a JSP page. The tag library
+facility for introducing new actions into a Jakarta Pages (JSP) page. The tag library
facility includes portable run-time support, a validation mechanism, and
authoring tool support. Both the classic JSP 1.2 style tag extension
mechanism and the newer JSP 2.0 onwards simple tag extension mechanism are
described. In <>, a mechanism
-for authoring tag extensions using only JSP syntax is described. This
+for authoring tag extensions using only Jakarta Pages (JSP) syntax is described. This
brings the power of tag extensions to page authors that may not know the
Java programming language.
@@ -7204,45 +7200,45 @@ found in the `jakarta.servlet.jsp.tagext` Javadoc.
=== Introduction
A Tag Library abstracts functionality used by
-a JSP page by defining a specialized (sub)language that enables a more
-natural use of that functionality within JSP pages.
+a Jakarta Pages (JSP) page by defining a specialized (sub)language that enables a more
+natural use of that functionality within Jakarta Pages (JSP).
The actions introduced by the Tag Library can
-be used by the JSP page author in JSP pages explicitly, when authoring
+be used by the Jakarta Pages (JSP) page author in Jakarta Pages (JSP) explicitly, when authoring
the page manually, or implicitly, when using an authoring tool. Tag
Libraries are particularly useful to authoring tools because they make
intent explicit and the parameters expressed in the action instance
provide information to the tool.
Actions that are delivered as tag libraries
-are imported into a JSP page using the `taglib` directive. They are
+are imported into a Jakarta Pages (JSP) page using the `taglib` directive. They are
available for use in the page using the prefix given by the directive.
An action can create new objects that can be passed to other actions, or
can be manipulated programmatically through a scripting element in the
-JSP page.
+Jakarta Pages (JSP) page.
The semantics of a specific custom action in
a tag library is described via a tag handler class which is usually
-instantiated at runtime by the JSP page implementation class. When the
-tag library is well known to the JSP container
+instantiated at runtime by the Jakarta Pages (JSP) page implementation class. When the
+tag library is well known to the Jakarta Pages (JSP) container
(<>), the Container can
use alternative implementations as long as the semantics are preserved.
Tag libraries are portable: they can be used
-in any legal JSP page regardless of the scripting language used in that
+in any legal Jakarta Pages (JSP) page regardless of the scripting language used in that
page.
The tag extension mechanism includes
information to:
-* Execute a JSP page that uses the tag
+* Execute a Jakarta Pages (JSP) page that uses the tag
library.
-* Author or modify a JSP page.
-* Validate the JSP page.
-* Present the JSP page to the end user.
+* Author or modify a Jakarta Pages (JSP) page.
+* Validate the Jakarta Pages (JSP) page.
+* Present the Jakarta Pages (JSP) page to the end user.
A Tag Library is described via the Tag
-Library Descriptor ( TLD), an XML document that is described below.
+Library Descriptor (TLD), an XML document that is described below.
==== Goals
@@ -7250,16 +7246,16 @@ The tag extension mechanism described in this
chapter addresses the following goals. It is designed to be:
* _Portable_ - An action described in a tag
-library must be usable in any JSP container.
+library must be usable in any Jakarta Pages (JSP) container.
* _Simple_ - Unsophisticated users must be
-able to understand and use this mechanism. Vendors of JSP functionality
+able to understand and use this mechanism. Vendors of Jakarta Pages (JSP) functionality
must find it easy to make it available to users as actions.
* _Expressive_ - The mechanism must support
a wide range of actions, including nested actions, scripting elements
inside action bodies, and creation, use, and updating of scripting
variables.
* _Usable from different scripting
-languages_ - Although the JSP specification currently only defines the
+languages_ - Although the Jakarta Pages (JSP) specification currently only defines the
semantics for scripts in the Java programming language, we want to leave
open the possibility of other scripting languages.
* _Built upon existing concepts and
@@ -7269,21 +7265,21 @@ want to avoid future conflicts whenever we can predict them.
[[_Overview]]
==== Overview
-The processing of a JSP page conceptually
+The processing of a Jakarta Pages (JSP) page conceptually
follows these steps:
_Parsing_
-JSP pages can be authored using two different
-syntaxes: a JSP syntax and an XML syntax. The semantics and validation
-of a JSP syntax page is described with reference to the semantics and
+Jakarta Pages (JSP) can be authored using two different
+syntaxes: a Jakarta Pages (JSP) syntax and an XML syntax. The semantics and validation
+of a Jakarta Pages (JSP) syntax page is described with reference to the semantics and
validation of an equivalent document in the XML syntax.
-The first step is to parse the JSP page. The
+The first step is to parse the Jakarta Pages (JSP) page. The
page that is parsed is as expanded by the processing of include
directives. Information in the TLD is used in this step, including the
identification of custom tags, so there is some processing of the taglib
-directives in the JSP page.
+directives in the Jakarta Pages (JSP) page.
_Validation_
@@ -7304,7 +7300,7 @@ See the APIs for more details.
_Translation_
Finally, the XML document is processed to
-create a JSP page implementation class. This process may involve
+create a Jakarta Pages (JSP) page implementation class. This process may involve
creating scripting variables. Each custom action will provide
information about variables, either statically in the TLD, or more
flexibly by using the `getVariableInfo` method of a `TagExtraInfo`
@@ -7312,8 +7308,8 @@ class.
_Execution_
-Once a JSP page implementation class has been
-associated with a JSP page, the class will be treated as any other
+Once a Jakarta Pages (JSP) page implementation class has been
+associated with a Jakarta Pages (JSP) page, the class will be treated as any other
servlet class: requests will be directed to instances of the class. At
run-time, tag handler instances will be created and methods will be
invoked in them.
@@ -7324,11 +7320,11 @@ A classic tag handler is a Java class that
implements the `Tag`, `IterationTag`, or `BodyTag` interface, and is
the run-time representation of a custom action.
-The JSP page implementation class
+The Jakarta Pages (JSP) page implementation class
instantiates a tag handler object, or reuses an existing tag handler
-object, for each action in the JSP page. The handler object is a Java
+object, for each action in the Jakarta Pages (JSP) page. The handler object is a Java
object that implements the `jakarta.servlet.jsp.tagext.Tag` interface. The
-handler object is responsible for the interaction between the JSP page
+handler object is responsible for the interaction between the Jakarta Pages (JSP) page
and additional server-side objects.
There are three main interfaces: `Tag`,
@@ -7374,14 +7370,14 @@ This type of action can be implemented with a
tag handler that implements the `Tag` interface. The tag handler needs
to use only the `doStartTag` method which is invoked when the start tag
is encountered. It can access the attributes of the tag and information
-about the state of the JSP page. The information is passed to the `Tag`
+about the state of the Jakarta Pages (JSP) page. The information is passed to the `Tag`
object through setter method calls, prior to the call to `doStartTag`.
Since simple actions with empty tag bodies
are common, the Tag Library Descriptor can be used to indicate that the
tag is always intended to be empty. This indication leads to better
error checking at translation time, and to better code quality in the
-JSP page implementation class.
+Jakarta Pages (JSP) page implementation class.
===== Actions with a Body
@@ -7447,7 +7443,7 @@ updating the scripting variables. The variables thus affected are part
of the semantics of the custom action and are the responsibility of the
tag library author.
-This information is used at JSP page
+This information is used at Jakarta Pages (JSP) page
translation time and can be described in one of two ways: directly in
the TLD for simple cases, or through subclasses of `TagExtraInfo`.
Either mechanism will indicate the names and types of the scripting
@@ -7457,12 +7453,12 @@ At request time the tag handler will
associate objects with the scripting variables through the `pageContext`
object.
-It is the responsibility of the JSP page
+It is the responsibility of the Jakarta Pages (JSP) page
translator to automatically supply the code required to do the
“synchronization” between the `pageContext` values and the scripting
variables.
-There are some sections of JSP where
+There are some sections of Jakarta Pages (JSP) pages where
scripting is not allowed. For example, this is the case in a tag body
where the `body-content` is declared as ‘`scriptless`’, or in a page
where `` is true. In these sections, it is not
@@ -7479,8 +7475,8 @@ scriptlet expressions in tag bodies can rely on surrounding context
defined using scriptlets in the enclosing page.
With the advent of the Expression Language
-(EL) and JSP Standard Tag Library (JSTL), it is now feasible to develop
-JSP pages that do not need scriptlets or scriptlet expressions. This
+(EL) and Jakarta Standard Tag Library (JSTL), it is now feasible to develop
+Jakarta Pages (JSP) that do not need scriptlets or scriptlet expressions. This
allows us to define a tag invocation protocol that is easier to use for
many use cases.
@@ -7495,7 +7491,7 @@ developers who need the flexibility of the Java language in order to
write their tag handlers. The
`jakarta.servlet.jsp.tagext.SimpleTagSupport` class provides a default
implementation for all methods in `SimpleTag`.
-* In JSP, using tag files. This method can be
+* In Jakarta Pages (JSP), using tag files. This method can be
used by page authors who do not know Java. It can also be used by
advanced page authors or tag library developers who know Java but are
producing tag libraries that are presentation-centric or can take
@@ -7516,28 +7512,28 @@ allows for potential future integration with other technologies. This is
facilitated by the `JspContext` class, which `PageContext` now extends.
`JspContext` provides generic services such as storing the `JspWriter`
and keeping track of scoped attributes, whereas `PageContext` has
-functionality specific to serving JSPs in the context of servlets.
+functionality specific to serving Jakarta Pages (JSP)s in the context of servlets.
Whereas the `Tag` interface relies on `PageContext`, `SimpleTag` only
relies on `JspContext`.
The body of a Simple Tag, if present, is
-translated into a JSP Fragment and passed to the `setJspBody` method.
+translated into a Jakarta Pages (JSP) Fragment and passed to the `setJspBody` method.
The tag can then execute the fragment as many times as needed. See
-<> for more details on JSP
+<> for more details on Jakarta Pages (JSP)
Fragments.
-Because JSP Fragments do not support
-scriptlets, the of a SimpleTag cannot be "JSP". A JSP
+Because Jakarta Pages (JSP) Fragments do not support
+scriptlets, the of a SimpleTag cannot be "JSP". A Jakarta Pages (JSP)
page is invalid if it references a custom tag whose tag handler
implements the SimpleTag interface and whose is equal to
"JSP" as per the supporting TLD.
-==== JSP Fragments
+==== Jakarta Pages (JSP) Fragments
During the translation phase, various pieces
of the page are translated into implementations of the
`jakarta.servlet.jsp.tagext.JspFragment` abstract class, before being
-passed to a tag handler. This is done automatically for any JSP code in
+passed to a tag handler. This is done automatically for any Jakarta Pages (JSP) code in
the body of a named attribute (one that is defined by ``
) that is declared to be a fragment, or of type `JspFragment`, in the
TLD. This is also automatically done for the body of any tag handled by
@@ -7545,12 +7541,12 @@ a Simple Tag handler. Once passed in, the tag handler can then evaluate
and re-evaluate the fragment as many times as needed, or even pass it
along to other tag handlers, in the case of Tag Files.
-A JSP fragment can be parameterized by a tag
+A Jakarta Pages (JSP) fragment can be parameterized by a tag
handler by setting page-scoped attributes in the `JspContext` associated
with the fragment. These attributes can then be accessed via the EL.
A translation error must occur if a piece of
-JSP code that is to be translated into a JSP Fragment contains
+Jakarta Pages (JSP) code that is to be translated into a Jakarta Pages (JSP) Fragment contains
scriptlets or scriptlet expressions.
See the `jakarta.servlet.jsp.tagext` Javadoc
@@ -7622,7 +7618,7 @@ To make things easier, the
expose it as if it were a `Tag` instace. The original `JspTag` can be
retrieved through its `getAdaptee` method. Whenever calling the
`setParent` method on a classic `Tag` in a case where the outer tag does
-not implement `Tag`, the JSP Container must construct a new
+not implement `Tag`, the Jakarta Pages (JSP) Container must construct a new
`TagAdapter` and call `setParent` on the classic `Tag` passing in the
adapter.
@@ -7650,7 +7646,7 @@ interface.
A tag library may include classes that are
event listeners (see the Servlet 6.2 specification). The listeners
-classes are listed in the tag library descriptor and the JSP container
+classes are listed in the tag library descriptor and the Jakarta Pages (JSP) container
automatically instantiates them and registers them. A Container is
required to locate all TLD files (see <> for details on how they are
identified), read their `listener` elements, and treat the event
@@ -7681,7 +7677,7 @@ Section SRV.15.5 of the Servlet Specification
describes the behavior of annotations and resource injection in Jakarta EE
technology compliant web containers.
-In the JSP specification, tag handlers which
+In the Jakarta Pages (JSP) specification, tag handlers which
implement interfaces `jakarta.servlet.jsp.tagext.Tag` and
`jakarta.servlet.jsp.tagext.SimpleTag` may be annotated for injection. In
both cases, injection occurs immediately after an instance of the tag
@@ -7704,18 +7700,18 @@ The annotations supported are:
Please see Section SRV.15.5 of the servlet
specification for more details on these annotations.
-A JSP container that is not part of a Jakarta EE
+A Jakarta Pages (JSP) container that is not part of a Jakarta EE
technology-compliant implementation is encouraged, but not required, to
support resource injection.
-Resource injection is not supported for JSP
-pages or tag files.
+Resource injection is not supported for Jakarta Pages (JSP)
+pages, documents or tag files.
=== Tag Libraries
A tag library is a collection of actions that
-encapsulate some functionality to be used from within a JSP page. A tag
-library is made available to a JSP page through a `taglib` directive
+encapsulate some functionality to be used from within a Jakarta Pages (JSP) page. A tag
+library is made available to a Jakarta Pages (JSP) page through a `taglib` directive
that identifies the tag library via a URI (Universal Resource
Identifier).
@@ -7729,9 +7725,9 @@ handler classes as indicated in <> below.
==== Packaged Tag Libraries
-JSP page authoring tools and JSP containers
+Jakarta Pages (JSP) page authoring tools and Jakarta Pages (JSP) containers
are required to accept a tag library that is packaged as a JAR file.
-When deployed in a JSP container, the standard JAR conventions described
+When deployed in a Jakarta Pages (JSP) container, the standard JAR conventions described
in the Servlet 6.2 specification apply, including the conventions for
dependencies on extensions.
@@ -7764,17 +7760,17 @@ mapping between the URI and the TLD is explained further below.
==== Tag Library Directive
-The `taglib` directive in a JSP page declares
+The `taglib` directive in a Jakarta Pages (JSP) page declares
that the page uses a tag library, uniquely identifies the tag library
using a URI, and associates a tag prefix with usage of the actions in
the library.
-A JSP container maps the URI used in the
+A Jakarta Pages (JSP) container maps the URI used in the
`taglib` directive into a Tag Library Descriptor in two steps: it
resolves the URI into a TLD resource path, and then derives the TLD
object from the TLD resource path.
-If the JSP container cannot locate a TLD
+If the Jakarta Pages (JSP) container cannot locate a TLD
resource path for a given URI, a fatal translation error shall result.
Similarly, it is a fatal translation error for a URI attribute value to
resolve to two different TLD resource paths.
@@ -7787,18 +7783,18 @@ by it.
The Tag Library Descriptor (TLD) is an XML
document that describes a tag library. The TLD for a tag library is used
-by a JSP container to interpret pages that include `taglib` directives
-referring to that tag library. The TLD is also used by JSP page
-authoring tools that will generate JSP pages that use a library, and by
+by a Jakarta Pages (JSP) container to interpret pages that include `taglib` directives
+referring to that tag library. The TLD is also used by Jakarta Pages (JSP) page
+authoring tools that will generate Jakarta Pages (JSP) that use a library, and by
authors who do the same manually.
The TLD includes documentation on the library
-as a whole and on its individual tags, version information on the JSP
+as a whole and on its individual tags, version information on the Jakarta Pages (JSP)
container and on the tag library, and information on each of the actions
defined in the tag library.
The TLD may name a `TagLibraryValidator`
-class that can validate that a JSP page conforms to a set of constraints
+class that can validate that a Jakarta Pages (JSP) page conforms to a set of constraints
expected by the tag library.
Each action in the library is described by
@@ -7829,7 +7825,7 @@ descriptor files must always be in the `WEB-INF` directory, or some
subdirectory of it. TLD files should not be placed in `/WEB-INF/classes`
or `/WEB-INF/lib`, and 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`.
+an implicit tag library with its Jakarta Pages (JSP) version and `tlib-version`.
The XML Schema for a TLD document is
`http://java.sun.com/xml/ns/j2ee/web-jsptaglibrary_2_1.xsd`.
@@ -7862,7 +7858,7 @@ is built from an explicit taglib map in `web.xml` (described in
extended with implicit entries deduced from packaged tag libraries in
the web application (described in <>), and
implicit entries known to the
-JSP container. The fallback interpretation is targetted to a casual use
+Jakarta Pages (JSP) container. The fallback interpretation is targetted to a casual use
of the mechanism, as in the development cycle of the Web Application; in
that case the URI is interpreted as a direct path to the TLD (see
<>).
@@ -7873,8 +7869,8 @@ sections for details):
. If the container is Jakarta EE platform
compliant, the Map Entries for the tag libraries that are part of the
-Jakarta EE platform. This currently includes the Jakarta Server Pages Standard
-Tag Library libraries and the Jakarta Server Faces libraries.
+Jakarta EE platform. This currently includes the Jakarta Standard
+Tag Library libraries and the Jakarta Faces libraries.
. Taglib Map in web.xml
. Implicit Map Entries from TLDs
.. TLDs in JAR files in WEB-INF/lib
@@ -7947,7 +7943,7 @@ The taglib map generated in Sections
<> may contain one or more
`` entries. Each entry is identified by a `taglib_uri`,
which is the value of the `` subelement. This `taglib_uri`
-may be an absolute URI, or a relative URI spec starting with `/` or one
+may be an absolute URI, or a relative URI specification starting with `/` or one
not starting with `/`. Each entry also defines a `taglib_location` as
follows:
@@ -7987,7 +7983,7 @@ URI that does not start with `/` +
Look in the `taglib map` for an entry whose
`taglib_uri` is `noroot_rel_uri`. If found, the corresponding
`taglib_location` is the TLD resource path. If no such entry is found,
-resolve `noroot_rel_uri` relative to the current JSP page where the
+resolve `noroot_rel_uri` relative to the current Jakarta Pages (JSP) page where the
directive appears; that value (by definition, this is a relative URI
specification that starts with `/`) is the TLD resource path. For
example, if `/a/b/c.jsp` references +
@@ -8039,7 +8035,7 @@ accountability. For example, in the case above, it enables:
The set of classes available at translation
time is the same as that available at runtime: the classes in the
-underlying Java platform, those in the JSP container, and those in the
+underlying Java platform, those in the Jakarta Pages (JSP) container, and those in the
class files in `WEB-INF/classes`, in the JAR files in `WEB-INF/lib`,
and, indirectly those indicated through the use of the `class-path`
attribute in the `META-INF/MANIFEST` file of these JAR files.
@@ -8049,7 +8045,7 @@ attribute in the `META-INF/MANIFEST` file of these JAR files.
As part of the process of assembling a web
application, the Application Assembler will create a `WEB-INF/`
directory, with appropriate `lib/` and `classes/` subdirectories, place
-JSP pages, servlet classes, auxiliary classes, and tag libraries in the
+Jakarta Pages (JSP), servlet classes, auxiliary classes, and tag libraries in the
proper places, and create a `WEB-INF/web.xml` that ties everything
together.
@@ -8066,13 +8062,13 @@ library; see <>.
==== Well-Known URIs
-A JSP container may “know of” some specific
+A Jakarta Pages (JSP) container may “know of” some specific
URIs and may provide alternate implementations for the tag libraries
described by these URIs, but the user must see the behavior as that
described by the required, portable tag library description described by
the URI.
-A JSP container must always use the mapping
+A Jakarta Pages (JSP) container must always use the mapping
specified for a URI in the `web.xml` deployment descriptor if present.
If the deployer wants to use the platform-specific implementation of the
well-known URI, the mapping for that URI should be removed at deployment
@@ -8084,22 +8080,22 @@ The JSP 2.0 Tag Library Descriptor supports
the notion of Tag Extension Elements and Tag Library Extension Elements.
These are elements added to the TLD by the tag library developer that
provide additional information about the tag, using a schema defined
-outside of the JSP specification.
+outside of the Jakarta Pages (JSP) specification.
The information contained in these extensions
is intended to be used by tools only, and is not accessible at
-compile-time, deployment-time, or run-time. JSP containers must not
+compile-time, deployment-time, or run-time. Jakarta Pages (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. In addition, JSP
+of a particular Tag or Tag Library Extension Element. In addition, Jakarta Pages (JSP)
containers must consider invalid any tag library that specifies
`mustUnderstand="true"` for any Tag or Tag Library Extension element.
Any attempt to use an invalid tag library must produce a translation
error. This is to preserve application compatibility across containers.
-The JSP container may use schema to validate
+The Jakarta Pages (JSP) container may use schema to validate
the structure of the Tag Library Descriptor. If it does so, any new
content injected into Tag or Tag Library Extension elements must not be
-validated by the JSP Container.
+validated by the Jakarta Pages (JSP) Container.
Tag Library Extension Elements provide
extension information at the tag library level, and are specified by
@@ -8118,7 +8114,7 @@ that cause sounds to be played when inserting tags in a document.
In this hypothetical example, ACME has
published an XML Schema at `http://www.acme.com/acme.xsd` that defines
-the extensions, and has provided plug-ins for various JSP-capable IDEs
+the extensions, and has provided plug-ins for various Jakarta Pages (JSP) capable IDEs
to recognize these extension elements.
The following example tag library uses ACME’s
@@ -8244,7 +8240,7 @@ The corresponding `acme.xsd` file would look something like:
=== Validation
There are a number of reasons why the
-structure of a JSP page should conform to some validation rules:
+structure of a Jakarta Pages (JSP) page should conform to some validation rules:
* Request-time semantics; e.g. a subelement
may require the information from some enclosing element at request-time.
@@ -8255,7 +8251,7 @@ development group may want to constrain the way some features are used.
Validation can be done either at
translation-time or at request-time. In general translation-time
-validation provides a better user experience, and the JSP 4.1
+validation provides a better user experience, and the Jakarta Pages (JSP) 4.1
specification provides a very flexible translation-time validation
mechanism.
@@ -8283,13 +8279,13 @@ TLD.
===== Validator Classes
A `TagLibraryValidator` class may be listed
-in the TLD for a tag library to request that a JSP page be validated.
-The XML view of a JSP page is exposed through a `PageData` class, and
+in the TLD for a tag library to request that a Jakarta Pages (JSP) page be validated.
+The XML view of a Jakarta Pages (JSP) page is exposed through a `PageData` class, and
the validator class can do any checks the tag library author may have
found appropriate.
-The JSP container must uniquely identify all
-XML elements in the XML view of a JSP page through a `jsp:id` attribute.
+The Jakarta Pages (JSP) container must uniquely identify all
+XML elements in the XML view of a Jakarta Pages (JSP) page through a `jsp:id` attribute.
This attribute can be used to provide better information on the location
of an error.
@@ -8298,7 +8294,7 @@ initialization parameters in the TLD. This eases the reuse of validator
classes. We expect that validator classes will be written based on
different XML schema mechanisms (DTDs, XSchema, Relaxx, others).
Standard validator classes may be incorporated into a later version of
-the JSP specification if a clear schema standard appears at some point.
+the Jakarta Pages (JSP) specification if a clear schema standard appears at some point.
===== TagExtraInfo Class Validation
@@ -8324,7 +8320,7 @@ In some cases, additional request-time
validation will be done dynamically within the methods in the tag
handler. If an error is discovered, an instance of `JspException` can be
thrown. If uncaught, this object will invoke the errorpage mechanism of
-the JSP specification.
+the Jakarta Pages (JSP) specification.
=== Conventions and Other Issues
@@ -8340,7 +8336,7 @@ introduction of implicit objects:
* Add an action called `defineObjects` to
define the desired objects.
-The JSP page can make these objects available
+The Jakarta Pages (JSP) page can make these objects available
as follows:
[source,jsp]
@@ -8364,9 +8360,9 @@ compliant).
This mechanism, together with the access to
metadata information allows for vendors to innovate within the standard.
-NOTE: If a feature is added to a JSP specification, and a vendor also provides
+NOTE: If a feature is added to a Jakarta Pages (JSP) specification, and a vendor also provides
that feature through its vendor-specific mechanism, the standard mechanism, as
-indicated in the JSP specification will “win”. This means that vendor-specific
+indicated in the Jakarta Pages (JSP) specification will “win”. This means that vendor-specific
mechanisms can slowly migrate into the specification as they prove their
usefulness.
@@ -8386,8 +8382,8 @@ and deployment time. For example, a tag library that provides access to
databases may be customized with login and password information.
There is no convenient place in `web.xml` in
-the Servlet 6.2 spec for customization information. A standardized
-mechanism is probably going to be part of a forthcoming JSP
+the Servlet 6.2 specification for customization information. A standardized
+mechanism is probably going to be part of a forthcoming Jakarta Pages (JSP)
specification, but in the meantime the suggestion is that a tag library
author place this information in a well-known location at some resource
in the `WEB-INF/` portion of the Web Application and access it via
@@ -8399,40 +8395,40 @@ the `getResource` call on the `ServletContext`.
This chapter describes the details of tag
files, a JSP 2.0 onwards facility that allows page authors to author tag
-extensions using only JSP syntax. In the past, the ability to
+extensions using only Jakarta Pages (JSP) syntax. In the past, the ability to
encapsulate presentation logic into reusable, full-featured tag
libraries was only available to developers that had a reasonable amount
of Java experience. Tag files bring the power of reuse to the basic page
-author, who are not required to know Java. When used together with JSP
+author, who are not required to know Java. When used together with Jakarta Pages (JSP)
Fragments and Simple Tag Handlers, these concepts have the ability to
-simplify JSP development substantially, even for developers who do know
+simplify Jakarta Pages (JSP) development substantially, even for developers who do know
Java.
=== Overview
-As of JSP version 2.0, the JSP Compiler is
+As of Jakarta Pages (JSP) version 2.0, the Jakarta Pages (JSP) Compiler is
required to recognize tag files. A tag file is a source file that
-provides a way for a page author to abstract a segment of JSP code and
+provides a way for a page author to abstract a segment of Jakarta Pages (JSP) code and
make it reusable via a custom action.
-Tag files allow a JSP page author to create
-tag libraries using JSP syntax. This means that page authors no longer
+Tag files allow a Jakarta Pages (JSP) page author to create
+tag libraries using Jakarta Pages (JSP) syntax. This means that page authors no longer
need to know Java or ask someone who knows Java to write a tag
extension. Even for page authors or tag library developers who know
Java, writing tag files is more convenient when developing tags that
primarily output template text.
The required file extension for a tag file
-are `.tag` or `.tagx.` As is the case with JSP files, the actual tag may
+are `.tag` or `.tagx.` As is the case with Jakarta Pages (JSP) files, the actual tag may
be composed of a top file that includes other files that contain either
a complete tag or a segment of a tag file. Just as the recommended
-extension for a segment of a JSP file is `.jspf`, the recommended
+extension for a segment of a Jakarta Pages (JSP) file is `.jspf`, the recommended
extension for a segment of a tag file is `.tagf`.
=== Syntax of Tag Files
The syntax of a tag file is similar to that
-of a JSP page, with the following exceptions:
+of a Jakarta Pages (JSP) page, with the following exceptions:
* Directives - Some directives are not
available or have limited availability, and some tag file specific
@@ -8441,7 +8437,7 @@ on tag file directives.
* The `` and ``
standard actions can only be used in Tag Files.
-The EBNF grammar in <> describes the syntax of tag
+The EBNF grammar in <> describes the syntax of tag
files. The root production for a tag files is `JSPTagDef`.
See <> for details on tag files in XML syntax.
@@ -8449,7 +8445,7 @@ See <> for details on tag files in XML syntax.
=== Semantics of Tag Files
For each tag file in the web application, a
-tag handler is made available to JSP pages and other tag files. The
+tag handler is made available to Jakarta Pages (JSP) and other tag files. The
specifics of how this is done are left up to the Container
implementation. For example, some Containers may choose to compile tag
files into Java tag handlers, whereas others may decide to interpret the
@@ -8461,22 +8457,22 @@ handlers defined as tag files:
* The tag file implementation must keep a
copy of the `JspContext` instance passed to it by the invoking page
-via the `setJspContext` method. This is called the _Invoking JSP Context_.
+via the `setJspContext` method. This is called the _Invoking JspContext_.
* 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`. This
+maintain a second instance of `JspContext` called a _JspContext Wrapper_.
+If the Invoking JspContext is an instance of `PageContext`,
+the JspContext Wrapper must also be an instance of `PageContext`. This
wrapper must be returned when `getJspContext()` is called.
-* For each invocation to the tag, the JSP
-Context Wrapper must present a clean page scope containing no initial
+* For each invocation to the tag, the
+JspContext Wrapper must present a clean page scope containing no initial
elements. All scopes other than the page scope must be identical to
-those in the Invoking JSP Context and must be modified accordingly when
-updates are made to those scopes in the JSP Context Wrapper. Any
+those in the Invoking JspContext and must be modified accordingly when
+updates are made to those scopes in the JspContext Wrapper. Any
modifications to the page scope, however, must not affect the Invoking
-JSP Context.
+JspContext.
* For each attribute declared and specified,
-a page-scoped variable must be created in the page scope of the JSP
-Context Wrapper, unless the attribute is a deferred value or a deferred
+a page-scoped variable must be created in the page scope of the
+JspContext Wrapper, unless the attribute is a deferred value or a deferred
method, in which case the VariableMapper obtained from the ELContext in
the current pageContext is used to map the deferred expression to the
attribute name. The name of the variable must be the same as the
@@ -8513,7 +8509,7 @@ evaluation of the deferred expression. Secondly, since the
`VariableMapper` is used to resolve variables at EL parse time, a
deferred expression such as `#{attr1.foo}` is not dependent on `attr1`
anymore, so that it can be evaluated long after the end of life of the
-tag file's pageContext. This is very useful for Jakarta Server Faces
+tag file's pageContext. This is very useful for Jakarta Faces
applications. +
+
Since the EL syntax does not allow for invocation of the method in a
@@ -8523,9 +8519,9 @@ another tag that has a deferred-method attribute, in the form of
* For all intents and purposes other than for
synchronizing the `AT_BEGIN`, `NESTED`, and `AT_END` scripting
-variables, the effective `JspContext` for the tag file is the JSP
-Context Wrapper. For example, the `jspContext` scripting variable must
-point to the JSP Context Wrapper instead of the invoking JSP Context.
+variables, the effective `JspContext` for the tag file is the
+JspContext Wrapper. For example, the `jspContext` scripting variable must
+point to the JspContext Wrapper instead of the invoking JspContext.
* The tag handler must behave as though a tag
library descriptor entry was defined for it, in accordance with the
@@ -8533,7 +8529,7 @@ library descriptor entry was defined for it, in accordance with the
file translation unit.
It is legal for a tag file to forward to a
-page via the `` standard action. Just as for JSP pages, the
+page via the `` standard action. Just as for Jakarta Pages (JSP), the
forward is handled through the request dispatcher. Upon return from the
`RequestDispatcher.forward` method, the generated tag handler must stop
processing of the tag file and throw
@@ -8552,7 +8548,7 @@ tag handler from a tag file. In general, SimpleTag Extensions can be
used in environments other than servlet environments. However, because
the `Tag` interface relies on `PageContext`, which in turn assumes a
servlet environment, using classic tag handlers indirectly binds the use
-of the tag file to servlet environments. Nonetheless, the JSP container
+of the tag file to servlet environments. Nonetheless, the Jakarta Pages (JSP) container
must allow such an invocation to occur. 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
@@ -8561,14 +8557,14 @@ of the classic tag fails, and a `JspException` must be thrown.
If a tag file in XML syntax contains a
jsp:root element, the value of that element’s version attribute must
-match the tag file’s JSP version. See <>, and
-<>, for how the JSP version
+match the tag file’s Jakarta Pages (JSP) version. See <>, and
+<>, for how the Jakarta Pages (JSP) version
of a tag file is determined.
=== Packaging Tag Files
One of the goals of tag files as a technology
-is to make it as easy to write a tag handler as it is to write a JSP.
+is to make it as easy to write a tag handler as it is to write a Jakarta Pages (JSP) page.
Traditionally, writing tag handlers has been a tedious task, with a lot
of time spent compiling and packaging the tag handlers and writing a TLD
to provide information to tools and page authors about the custom
@@ -8578,7 +8574,7 @@ power and flexibility as classic tag handlers have.
==== Location of Tag Files
-Tag extensions written in JSP using tag files
+Tag extensions written in Jakarta Pages (JSP) using tag files
can be placed in one of two locations. The first possibility is in the
`/META-INF/tags/` directory (or a subdirectory of `/META-INF/tags/`) in
a `JAR` file installed in the `/WEB-INF/lib/` directory of the web
@@ -8592,7 +8588,7 @@ little packaging. Only files with a `.tag` or `.tagx` extension are
recognized by the container to be tag files.
Tag files that appear in any other location
-are not considered tag extensions and must be ignored by the JSP
+are not considered tag extensions and must be ignored by the Jakarta Pages (JSP)
container. For example, a tag file that appears in the root of a web
application would be treated as content to be served.
@@ -8600,7 +8596,7 @@ application would be treated as content to be served.
To be accessible, tag files bundled in a
`JAR` require a Tag Library Descriptor. Tag files that appear in a JAR
-but are not defined in a TLD must be ignored by the JSP container.
+but are not defined in a TLD must be ignored by the Jakarta Pages (JSP) container.
JSP 2.0 added an additional TLD element to
describe tags within a tag library, namely ``. The
@@ -8609,7 +8605,7 @@ define the tag name and the full path of the tag file from the root of
the JAR, respectively. In a JAR file, the `` element must always
begin with `/META-INF/tags`. The values for the other subelements of
`` override the defaults specified in the tag directive. Tag
-files packaged in a JAR inherit the JSP version of the TLD that
+files packaged in a JAR inherit the Jakarta Pages (JSP) version of the TLD that
references them.
Note that it is possible to combine both
@@ -8627,12 +8623,12 @@ invalid tag library must trigger a translation error.
Tag files placed in the `/WEB-INF/tags/`
directory of the web application, or a subdirectory, are made easily
-accessible to JSPs without the need to explicitly write a Tag Library
+accessible to Jakarta Pages (JSP)s without the need to explicitly write a Tag Library
Descriptor. This makes it convenient for page authors to quickly
-abstract reusable JSP code by simply creating a new file and placing the
+abstract reusable Jakarta Pages (JSP) code by simply creating a new file and placing the
code inside of it.
-The JSP container must interpret the
+The Jakarta Pages (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 that directory. There are no special
@@ -8648,7 +8644,7 @@ contains three tag libraries:
/WEB-INF/tags/bar/baz/
/WEB-INF/tags/bar/baz/d.tag
-The JSP container must generate an implicit
+The Jakarta Pages (JSP) container must generate an implicit
tag library for each directory under and including `/WEB-INF/tags/`.
This tag library can be imported only via the `tagdir` attribute of the
`taglib` directive (see <>), and has the following
@@ -8684,23 +8680,23 @@ Library Descriptor for the `/WEB-INF/tags/bar/baz/` directory would be:
-The JSP version of an implicit tag library
+The Jakarta Pages (JSP) version of an implicit tag library
defaults to 2.0.
-The JSP version and tlib-version of an
+The Jakarta Pages (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. A JSP 2.1 onwards container must consider only
-the JSP version and tlib-version specified by an implicit.tld file, and
+the Jakarta Pages (JSP) version and tlib-version specified by an implicit.tld file, and
ignore its short-name element. Any additional elements in an
-implicit.tld file must cause a translation error. The JSP version
+implicit.tld file must cause a translation error. The Jakarta Pages (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.
-Upon deployment, the JSP container must
+Upon deployment, the Jakarta Pages (JSP) container must
search 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.
+actions defined in these tags available to Jakarta Pages (JSP) files.
If a directory contains two files with the
same tag name (e.g. `a.tag` and `a.tagx`), it is considered to be the
@@ -8714,7 +8710,7 @@ create additional tags from the same tag files. This is accomplished by
adding a `` element with a `` that points to the tag
file. In this case, the value of `` must start with
`/WEB-INF/tags`. 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
+an implicit TLD, the Jakarta Pages (JSP) versions of the TLD and implicit TLD do not
need to match.
==== Packaging as Precompiled Tag Handlers
@@ -8723,7 +8719,7 @@ Tag files can also be compiled into Java
classes and bundled as a tag library. This is useful for the situation
where a tag library developer wishes to distribute a binary version of
the tag library without the original source. Tag library developers that
-choose this form of packaging must use a tool that produces portable JSP
+choose this form of packaging must use a tool that produces portable Jakarta Pages (JSP)
code that uses only standard APIs. Containers are not required to
provide such a tool.
@@ -8734,7 +8730,7 @@ available within tag files, which define Simple Tag Handlers.
<<_Directives_available_to_tag_files>>
outlines which directives are available in tag files:
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[[_Directives_available_to_tag_files]]
.Directives available to tag files
[cols="20,20,60",options="header"]
@@ -8754,35 +8750,35 @@ a translation error must result.
|`taglib`
|yes
-|Identical to JSP pages.
+|Identical to a Jakarta Pages (JSP) page.
|`include`
|yes
-|Identical to JSP pages. Note that if the
+|Identical to a Jakarta Pages (JSP) page. Note that if the
included file contains syntax unsuitable for tag files, a translation
error must occur.
|`tag`
|yes
|Only applicable to tag files. An attempt to
-use this directive in JSP pages will result in a translation error.
+use this directive in a Jakarta Pages (JSP) page will result in a translation error.
|`attribute`
|yes
|Only applicable to tag files. An attempt to
-use this directive in JSP pages will result in a translation error.
+use this directive in a Jakarta Pages (JSP) page will result in a translation error.
|`variable`
|yes
|Only applicable to tag files. An attempt to
-use this directive in JSP pages will result in a translation error.
+use this directive in a Jakarta Pages (JSP) page will result in a translation error.
|===
==== The tag Directive
The `tag` directive is similar to the `page`
-directive, but applies to tag files instead of JSPs. Like the `page`
+directive, but applies to tag files instead of Jakarta Pages (JSP) pages. Like the `page`
directive, 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). There
@@ -8796,7 +8792,7 @@ multiple times. Multiple uses of the `import` attribute are cumulative
match.
The attribute/value namespace is reserved for
-use by this, and subsequent, JSP specifications.
+use by this, and subsequent, Jakarta Pages (JSP) specifications.
Unrecognized attributes or values result in
fatal translation errors.
@@ -8837,7 +8833,7 @@ tag_directive_attr_list ::= { display-name="display-name" }
The details of the attributes are as follows:
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[cols="20,80"]
[%breakable]
[[_Details_of_tag_directive_attribute]]
@@ -8926,7 +8922,7 @@ However, there is no corresponding global configuration element in
semantics of the deferredSyntaxAllowedAsLiteral attribute of the `page`
directive. However, there is no corresponding global configuration
element in `web.xml`. Causes a translation error if specified in a tag
-file with a JSP version less than 2.1.
+file with a Jakarta Pages (JSP) version less than 2.1.
|`trimDirective-` +
`Whitespaces`
@@ -8982,7 +8978,7 @@ attribute_directive_attr_list ::= name="attribute-name"
The details of the attributes are as follows:
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[cols="20,80"]
[%breakable]
.Details of `attribute` directive attributes
@@ -9033,14 +9029,14 @@ Defaults to no description.
represents a deferred value expression. Only one of `deferredValue` or
`deferredMethod` may be true. If `deferredValueType` is specified,
default is true, otherwise default is false. Causes a translation error
-if specified in a tag file with a JSP version less than 2.1.
+if specified in a tag file with a Jakarta Pages (JSP) version less than 2.1.
|`deferredValueType`
|(optional) The expected type resulting from
the evaluation of the attribute's value expression. If both
`deferredValueType` and `deferredValue` are specified, `deferredValue`
must be true. If `deferredValue` is true, default is `java.lang.Object`
-. Causes a translation error if specified in a tag file with a JSP
+. Causes a translation error if specified in a tag file with a Jakarta Pages (JSP)
version less than 2.1.
|`deferredMethod`
@@ -9048,7 +9044,7 @@ version less than 2.1.
represents a deferred method expression. Only one of `deferredValue` or
`deferredMethod` may be true. If `deferredMethodSignature` is specified,
default is true, otherwise default is false. Causes a translation error
-if specified in a tag file with a JSP version less than 2.1.
+if specified in a tag file with a Jakarta Pages (JSP) version less than 2.1.
|`deferredMethod-` +
`Signature`
@@ -9058,7 +9054,7 @@ attribute's method expression. If both `deferredMethod` and
`deferredMethodSignature` are specified, `deferredMethod` must be true.
If `deferredMethod` is true and `deferredMethodSignature` is not
specified, it defaults to `void methodname()`. Causes a translation
-error if specified in a tag file with a JSP version less than 2.1.
+error if specified in a tag file with a Jakarta Pages (JSP) version less than 2.1.
|===
@@ -9113,7 +9109,7 @@ variable_directive_attr_list ::= ( name-given="output-name"
The details of the attributes are as follows:
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[cols="25,75"]
[%breakable]
.Details of `variable` directive attributes
@@ -9176,8 +9172,8 @@ variable. Defaults to no description.
=== Tag Files in XML Syntax
Tag files can be authored using the XML
-syntax, as described in <>.
-This section describes the few distinctions from the case of JSP
+syntax, as described in <>.
+This section describes the few distinctions from the case of Jakarta Pages (JSP)
documents.
Tag files in XML syntax must have the
@@ -9188,7 +9184,7 @@ XML syntax.
The `jsp:root` element can, but needs not,
appear in tag files in XML syntax. A `jsp:root` element cannot appear in
-a tag file in JSP syntax.
+a tag file in standard syntax.
As indicated in <>, the default for tag
files, in either syntax, is not to generate the xml declaration. The
@@ -9202,16 +9198,16 @@ inferred using the conventions for XML documents. Using the
=== XML View of a Tag File
-Similar to JSP pages, tag files have an
+Similar to Jakarta Pages (JSP), tag files have an
equivalent XML document, the XML view of a tag file, that is exposed to
the translation phase for validation. During the translation phase for a
tag file, a tag XML view is created and passed to all tag library validators declared in
all tag libraries declared in the tag file.
The XML view of a tag file is identical to
-the XML view of a JSP, except that there are additional XML elements
+the XML view of a Jakarta Pages (JSP), except that there are additional XML elements
defined to handle tag file specific features. The XML view of a tag file
-is obtained in the same way that the XML view of a JSP page is obtained
+is obtained in the same way that the XML view of a Jakarta Pages (JSP) page is obtained
(see <>).
=== Implicit Objects
@@ -9226,7 +9222,7 @@ Each implicit object has a class or interface
type defined in a core Java technology or Jakarta Servlet API package, as
shown in <<_Implicit_Objects_Available_in_Tag_Files>>.
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[cols="15,45,40",options="header"]
[%breakable]
[[_Implicit_Objects_Available_in_Tag_Files]]
@@ -9281,14 +9277,14 @@ configuration object (as in the call
|`config`
|`jakarta.servlet.ServletConfig`
-|The `ServletConfig` for this JSP page. +
+|The `ServletConfig` for this Jakarta Pages (JSP) page. +
`page` scope.
|===
Object names with prefixes `jsp`, `jsp`,
`jspx` and `jspx`, in any combination of upper and lower case, are
-reserved by the JSP specification.
+reserved by the Jakarta Pages (JSP) specification.
=== Variable Synchronization
@@ -9335,12 +9331,12 @@ details.
==== Synchronization Points
-The JSP container is required to generate
+The Jakarta Pages (JSP) container is required to generate
code to handle the synchronization of each declared variable. The
details of how and when each variable is synchronized varies by the
variable’s scope, as per <<_Variable_synchronization_behavior>>.
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[cols="40,20,20,20",options="header"]
[%breakable]
[[_Variable_synchronization_behavior]]
@@ -9574,36 +9570,36 @@ Scripting Elements when the language directive value is `java`.
The scripting language is based on the Java
programming language (as specified by “The Java Language
-Specification”), but note that there is no valid JSP page, or a subset
+Specification”), but note that there is no valid Jakarta Pages (JSP) page, or a subset
of a page, that is a valid Java program.
The following sections describe the details
of the relationship between the scripting declarations, scriptlets, and
scripting expressions, and the Java programming language. The
-description is in terms of the structure of the JSP page implementation
-class. A JSP Container need not generate the JSP page implementation
+description is in terms of the structure of the Jakarta Pages (JSP) page implementation
+class. A Jakarta Pages (JSP) Container need not generate the Jakarta Pages (JSP) page implementation
class, but it must behave as if one exists.
=== Overall Structure
-Some details of what makes a JSP page legal
+Some details of what makes a Jakarta Pages (JSP) page legal
are very specific to the scripting language used in the page. This is
especially complex since scriptlets are language fragments, not
complete language statements.
-==== Valid JSP Page
+==== Valid Jakarta Pages (JSP) Page
-A JSP page is valid for a Java Platform if and
-only if the JSP page implementation class defined by
+A Jakarta Pages (JSP) page is valid for a Java Platform if and
+only if the Jakarta Pages (JSP) page implementation class defined by
<<_Structure_of_the_Java_Programming_Language_Class>> (after applying all
-include directives), together with any other classes defined by the JSP
+include directives), together with any other classes defined by the Jakarta Pages (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.
+the validation methods for all the tag libraries associated with the Jakarta Pages (JSP) page.
==== Reserved Names
All names of the form `{\_}jsp_*` and `{\_}jspx_*`, in any combination
-of upper and lower case, are reserved for the JSP specification. Names
+of upper and lower case, are reserved for the Jakarta Pages (JSP) specification. Names
of this form that are not defined in this specification are reserved
for future expansion.
@@ -9614,7 +9610,7 @@ need not be performed literally. An implementation may implement things
differently to provide better performance, lower memory footprint, or
other implementation attributes.
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[cols="25,75"]
[%breakable]
[[_Structure_of_the_Java_Programming_Language_Class]]
@@ -9625,13 +9621,13 @@ other implementation attributes.
`jsp` directive
|`import name1`
-|`SuperClass` is either selected by the JSP
-container or by the JSP author via the `jsp` directive. +
+|`SuperClass` is either selected by the Jakarta Pages (JSP)
+container or by the Jakarta Pages (JSP) author via the `jsp` directive. +
Name of class (`jspXXX`) is implementation
dependent.
|`class jspXXX extends SuperClass`
-|Start of the body of a JSP page
+|Start of the body of a Jakarta Pages (JSP) page
implementation class
|`{`
@@ -9671,7 +9667,7 @@ they appear.
=== Initialization Section
This section defines and initializes the
-implicit objects available to the JSP page. See <>.
+implicit objects available to the Jakarta Pages (JSP) page. See <>.
=== Main Section
@@ -9679,7 +9675,7 @@ This section provides the main mapping between
a request and a response object.
The content of the main section is determined
-from scriptlets, expressions, and the text body of the JSP page. The
+from scriptlets, expressions, and the text body of the Jakarta Pages (JSP) page. The
elements are processed sequentially in the order in which they appear in
the page. The translation for each one is determined as indicated below,
and its translation is inserted into this section. The translation
@@ -9754,7 +9750,7 @@ affected by other constructs, for example scriptlets.
The semantics of the action type determines
the names of the variables (usually the name of an `id` attribute, if
-present) and their type. The only standard action in the JSP
+present) and their type. The only standard action in the Jakarta Pages (JSP)
specification that defines objects is the `jsp:useBean` action. The name
of the variable introduced is the name of the `id` attribute and its
type is the type of the `class` attribute.
@@ -9792,26 +9788,26 @@ variables with `declare=false` and explicitly declare the variables themselves.
== XML View{counter2:jsp-chapter}
This chapter provides details on the XML
-view of a JSP page and tag files. The XML views are used to enable
-validation of JSP pages and tag files.
+view of a Jakarta Pages (JSP) page and tag files. The XML views are used to enable
+validation of Jakarta Pages (JSP) and tag files.
-=== XML View of a JSP Document, JSP Page or Tag File
+=== XML View of a Jakarta Pages (JSP) Document, Jakarta Pages (JSP) Page or Tag File
-This section describes the XML view of a JSP
-page or tag file: the mapping between a JSP page, JSP document or tag
+This section describes the XML view of a Jakarta Pages (JSP)
+page or tag file: the mapping between a Jakarta Pages (JSP) page, Jakarta Pages (JSP) document or tag
file, and an XML document describing it.
-==== JSP Documents and Tag Files in XML Syntax
+==== Jakarta Pages (JSP) Documents and Tag Files in XML Syntax
-The XML view of a JSP document or of a tag
-file written in XML syntax is very close to the original JSP page. Only
+The XML view of a Jakarta Pages (JSP) document or of a tag
+file written in XML syntax is very close to the original Jakarta Pages (JSP) page. Only
five transformations are performed:
-* Expand all include directives into the JSP
-content they include. See <> for the
+* Expand all include directives into the Jakarta Pages (JSP)
+content they include. See <> for the
semantics of mixing XML and standard syntax content.
* Add a `jsp:root` element as the root
-element if the JSP document or tag file in XML syntax does not have it.
+element if the Jakarta Pages (JSP) document or tag file in XML syntax does not have it.
* Set the value of the `pageEncoding`
attribute of the page directive to "`UTF-8`". The `page` directive and
the `pageEncoding` attribute are added if they don’t exist already.
@@ -9823,13 +9819,13 @@ pass to `ServletResponse.setContentType()`, determined as described in
* Add the `jsp:id` attribute (see
<>).
-==== JSP Pages or Tag Files in JSP Syntax
+==== Jakarta Pages (JSP) or Tag Files in Standard Syntax
-The XML view of a JSP page or tag file
+The XML view of a Jakarta Pages (JSP) page or tag file
written in standard syntax is defined by the following transformation:
-* Expand all include directives into the JSP
-content they include. See <> for the
+* Expand all include directives into the Jakarta Pages (JSP)
+content they include. See <> for the
semantics of mixing XML and standard syntax content.
* Add a `jsp:root` element as the root, with
appropriate `xmlns:jsp` attribute, and convert the `taglib` directive
@@ -9839,25 +9835,25 @@ expressions into valid XML elements as described in
<> and the following sections.
* Convert request-time attribute expressions
as in <>.
-* Convert JSP quotations to XML quotations.
+* Convert Jakarta Pages (JSP) quotations to XML quotations.
* Create `jsp:text` elements for all template
text.
* Add the `jsp:id` attribute (see <>).
-Note that the XML view of a JSP page or tag
-file has no `DOCTYPE` information; see <>.
+Note that the XML view of a Jakarta Pages (JSP) page or tag
+file has no `DOCTYPE` information; see <>.
A quick overview of the transformation is
shown in <<_XML_View_Transformations>>:
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[cols="30,70",options="header"]
[%breakable]
[[_XML_View_Transformations]]
.XML View Transformations
|===
-|JSP element
+|Jakarta Pages (JSP) element
|XML view
|`<%-- comment --%>`
@@ -9915,10 +9911,10 @@ Add `jsp:id.` [tag files only]
In more detail:
-==== JSP Comments
+==== Jakarta Pages (JSP) Comments
-JSP comments (of the form `<%-- comment --%>`) are not
-passed through to the XML view of a JSP page.
+Jakarta Pages (JSP) comments (of the form `<%-- comment --%>`) are not
+passed through to the XML view of a Jakarta Pages (JSP) page.
==== The page Directive
@@ -9953,7 +9949,7 @@ A taglib directive of the form
----
is translated into an `xmlns:prefix`
-attribute on the root of the JSP document, with a value that depends on
+attribute on the root of the Jakarta Pages (JSP) document, with a value that depends on
`uriValue`. If `uriValue` is a relative path, then the value used is
`urn:jsptld:` `uriValue` ; otherwise, the `uriValue` is used directly.
@@ -9965,7 +9961,7 @@ A taglib directive of the form
----
is translated into an `xmlns:prefix`
-attribute on the root of the JSP document, with a value of the form
+attribute on the root of the Jakarta Pages (JSP) document, with a value of the form
`urn:jsptagdir:` `tagDirValue`.
==== The include Directive
@@ -9977,7 +9973,7 @@ An include directive of the form
<%@ include file="value" %>
----
-is expanded into the JSP content indicated by
+is expanded into the Jakarta Pages (JSP) content indicated by
`value`. This is done to allow for validation of the page.
==== Declarations
@@ -10010,7 +10006,7 @@ instead say:
==== Scriptlets
Scriptlets are translated into a
-`jsp:scriptlet` element. In the XML document corresponding to JSP pages,
+`jsp:scriptlet` element. In the XML document corresponding to a Jakarta Pages (JSP) page,
directives are represented using the syntax:
[source,jsp]
@@ -10020,7 +10016,7 @@ directives are represented using the syntax:
==== Expressions
-In the XML document corresponding to JSP
+In the XML document corresponding to Jakarta Pages (JSP)
pages, directives are represented using the `jsp:expression` element:
[source,jsp]
@@ -10038,9 +10034,9 @@ conventions and the syntax of request-time attribute expressions.
Request-time attribute expressions are of the
form `<%= expression %>`. Although this syntax is consistent with the
-syntax used elsewhere in a JSP page, it is not a legal XML syntax. The
+syntax used elsewhere in a Jakarta Pages (JSP) page, it is not a legal XML syntax. The
XML mapping for these expressions is into values of the form `%=
-expression %`, where the JSP specification quoting convention has been
+expression %`, where the Jakarta Pages (JSP) specification quoting convention has been
converted to the XML quoting convention.
Request-time attribute values can also be
@@ -10063,7 +10059,7 @@ combined.
illustrates these rules. Assume the EL expression `${foo}` evaluates to `[bar]`
and that EL is enabled for this translation unit.
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[cols="30,30,30",options="header"]
[%breakable]
[[_XML_View_of_an_Escaped_EL_Expression_in_a_Request_time_Attribute_Value]]
@@ -10114,11 +10110,11 @@ syntax, where `${` is simply substituted with `#{`.
==== Template Text and XML Elements
-All text that is uninterpreted by the JSP
+All text that is uninterpreted by the Jakarta Pages (JSP)
translator is converted into the body for a `jsp:text` element. As a
consequence no XML elements of the form described in
<> will appear in the XML view of a
-JSP page written in JSP syntax.
+Jakarta Pages (JSP) page written in standard syntax.
Because `\\` is not an escape sequence within
template text in the standard syntax, no special transformation needs to
@@ -10131,7 +10127,7 @@ expression `${foo}` evaluates to `[bar]` and that EL is enabled for this
translation unit. The same rules apply for the `\#{expr}` syntax, where `${`
is simply substituted with `\#{`.
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[cols="30,30,30",options="header"]
[%breakable]
[[_XML_View_of_an_Escaped_EL_Expression_in_Template_Text]]
@@ -10166,12 +10162,12 @@ is simply substituted with `\#{`.
==== The jsp:id Attribute
-A JSP container must support a `jsp:id`
-attribute. This attribute can only be present in the XML view of a JSP
+A Jakarta Pages (JSP) container must support a `jsp:id`
+attribute. This attribute can only be present in the XML view of a Jakarta Pages (JSP)
page and can be used to improve the quality of translation time error
messages.
-The XML view of any JSP page will have an
+The XML view of any Jakarta Pages (JSP) page will have an
additional `jsp:id` attribute added to all XML elements. This attribute
is given a value that is unique over all elements in the XML view. The
prefix for the `id` attribute need not be "`jsp`" but it must map to
@@ -10238,16 +10234,16 @@ is translated into an element of the form:
----
-=== Validating an XML View of a JSP page
+=== Validating an XML View of a Jakarta Pages (JSP) page
-The XML view of a JSP page is a
+The XML view of a Jakarta Pages (JSP) page is a
namespace-aware document and it cannot be validated against a DTD except
in the most simple cases. To reduce confusion and possible unintended
-performance consequences, the XML view of a JSP page will not include a
+performance consequences, the XML view of a Jakarta Pages (JSP) page will not include a
`DOCTYPE`.
There are several mechanisms that are aware
-of namespaces that can be used to do validation of XML views of JSP
+of namespaces that can be used to do validation of XML views of Jakarta Pages (JSP)
pages. The most popular mechanism is the W3C XML Schema language, but
others are also suited, including some very simple ones that may check,
for example, that only some elements are being used, or, inversely, that
@@ -10255,27 +10251,27 @@ they are not used. The `TagLibraryValidator` for a tag library permits
encapsulating this knowledge with a tag library.
The `TagLibraryValidator` acts on the XML
-view of the JSP page. If the page was authored in JSP syntax, that view
+view of the Jakarta Pages (JSP) page. If the page was authored in standard syntax, that view
does not provide any detail on template data (all being grouped inside
-jsp:text elements), but fine detail can be described when using JSP
-documents. Similarly, when applying an XSLT transformation to a JSP document,
+jsp:text elements), but fine detail can be described when using Jakarta Pages (JSP)
+documents. Similarly, when applying an XSLT transformation to a Jakarta Pages (JSP) document,
XML fragments will be plainly visible, while the content of `jsp:text`
elements will not.
=== Examples
This section presents various examples of XML
-Views. The first shows a JSP page in XML syntax that includes XML
-fragments. The second shows a JSP page in JSP syntax and its mapping to
+Views. The first shows a Jakarta Pages (JSP) page in XML syntax that includes XML
+fragments. The second shows a Jakarta Pages (JSP) page in standard syntax and its mapping to
XML syntax. The three following examples illustrate the semantics of
cross-syntax translation-time includes and the effect on the XML View.
-==== A JSP Document
+==== A Jakarta Pages (JSP) Document
-This is an example of a very simple JSP
+This is an example of a very simple Jakarta Pages (JSP)
document that has some template XML elements. This particular example
describes a table that is a collection of 3 rows, with numeric values 1,
-2, 3. The JSP Standard Tag Library is being used:
+2, 3. The Jakarta Standard Tag Library is being used:
[source,jsp]
----
@@ -10289,12 +10285,12 @@ describes a table that is a collection of 3 rows, with numeric values 1,
----
-==== A JSP Page and its Corresponding XML View
+==== A Jakarta Pages (JSP) Page and its Corresponding XML View
-Here is an example of mapping between JSP and
+Here is an example of mapping between standard and
XML syntax.
-For this JSP page:
+For this Jakarta Pages (JSP) page:
[source,jsp]
----
@@ -10344,7 +10340,7 @@ xmlns:temp="urn:jsptld:/WEB-INF/tlds/my.tld">
==== Clearing Out Default Namespace on Include
This example illustrates the need to clear
-out the default namespace when doing a translation-time include of a JSP
+out the default namespace when doing a translation-time include of a Jakarta Pages (JSP)
document:
[source,jsp]
@@ -10361,7 +10357,7 @@ document:
----
-The resulting XML View for these two JSP
+The resulting XML View for these two Jakarta Pages (JSP)
documents is:
[source,xml]
@@ -10475,16 +10471,16 @@ pages is:
= Part II
-The next chapter provides detail specification information on some portions of the JSP specification that
-are intended for JSP Container Vendors, JSP Page authors, and JSP Tag Library authors.
+The next chapter provides detail specification information on some portions of the Jakarta Pages (JSP) specification that
+are intended for Jakarta Pages (JSP) Container Vendors, Jakarta Pages (JSP) Page authors, and Jakarta Pages (JSP) Tag Library authors.
The chapters is normative.
The chapter is:
-* JSP Container
+* Jakarta Pages (JSP) Container
-JSP Container Vendors, JSP Page authors, and JSP Tag
+Jakarta Pages (JSP) Container Vendors, Jakarta Pages (JSP) Page authors, and Jakarta Pages (JSP) Tag
Library authors should also read:
* `jakarta.servlet.jsp` Javadoc
@@ -10495,116 +10491,116 @@ These external resources are considered normative within the context of this spe
// Table, figure numbering etc
:table-number: 0
-== JSP Container{counter2:jsp-chapter}
+== Jakarta Pages (JSP) Container{counter2:jsp-chapter}
This chapter describes the contracts
-between a JSP container and a JSP page, including the precompilation
+between a Jakarta Pages (JSP) container and a Jakarta Pages (JSP) page, including the precompilation
protocol and debugging support requirements.
The information in this chapter is
-independent of the Scripting Language used in the JSP page.
+independent of the Scripting Language used in the Jakarta Pages (JSP) page.
<> describes information specific to when the `language`
attribute of the `page` directive has `java` as its value.
-JSP page implementation classes should use
+Jakarta Pages (JSP) page implementation classes should use
the `JspFactory` and `PageContext` classes to take advantage of
platform-specific implementations.
-=== JSP Page Model
+=== Jakarta Pages (JSP) Page Model
-A JSP page is represented at execution time by
-a JSP page implementation object and is executed by a JSP container. The
-JSP page implementation object is a servlet. The JSP container delivers
-requests from a client to a JSP page implementation object and responses
-from the JSP page implementation object to the client.
+A Jakarta Pages (JSP) page is represented at execution time by
+a Jakarta Pages (JSP) page implementation object and is executed by a Jakarta Pages (JSP) container. The
+Jakarta Pages (JSP) page implementation object is a servlet. The Jakarta Pages (JSP) container delivers
+requests from a client to a Jakarta Pages (JSP) page implementation object and responses
+from the Jakarta Pages (JSP) page implementation object to the client.
-The JSP page describes how to create a
+The Jakarta Pages (JSP) page describes how to create a
response object from a request object for a given protocol, possibly
-creating and/or using some other objects in the process . A JSP page may
-also indicate how some events are to be handled. In JSP 4.1 only `init`
+creating and/or using some other objects in the process . A Jakarta Pages (JSP) page may
+also indicate how some events are to be handled. In Jakarta Pages (JSP) 4.1 only `init`
and `destroy` events are allowed events.
-The JSP container must render a JSP page for the HTTP methods GET and POST
+The Jakarta Pages (JSP) container must render a Jakarta Pages (JSP) page for the HTTP methods GET and POST
with identical responses.
-The response for a HEAD request to a JSP page must be identical to the response
+The response for a HEAD request to a Jakarta Pages (JSP) page must be identical to the response
for a GET request minus the response body.
-The behavior of the JSP container is undefined for other methods.
+The behavior of the Jakarta Pages (JSP) container is undefined for other methods.
==== Protocol Seen by the Web Server
-The JSP container locates the appropriate
-instance of the JSP page implementation class and delivers requests to
-it using the servlet protocol. A JSP container may need to create such a
-class dynamically from the JSP page source before delivering request and
+The Jakarta Pages (JSP) container locates the appropriate
+instance of the Jakarta Pages (JSP) page implementation class and delivers requests to
+it using the servlet protocol. A Jakarta Pages (JSP) container may need to create such a
+class dynamically from the Jakarta Pages (JSP) page source before delivering request and
response objects to it.
The `Servlet` class defines the contract
-between the JSP container and the JSP page implementation class. When
+between the Jakarta Pages (JSP) container and the Jakarta Pages (JSP) page implementation class. When
the HTTP protocol is used, the contract is described by the
-`HttpServlet` class. Most JSP pages use the HTTP protocol, but other
+`HttpServlet` class. Most Jakarta Pages (JSP) use the HTTP protocol, but other
protocols are allowed by this specification.
-The JSP container automatically makes a
-number of server-side objects available to the JSP page implementation
+The Jakarta Pages (JSP) container automatically makes a
+number of server-side objects available to the Jakarta Pages (JSP) page implementation
object . See <>.
-===== Protocol Seen by the JSP Page Author
+===== Protocol Seen by the Jakarta Pages (JSP) Page Author
-The JSP specification defines the contract
-between the JSP container and the JSP page author. This contract defines
-the assumptions an author can make for the actions described in the JSP
+The Jakarta Pages (JSP) specification defines the contract
+between the Jakarta Pages (JSP) container and the Jakarta Pages (JSP) page author. This contract defines
+the assumptions an author can make for the actions described in the Jakarta Pages (JSP)
page.
The main portion of this contract is the
-`_jspService` method that is generated automatically by the JSP
-container from the JSP page. The details of this contract are provided
+`_jspService` method that is generated automatically by the Jakarta Pages (JSP)
+container from the Jakarta Pages (JSP) page. The details of this contract are provided
in <>.
-The contract also describes how a JSP author
+The contract also describes how a Jakarta Pages (JSP) author
can indicate what actions will be taken when the `init` and `destroy`
-methods of the page implementation occur. In JSP 4.1 this is done by
+methods of the page implementation occur. In Jakarta Pages (JSP) 4.1 this is done by
defining methods with the names `jspInit` and `jspDestroy` in a
-declaration scripting element in the JSP page. The `jspInit` method, if
+declaration scripting element in the Jakarta Pages (JSP) page. The `jspInit` method, if
present, will be called to prepare the page before the first request is
-delivered. Similarly a JSP container can reclaim resources used by a JSP
-page when a request is not being serviced by the JSP page by invoking
+delivered. Similarly a Jakarta Pages (JSP) container can reclaim resources used by a Jakarta Pages (JSP)
+page when a request is not being serviced by the Jakarta Pages (JSP) page by invoking
its `jspDestroy` method, if present.
-A JSP page author may not (re)define servlet
+A Jakarta Pages (JSP) page author may not (re)define servlet
methods through a declaration scripting element.
-The JSP specification reserves names for
+The Jakarta Pages (JSP) specification reserves names for
methods and variables starting with `jsp`, `jsp`, `jspx`, and
`jspx`, in any combination of upper and lower case.
===== The HttpJspPage Interface
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
+Jakarta Pages (JSP) container and the Jakarta Pages (JSP) page author is aided by the requirement that
+the `Servlet` class corresponding to the Jakarta Pages (JSP) page must implement the
`jakarta.servlet.jsp.HttpJspPage` interface (or the
`jakarta.servlet.jsp.JspPage` interface if the protocol is not HTTP).
-[[Contracts_between_a_JSP_Page_and_a_JSP_Container]]
-.*Figure JSP.{jsp-chapter}-1* Contracts between a JSP Page and a JSP Container
+[[Contracts_between_a_Jakarta_Pages_Page_and_a_Jakarta_Pages_Container]]
+.*Figure Jakarta Pages (JSP).{jsp-chapter}-1* Contracts between a Jakarta Pages (JSP) Page and a Jakarta Pages (JSP) Container
image:sp-11.svg[image]
The involved contracts are shown in
-<>. We now revisit
+<>. We now revisit
this whole process in more detail.
-=== JSP Page Implementation Class
+=== Jakarta Pages (JSP) Page Implementation Class
-The JSP container creates a JSP page
-implementation class for each JSP page.
+The Jakarta Pages (JSP) container creates a Jakarta Pages (JSP) page
+implementation class for each Jakarta Pages (JSP) page.
-The name of the JSP page implementation class
+The name of the Jakarta Pages (JSP) page implementation class
is implementation dependent.
-The JSP Page implementation object belongs to
+The Jakarta Pages (JSP) page implementation object belongs to
an implementation-dependent named package. The package used may vary
-between one JSP and another, so minimal assumptions should be made.
+between one Jakarta Pages (JSP) and another, so minimal assumptions should be made.
As of JSP 2.0, it is illegal to refer to any
classes from the unnamed (a.k.a. default) package. This will result in a
@@ -10612,98 +10608,98 @@ translation error. This restriction also applies for all other
cases where classes are referenced, such as when specifying the class
name for a tag in a TLD.
-The JSP container may create the
-implementation class for a JSP page, or a superclass may be provided by
-the JSP page author through the use of the `extends` attribute in the
+The Jakarta Pages (JSP) container may create the
+implementation class for a Jakarta Pages (JSP) page, or a superclass may be provided by
+the Jakarta Pages (JSP) page author through the use of the `extends` attribute in the
`page` directive.
The extends mechanism is available for
sophisticated users. It should be used with extreme care as it restricts
-decisions that a JSP container can make. It may restrict efforts to
+decisions that a Jakarta Pages (JSP) container can make. It may restrict efforts to
improve performance, for example.
-The JSP page implementation class will
+The Jakarta Pages (JSP) page implementation class will
implement `jakarta.servlet.Servlet` and requests are delivered to the
class as per the rules in the Servlet 6.2 specification.
-A JSP page implementation class may depend on
-support classes. If the JSP page implementation class is packaged into a
+A Jakarta Pages (JSP) page implementation class may depend on
+support classes. If the Jakarta Pages (JSP) page implementation class is packaged into a
WAR, any dependent classes will have to be included so it will be
-portable across all JSP containers.
+portable across all Jakarta Pages (JSP) containers.
-A JSP page author writes a JSP page expecting
+A Jakarta Pages (JSP) page author writes a Jakarta Pages (JSP) page expecting
that the client and the server will communicate using a certain
-protocol. The JSP container must guarantee that requests to and
-responses from the page use that protocol. Most JSP pages use HTTP, and
+protocol. The Jakarta Pages (JSP) container must guarantee that requests to and
+responses from the page use that protocol. Most Jakarta Pages (JSP) use HTTP, and
their implementation classes must implement the `HttpJspPage` interface,
which extends `JspPage`. If the protocol is not HTTP, then the class
will implement an interface that extends `JspPage`.
==== API Contracts
-The contract between the JSP container and a
-Java class implementing a JSP page corresponds to the `Servlet`
+The contract between the Jakarta Pages (JSP) container and a
+Java class implementing a Jakarta Pages (JSP) page corresponds to the `Servlet`
interface. Refer to the Servlet 6.2 specification for details.
The responsibility for adhering to this
-contract rests on the JSP container implementation if the JSP page does
+contract rests on the Jakarta Pages (JSP) container implementation if the Jakarta Pages (JSP) page does
not use the `extends` attribute of the `jsp` directive. If the `extends`
-attribute of the `jsp` directive is used, the JSP page author must
+attribute of the `jsp` directive is used, the Jakarta Pages (JSP) page author must
guarantee that the superclass given in the extends attribute supports
this contract.[[a2917]]
-[caption='*Table JSP.{jsp-chapter}-{counter:table-number}* ']
+[caption='*Table Jakarta Pages (JSP).{jsp-chapter}-{counter:table-number}* ']
[cols="55,45",options="header"]
[%breakable]
-[[How_the_JSP_Container_Processes_JSP_Pages]]
-.How the JSP Container Processes JSP Pages
+[[How_the_Jakarta_Pages_Container_Processes_Jakarta_Pages_Pages]]
+.How the Jakarta Pages (JSP) Container Processes Jakarta Pages (JSP)
|===
-|Methods the JSP Container Invokes
+|Methods the Jakarta Pages (JSP) Container Invokes
|Comments
|`void jspInit()`
-|Method is optionally defined in JSP page. +
-Method is invoked when the JSP page is
+|Method is optionally defined in Jakarta Pages (JSP) page. +
+Method is invoked when the Jakarta Pages (JSP) page is
initialized. +
When method is called all the methods in
`servlet`, including `getServletConfig` are available.
|`void jspDestroy()`
-|Method is optionally defined in JSP page. +
+|Method is optionally defined in Jakarta Pages (JSP) page. +
Method is invoked before destroying the page.
|`void _jspService(,
) throws
IOException, ServletException`
-|Method may *not* be defined in JSP page. +
-The JSP container automatically generates
-this method, based on the contents of the JSP page. +
+|Method may *not* be defined in Jakarta Pages (JSP) page. +
+The Jakarta Pages (JSP) container automatically generates
+this method, based on the contents of the Jakarta Pages (JSP) page. +
Method invoked at each client request.
|===
==== Request and Response Parameters
-As shown in <> the methods
-in the contract between the JSP container and the JSP page require
+As shown in <> the methods
+in the contract between the Jakarta Pages (JSP) container and the Jakarta Pages (JSP) page require
request and response parameters.
The formal type of the request parameter
(which this specification calls ``) is an
interface that extends `jakarta.servlet.ServletRequest`. The interface
-must define a protocol-dependent request contract between the JSP
-container and the class that implements the JSP page.
+must define a protocol-dependent request contract between the Jakarta Pages (JSP)
+container and the class that implements the Jakarta Pages (JSP) page.
Likewise, the formal type of the response
parameter (which this specification calls ``)
is an interface that extends `jakarta.servlet.ServletResponse`. The
interface must define a protocol-dependent response contract between the
-JSP container and the class that implements the JSP page.
+Jakarta Pages (JSP) container and the class that implements the Jakarta Pages (JSP) page.
The request and response interfaces together
-describe a protocol-dependent contract between the JSP container and the
-class that implements the JSP page. The HTTP contract is defined by the
+describe a protocol-dependent contract between the Jakarta Pages (JSP) container and the
+class that implements the Jakarta Pages (JSP) page. The HTTP contract is defined by the
`jakarta.servlet.http.HttpServletRequest` and
`jakarta.servlet.http.HttpServletResponse` interfaces.
@@ -10713,30 +10709,30 @@ methods, but cannot describe syntactically the methods involving the
protocols that extend `JspPage` can, just as `HttpJspPage` describes
them for the HTTP protocol.
-JSP containers that conform to this
-specification (in both JSP page implementation classes and JSP container
+Jakarta Pages (JSP) containers that conform to this
+specification (in both Jakarta Pages (JSP) page implementation classes and Jakarta Pages (JSP) container
runtime) must support the `request` and `response` interfaces for the
HTTP protocol as described in this section.
==== Omitting the extends Attribute
If the `extends` attribute of the `page`
-directive (see Section <>) in a JSP page is not
-used, the JSP container can generate any class that satisfies the
-contract described in <>
-when it transforms the JSP page.
+directive (see Section <>) in a Jakarta Pages (JSP) page is not
+used, the Jakarta Pages (JSP) container can generate any class that satisfies the
+contract described in <>
+when it transforms the Jakarta Pages (JSP) page.
In the following code examples, <>
illustrates a generic HTTP superclass named `ExampleHttpSuper`.
-<> shows a subclass named
+<> shows a subclass named
`_jsp1344` that extends `ExampleHttpSuper` and is the class generated
-from the JSP page. By using separate `_jsp1344` and `ExampleHttpSuper`
-classes, the JSP page translator does not need to discover whether the
-JSP page includes a declaration with `jspInit` or `jspDestroy`. This
+from the Jakarta Pages (JSP) page. By using separate `_jsp1344` and `ExampleHttpSuper`
+classes, the Jakarta Pages (JSP) page translator does not need to discover whether the
+Jakarta Pages (JSP) page includes a declaration with `jspInit` or `jspDestroy`. This
significantly simplifies the implementation.
[[A_Generic_HTTP_Superclass]]
-.*Code Example JSP.11-1* A Generic HTTP Superclass
+.*Code Example Jakarta Pages (JSP).11-1* A Generic HTTP Superclass
[source,java]
----
imports jakarta.servlet.*;
@@ -10744,7 +10740,7 @@ imports jakarta.servlet.http.*;
imports jakarta.servlet.jsp.*;
/**
- * An example of a superclass for an HTTP JSP class
+ * An example of a superclass for an HTTP Jakarta Pages (JSP) class
*/
abstract class ExampleHttpSuper implements HttpJspPage {
@@ -10767,7 +10763,7 @@ abstract class ExampleHttpSuper implements HttpJspPage {
// This one is not final so it can be overridden by a more precise method
public String getServletInfo() {
- return "A Superclass for an HTTP JSP"; // maybe better?
+ return "A Superclass for an HTTP Jakarta Pages (JSP)"; // maybe better?
}
final public void destroy() {
@@ -10788,7 +10784,7 @@ abstract class ExampleHttpSuper implements HttpJspPage {
}
/**
- * abstract method to be provided by the JSP processor in the subclass
+ * abstract method to be provided by the Jakarta Pages (JSP) processor in the subclass
* Must be defined in subclass.
*/
abstract public void _jspService(HttpServletRequest request,
@@ -10796,8 +10792,8 @@ abstract class ExampleHttpSuper implements HttpJspPage {
}
----
-[[The_Java_Class_Generated_From_a_JSP_Page]]
-.*Code Example JSP.11-2* The Java Class Generated From a JSP Page
+[[The_Java_Class_Generated_From_a_Jakarta_Pages_Page]]
+.*Code Example Jakarta Pages (JSP).11-2* The Java Class Generated From a Jakarta Pages (JSP) Page
[source,java]
----
imports jakarta.servlet.*;
@@ -10805,10 +10801,10 @@ imports jakarta.servlet.http.*;
imports jakarta.servlet.jsp.*;
/**
- * An example of a class generated for a JSP.
+ * An example of a class generated for a Jakarta Pages (JSP).
*
* The name of the class is unpredictable.
- * We are assuming that this is an HTTP JSP page (like almost all are)
+ * We are assuming that this is an HTTP Jakarta Pages (JSP) page (like almost all are)
*/
class _jsp1344 extends ExampleHttpSuper {
@@ -10821,8 +10817,8 @@ class _jsp1344 extends ExampleHttpSuper {
public void jspDestroy() {...}
// The next method is generated automatically by the
- // JSP processor.
- // body of JSP page
+ // Jakarta Pages (JSP) processor.
+ // body of Jakarta Pages (JSP) page
public void _jspService(HttpServletRequest request,
HttpServletResponse response)
@@ -10839,13 +10835,13 @@ class _jsp1344 extends ExampleHttpSuper {
==== Using the extends Attribute
-If the JSP page author uses `extends`, the
+If the Jakarta Pages (JSP) page author uses `extends`, the
generated class is identical to the one shown in
-<>, except that the class
+<>, except that the class
name is the one specified in the `extends` attribute.
-The contract on the JSP page implementation
-class does not change. The JSP container should check (usually through
+The contract on the Jakarta Pages (JSP) page implementation
+class does not change. The Jakarta Pages (JSP) container should check (usually through
reflection) that the provided superclass:
* Implements `HttpJspPage` if the protocol is
@@ -10854,7 +10850,7 @@ HTTP, or `JspPage` otherwise.
interface are declared final.
Additionally, it is the responsibility of the
-JSP page author that the provided superclass satisfies:
+Jakarta Pages (JSP) page author that the provided superclass satisfies:
* The `service` method of the servlet API
invokes the `_jspService` method.
@@ -10863,13 +10859,13 @@ configuration, makes it available via `getServletConfig`, then invokes
`jspInit`.
* The `destroy` method invokes `jspDestroy`.
-A JSP container may give a fatal translation
+A Jakarta Pages (JSP) container may give a fatal translation
error if it detects that the provided superclass does not satisfy these
-requirements, but most JSP containers will not check them.
+requirements, but most Jakarta Pages (JSP) containers will not check them.
=== Buffering
-The JSP container buffers data (if the jsp
+The Jakarta Pages (JSP) container buffers data (if the jsp
directive specifies it using the buffer attribute) as it is sent from
the server to the client. Headers are not sent to the client until the
first flush method is invoked. Therefore, it is possible to call methods
@@ -10898,7 +10894,7 @@ _jspService( request, response) {
false,
PageContext.DEFAULT`BUFFER,
false);
- JSPWriter out = pageContext.getOut();
+ Jakarta Pages (JSP)Writer out = pageContext.getOut();
// ...
// ... the body goes here using "out"
// ...
@@ -10916,34 +10912,34 @@ can still be used in a scriptlet in a `.jsp` file, by invoking
=== Precompilation
-A JSP page that is using the HTTP protocol
-will receive HTTP requests. JSP 4.1 compliant containers must support a
+A Jakarta Pages (JSP) page that is using the HTTP protocol
+will receive HTTP requests. Jakarta Pages (JSP) 4.1 compliant containers must support a
simple precompilation protocol, as well as some basic reserved parameter
names. Note that the precompilation protocol is related but not the same
-as the notion of compiling a JSP page into a `Servlet` class
-(<>).
+as the notion of compiling a Jakarta Pages (JSP) page into a `Servlet` class
+(<>).
==== Request Parameter Names
All request parameter names that start with
-the prefix `jsp` are reserved by the JSP specification and should not be
+the prefix `jsp` are reserved by the Jakarta Pages (JSP) specification and should not be
used by any user or implementation except as indicated by the
specification.
-All JSPs pages should ignore (not depend on)
+All Jakarta Pages (JSP) pages should ignore (not depend on)
any parameter that starts with `jsp_`.
==== Precompilation Protocol
-A request to a JSP page that has a request
+A request to a Jakarta Pages (JSP) page that has a request
parameter with name `jsp_precompile` is a precompilation request. The
`jsp_precompile` parameter may have no value, or may have values `true`
or `false`. In all cases, the request should not be delivered to the
-JSP page.
+Jakarta Pages (JSP) page.
The intention of the precompilation request
-is that of a suggestion to the JSP container to precompile the JSP page
-into its JSP page implementation class. The suggestion is conveyed by
+is that of a suggestion to the Jakarta Pages (JSP) container to precompile the Jakarta Pages (JSP) page
+into its Jakarta Pages (JSP) page implementation class. The suggestion is conveyed by
giving the parameter the value `true` or no value, but note that the
request can be ignored.
@@ -10968,23 +10964,23 @@ error; 500 (Server error).
=== Debugging Requirements
The Jakarta Debugging Support for Other Languages specification provides
-the JSP Compiler with a standard format to convey source map debugging
+the Jakarta Pages (JSP) Compiler with a standard format to convey source map debugging
information to tools such as debuggers. See
`https://jakarta.ee/specifications/debugging/2.0/` for details.
-JSP 4.1 containers are required to provide debugging support for JSP pages
+Jakarta Pages (JSP) 4.1 containers are required to provide debugging support for Jakarta Pages (JSP)
and tag files written in either standard or XML syntax.
-The JSP compiler must produce `.class` files
+The Jakarta Pages (JSP) compiler must produce `.class` files
with a `SourceDebugExtension` attribute, mapping each line or lines of
-JSP code to the corresponding generated line or lines of Java code. For
+Jakarta Pages (JSP) code to the corresponding generated line or lines of Java code. For
both pages and tag files, the stratum that maps to the original source
should be named `JSP` in the Source Debug Extension (this stratum name
-is reserved for use by the JSP specification). This stratum should be
+is reserved for use by the Jakarta Pages (JSP) specification). This stratum should be
specified as the default, unless the page or tag file was generated from
some other source.
-The exact mechanism for causing the JSP
+The exact mechanism for causing the Jakarta Pages (JSP)
compiler to produce source map debugging information is
implementation-dependent.
@@ -10993,12 +10989,12 @@ implementation-dependent.
The following is a set of non-normative
guidelines for generating high quality line number mappings. The
guidelines are presented to help produce a consistent debugging
-experience for page authors across containers. Where possible the JSP
+experience for page authors across containers. Where possible the Jakarta Pages (JSP)
container should generate line number mappings as follows:
-. A breakpoint on a JSP
+. A breakpoint on a Jakarta Pages (JSP)
line causes execution to stop before any Java code which amounts to a
-translation of the JSP line is executed (for one possible exception, see
+translation of the Jakarta Pages (JSP) line is executed (for one possible exception, see
(5). Note that
given the LineInfo Composition Algorithm (see Jakarta Debugging Support
for Other Languages specification), it
@@ -11006,26 +11002,26 @@ is acceptable for the mappings to include one or more Java lines which
are never translated into executable byte code, as long as at least one
of them does.
. It is permitted for two or more lines of
-JSP to include the same Java lines in their mappings.
-. If a line of JSP has no manifestation in
+Jakarta Pages (JSP) to include the same Java lines in their mappings.
+. If a line of a Jakarta Pages (JSP) page has no manifestation in
the Java source other than white-space preserving source, it should not
be mapped.
-* The following standard syntax JSP entities
+* The following standard syntax Jakarta Pages (JSP) entities
should not be mapped to generated code. These entities either have no
manifestation in the generated Java code (e.g. comments), or are not
manifest in such a way that it allows the debugged process to stop (e.g.
the page directive import):
-** JSP comments
+** Jakarta Pages (JSP) comments
** Directives
-* The following XML syntax JSP entities
+* The following XML syntax Jakarta Pages (JSP) entities
should not be mapped to generated code. These entities frequently have
no manifestation in the generated Java code.
** ``
** ``
. Declarations and scriptlets (standard or
-XML JSP). Lines in these constructs should preserve a one-to-one mapping
+XML Jakarta Pages (JSP)). Lines in these constructs should preserve a one-to-one mapping
with the corresponding generated code lines. Empty lines and comment
lines are not mapped.
. For scriptlets,
@@ -11036,7 +11032,7 @@ corresponding Java code.
+
If the line starts with template text, the
Java code which handles it may be excluded from the mappings if this
-would cause the debugger to stop before the apparent execution of JSP
+would cause the debugger to stop before the apparent execution of Jakarta Pages (JSP)
lines preceding the line in question. For example:
+
....
@@ -11068,7 +11064,7 @@ mapping 101 to 202, 203 etc. may result in more intuitive behavior of
the debugger. +
+
For scriptlets that contain more than one line, there should be a
-one-to-one mapping from JSP to Java lines, and the mapping should start
+one-to-one mapping from Jakarta Pages (JSP) page to Java lines, and the mapping should start
at the first Java code that is not whitespace or comments. Therefore, a
line that contains only the open scriptlet delimeter is not mapped.
@@ -11077,7 +11073,7 @@ line that contains only the open scriptlet delimeter is not mapped.
. Scriptlet expressions
and EL expressions in attribute values. The source line mappings should
include any Java source lines that deal with the evaluation of the
-rtexpr value as well as source that deals with the JSP action.
+rtexpr value as well as source that deals with the Jakarta Pages (JSP) action.
. Standard or custom actions.
* Empty tags and start tags special case: The
`jsp:params` action typically has no manifestation and should not be
@@ -11091,7 +11087,7 @@ lines should include the first sequential line which deals with either
the tag or the attribute evaluation in order to meet
(1)
* Closing tags frequently do not have a
-manifestation in the Java source, but sometimes do. In case a JSP line
+manifestation in the Java source, but sometimes do. In case a Jakarta Pages (JSP) line
contains only a closing tag, the line may be mapped to whitespace
preserving Java source if it has no semantic translation. This will
avoid a confusing user experience where it is sometimes possible to set
@@ -11106,45 +11102,45 @@ Appendices A, C, and D are non-normative.
The Appendices are:
-* Appendix A - Packaging JSP pages
+* Appendix A - Packaging Jakarta Pages (JSP)
* Appendix B - Page Character Encoding Detection Algorithm
* Appendix C - Changes
* Appendix D - Glossary of terms
[appendix]
-== Packaging JSP Pages
+== Packaging Jakarta Pages (JSP)
This appendix shows two simple examples
-of packaging a JSP page into a WAR for delivery into a Web container. In
-the first example, the JSP page is delivered in source form. This is
-likely to be the most common example. In the second example the JSP page
-is compiled into a servlet that uses only Servlet 6.2 and JSP 4.1 API
+of packaging a Jakarta Pages (JSP) page into a WAR for delivery into a Web container. In
+the first example, the Jakarta Pages (JSP) page is delivered in source form. This is
+likely to be the most common example. In the second example the Jakarta Pages (JSP) page
+is compiled into a servlet that uses only Servlet 6.2 and Jakarta Pages (JSP) 4.1 API
calls; the servlet is then packaged into a WAR with a deployment
-descriptor such that it looks as the original JSP page to any client.
+descriptor such that it looks as the original Jakarta Pages (JSP) page to any client.
This appendix is non normative. Actually,
strictly speaking, the appendix relates more to the Servlet 6.2
-capabilities than to the JSP 4.1 capabilities. The appendix is included
-here as this is a feature that JSP page authors and JSP page authoring
+capabilities than to the Jakarta Pages (JSP) 4.1 capabilities. The appendix is included
+here as this is a feature that Jakarta Pages (JSP) page authors and Jakarta Pages (JSP) page authoring
tools are interested in.
-=== A Very Simple JSP Page
+=== A Very Simple Jakarta Pages (JSP) Page
-We start with a very simple JSP page
+We start with a very simple Jakarta Pages (JSP) page
`HelloWorld.jsp`.
[source,jsp]
----
- <%@ page info="Example JSP pre-compiled" %>
+ <%@ page info="Example Jakarta Pages (JSP) pre-compiled" %>
Hello World
----
-=== The JSP Page Packaged as Source in a WAR File
+=== The Jakarta Pages (JSP) Page Packaged as Source in a WAR File
-The JSP page can be packaged into a WAR file
-by just placing it at location `/HelloWorld.jsp` the default JSP page
+The Jakarta Pages (JSP) page can be packaged into a WAR file
+by just placing it at location `/HelloWorld.jsp` the default Jakarta Pages (JSP) page
extension mapping will pick it up. The `web.xml` is trivial:
[source,xml]
@@ -11158,14 +11154,14 @@ extension mapping will pick it up. The `web.xml` is trivial:
----
-=== The Servlet for the Compiled JSP Page
+=== The Servlet for the Compiled Jakarta Pages (JSP) Page
As an alternative, we will show how one can
-compile the JSP page into a servlet class to run in a JSP container.
+compile the Jakarta Pages (JSP) page into a servlet class to run in a Jakarta Pages (JSP) container.
-The JSP page is compiled into a servlet with
+The Jakarta Pages (JSP) page is compiled into a servlet with
some implementation dependent name `com.acme._jsp_HelloWorld_XXX_Impl`.
-The servlet code only depends on the JSP 4.1 and Servlet 6.2 APIs, as
+The servlet code only depends on the Jakarta Pages (JSP) 4.1 and Servlet 6.2 APIs, as
follows:
[source,java]
@@ -11224,7 +11220,7 @@ public class _jsp_HelloWorld_XXX_Impl
=== The Web Application Descriptor
-The servlet is made to look as a JSP page
+The servlet is made to look as a Jakarta Pages (JSP) page
with the following `web.xml`:
[source,xml]
@@ -11248,7 +11244,7 @@ with the following `web.xml`:
----
-=== The WAR for the Compiled JSP Page
+=== The WAR for the Compiled Jakarta Pages (JSP) Page
Finally everything is packaged together into
a WAR:
@@ -11257,7 +11253,7 @@ a WAR:
* `/WEB-INF/classes/com/acme/_jsp_HelloWorld_XXX_Impl.class`
Note that if the servlet class generated for
-the JSP page had depended on some support classes, they would have to be
+the Jakarta Pages (JSP) page had depended on some support classes, they would have to be
included in the WAR.
@@ -11266,27 +11262,27 @@ included in the WAR.
This appendix details the algorithm
containers are required to use in order to determine the character
-encoding for a JSP page or tag file. See <>
+encoding for a Jakarta Pages (JSP) page or tag file. See <>
for details on where this algorithm is
used. The algorithm is designed to maximize convenience to the page
author, while preserving backwards compatibility with previous versions
-of the JSP specification.
+of the Jakarta Pages (JSP) specification.
-=== Detection Algorithm for JSP pages
+=== Detection Algorithm for Jakarta Pages (JSP)
The following is a complete though
-unoptimized algorithm for determining the character encoding for a JSP
-file. JSP containers may use an optimized version of this algorithm, but
+unoptimized algorithm for determining the character encoding for a Jakarta Pages (JSP)
+file. Jakarta Pages (JSP) containers may use an optimized version of this algorithm, but
it must detect the same encoding as the algorithm in all cases.
-. Decide whether the source file is a JSP
-page in standard syntax or a JSP document in XML syntax.
+. Decide whether the source file is a Jakarta Pages (JSP)
+page in standard syntax or a Jakarta Pages (JSP) document in XML syntax.
.. If there is a `` element in a
`` that names this file, then if it has the value
-"`true`", the file is a JSP document, and if it has the value "`false`",
-the file is not a JSP document.
+"`true`", the file is a Jakarta Pages (JSP) document, and if it has the value "`false`",
+the file is not a Jakarta Pages (JSP) document.
.. Otherwise, if the file name has the
-extension "`jspx`", the file is a JSP document.
+extension "`jspx`", the file is a Jakarta Pages (JSP) document.
.. Otherwise, try to find a ``
element in the file.
... Determine the initial encoding from the
@@ -11297,18 +11293,18 @@ for all other cases, use the `UTF-*` or `UCS-*` encoding given in the
appendix.
... Read the file using the initial encoding
and search for a `` element. If the element is found and is
-the top element, the file is a JSP document in XML syntax
-.. Otherwise, the file is a JSP page in
+the top element, the file is a Jakarta Pages (JSP) document in XML syntax
+.. Otherwise, the file is a Jakarta Pages (JSP) page in
standard syntax.
. Reset the file.
-. If the file is a JSP page in standard syntax:
+. If the file is a Jakarta Pages (JSP) page in standard syntax:
+
3.1 If the file is not preceded by a BOM:
+
--
-.. Check whether there is a JSP configuration
+.. Check whether there is a Jakarta Pages (JSP) configuration
element `` whose URL pattern matches this file.
.. Read the file using the initial encoding
and search for a `pageEncoding` attribute in a page declaration. The
@@ -11351,12 +11347,12 @@ 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.
-. If the file is a JSP document in XML syntax, use these steps.
+. If the file is a Jakarta Pages (JSP) document in XML syntax, use these steps.
.. Determine the page character encoding as
described in appendix F.1 of the XML 1.0 specification. Note whether the
encoding was named in the encoding attribute of the XML prolog or just
derived from the initial bytes.
-.. Check whether there is a JSP configuration
+.. Check whether there is a Jakarta Pages (JSP) configuration
element `` whose URL pattern matches this file.
.. Read the file using the detected encoding
and search for a `pageEncoding` attribute in a ``
@@ -11377,7 +11373,7 @@ attribute, and the two name different encodings.
The following details the algorithm for
determining the character
-encoding for a tag file. JSP containers may
+encoding for a tag file. Jakarta Pages (JSP) containers may
use an optimized version
of this algorithm, but it must detect the
same encoding as the algorithm
@@ -11418,7 +11414,7 @@ by the BOM, and search for a pageEncoding attribute in a tag directive.
tag directive attribute whose encoding does not match the encoding
indicated by the BOM.
-. If the file is a JSP document in XML syntax, use these steps.
+. If the file is a Jakarta Pages (JSP) document in XML syntax, use these steps.
.. Determine the page character encoding as
described in appendix F.1 of the XML 1.0 specification.
.. Read the file using the detected encoding.
@@ -11427,9 +11423,9 @@ described in appendix F.1 of the XML 1.0 specification.
== Changes
This appendix lists the changes in the
-Jakarta Server Pages specification. This appendix is non-normative.
+Jakarta Pages specification. This appendix is non-normative.
-=== Changes between JSP 4.1 and JSP 4.0
+=== Changes between Jakarta Pages (JSP) 4.1 and Jakarta Pages (JSP) 4.0
* https://github.com/jakartaee/pages/issues/245[#245]
Utilise the new `ELResolver.StandaloneIdentifierMarker` class to optimise the
@@ -11437,10 +11433,10 @@ Jakarta Server Pages specification. This appendix is non-normative.
resolving of standalong identifiers e.g. `${my-identifier}`.
* https://github.com/jakartaee/pages/issues/363[#363]
- Align the JSP specification with the Platform specification regarding support
+ Align the Jakarta Pages (JSP) specification with the Platform specification regarding support
for older descriptors.
-=== Changes between JSP 4.0 and JSP 3.1
+=== Changes between Jakarta Pages (JSP) 4.0 and Jakarta Pages (JSP) 3.1
* Update the minimum Java version to Java 17.
@@ -11464,7 +11460,7 @@ Jakarta Server Pages specification. This appendix is non-normative.
* Update `ErrorData` to add support for the new attribute
`jakarta.servlet.error.method`.
-=== Changes between JSP 3.1 and JSP 3.0
+=== Changes between Jakarta Pages (JSP) 3.1 and Jakarta Pages (JSP) 3.0
* Deprecate methods that override `ELResolver.getFeatureDescriptors()` as that
method has been deprecated as of EL 5.0.
@@ -11475,7 +11471,7 @@ Jakarta Server Pages specification. This appendix is non-normative.
Clarify the meaning of 'scope' in the context of scripting variables
associated with custom actions.
* https://github.com/jakartaee/pages/issues/44[#44]
- Clarify that the EL environment within a JSP has a set of default imports
+ Clarify that the EL environment within a Jakarta Pages (JSP) page has a set of default imports
consistent with the default imports for the scripting environment. Refactor
the `ScopedAttributeELResolver` to remove the special handling for imports and
unresolved variables.
@@ -11486,7 +11482,7 @@ Jakarta Server Pages specification. This appendix is non-normative.
Deprecate the `jsp:plugin` action and related actions as the associated HTML
elements are no longer supported by any major browser.
-=== Changes between JSP 3.0 and JSR 245
+=== Changes between Jakarta Pages (JSP) 3.0 and JSR 245
* The API has moved from the `javax.servlet.jsp` package to the
`jakarta.servlet.jsp` package.
@@ -11503,24 +11499,24 @@ concepts mentioned in this specification. This appendix is
non-normative.
*action* +
-An element in a JSP page that can act on
+An element in a Jakarta Pages (JSP) page that can act on
implicit objects and other server-side objects or can define new
scripting variables. Actions follow the XML syntax for elements with a
start tag, a body and an end tag; if the body is empty it can also use
the empty tag syntax. The tag must use a prefix.
*action, standard* +
-An action that is defined in the JSP
-specification and is always available to a JSP file without being
+An action that is defined in the Jakarta Pages (JSP)
+specification and is always available to a Jakarta Pages (JSP) file without being
imported.
*action, custom* +
An action described in a portable manner by a
tag library descriptor and a collection of Java classes and imported
-into a JSP page by a taglib directive.
+into a Jakarta Pages (JSP) page by a taglib directive.
*Application Assembler* +
-A person that combines JSP pages, servlet
+A person that combines Jakarta Pages (JSP), servlet
classes, HTML content, tag libraries, and other Web content into a
deployable Web application.
@@ -11535,22 +11531,22 @@ and protocols that the container must support.
*Component Provider* +
A vendor that provides a component either as
-Java classes or as JSP page source.
+Java classes or as Jakarta Pages (JSP) page source.
*distributed container* +
-A JSP container that can run a Web
+A Jakarta Pages (JSP) container that can run a Web
application that is tagged as distributable and is spread across
multiple Java virtual machines that might be running on different
hosts.
*declaration* +
A scripting element that declares methods,
-variables, or both in a JSP page. Syntactically it is delimited by the
+variables, or both in a Jakarta Pages (JSP) page. Syntactically it is delimited by the
`<%!` and `%>` characters.
*directive* +
-An element in a JSP page that gives an
-instruction to the JSP container and is interpreted at translation time.
+An element in a Jakarta Pages (JSP) page that gives an
+instruction to the Jakarta Pages (JSP) container and is interpreted at translation time.
Syntactically it is delimited by the `<%@` and `%>` characters.
*dynamic attribute* +
@@ -11558,27 +11554,27 @@ An attribute, passed to a custom action,
whose name is not explicitly declared in the tag library descriptor.
*element* +
-A portion of a JSP page that is recognized by
-the JSP translator. An element can be a directive, an action, or a
+A portion of a Jakarta Pages (JSP) page that is recognized by
+the Jakarta Pages (JSP) translator. An element can be a directive, an action, or a
scripting element.
*EL expression* +
-An element in a JSP page representing an
-expression to be parsed and evaluated via the JSP Expression Language.
+An element in a Jakarta Pages (JSP) page representing an
+expression to be parsed and evaluated via the Jakarta Pages (JSP) Expression Language.
Syntactically it is delimited by the `${` and `}` characters.
*expression* +
Either a scripting expression or an EL expression.
*fixed template data* +
-Any portions of a JSP file that are not
-described in the JSP specification, such as HTML tags, XML tags, and
+Any portions of a Jakarta Pages (JSP) file that are not
+described in the Jakarta Pages (JSP) specification, such as HTML tags, XML tags, and
text. The template data is returned to the client in the response or is
processed by a component.
*implicit object* +
A server-side object that is defined by the
-JSP container and is always available in a JSP file without being
+Jakarta Pages (JSP) container and is always available in a Jakarta Pages (JSP) file without being
declared. The implicit objects are `request`, `response`,
`pageContext`, `session`, `application`, `out`, `config`, `page`,
and `exception` for scriptlets and scripting expressions. The implicit
@@ -11586,63 +11582,63 @@ objects are `pageContext`, `pageScope`, `requestScope`,
`sessionScope`, `applicationScope`, `param`, `paramValues`, `header`,
`headerValues`, `cookie` and `initParam` for EL expressions.
-*Jakarta Server Pages technology* +
+*Jakarta Pages technology* +
An extensible Web technology that uses
template data, custom elements, scripting languages, and server-side
Java objects to return dynamic content to a client. Typically the
template data is HTML or XML elements, and in many cases the client is a
Web browser.
-*JSP container* +
+*Jakarta Pages (JSP) container* +
A system-level entity that provides life
-cycle management and runtime support for JSP and servlet components.
+cycle management and runtime support for Jakarta Pages (JSP) and servlet components.
-*JSP configuration* +
-The deployment-time process by which the JSP
+*Jakarta Pages (JSP) configuration* +
+The deployment-time process by which the Jakarta Pages (JSP)
container is declaratively configured using a deployment descriptor.
-*JSP file* +
-A text file that contains JSP elements,
-forming a complete JSP page or just a partial page that must be combined
-with other JSP files to form a complete page. Most top-level JSP files
+*Jakarta Pages (JSP) file* +
+A text file that contains Jakarta Pages (JSP) elements,
+forming a complete Jakarta Pages (JSP) page or just a partial page that must be combined
+with other Jakarta Pages (JSP) files to form a complete page. Most top-level Jakarta Pages (JSP) files
have a `.jsp` extension, but other extensions can be configured as
well.
-*JSP fragment* +
-A portion of JSP code, translated into an
+*Jakarta Pages (JSP) fragment* +
+A portion of Jakarta Pages (JSP) code, translated into an
implementation of the `jakarta.servlet.jsp.JspFragment` abstract class.
-*JSP page* +
-One or more JSP files that form a
+*Jakarta Pages (JSP) page* +
+One or more Jakarta Pages (JSP) files that form a
syntactically complete description for processing a request to create a
response.
-*JSP page, front* +
-A JSP page that receives
+*Jakarta Pages (JSP) page, front* +
+A Jakarta Pages (JSP) page that receives
an HTTP request directly from the client. It creates, updates, and/or
accesses some server-side data and then forwards the request to a
-presentation JSP page.
+presentation Jakarta Pages (JSP) page.
-*JSP page, presentation* +
- A JSP page that is intended for presentation
+*Jakarta Pages (JSP) page, presentation* +
+ A Jakarta Pages (JSP) page that is intended for presentation
purposes only. It accesses and/or updates some server-side data and
incorporates fixed template data to create content that is sent to the
client.
-*JSP page implementation class* +
+*Jakarta Pages (JSP) page implementation class* +
The Java programming language class, a
-servlet, that is the runtime representation of a JSP page and which
+servlet, that is the runtime representation of a Jakarta Pages (JSP) page and which
receives the request object and updates the response object. The page
-implementation class can use the services provided by the JSP container,
-including both the servlet and the JSP APIs.
+implementation class can use the services provided by the Jakarta Pages (JSP) container,
+including both the servlet and the Jakarta Pages (JSP) APIs.
-*JSP page implementation object* +
-The instance of the JSP page implementation
+*Jakarta Pages (JSP) page implementation object* +
+The instance of the Jakarta Pages (JSP) page implementation
class that receives the `request` object and updates the `response`
object.
-*JSP segment* +
-A portion of JSP code defined in a separate
+*Jakarta Pages (JSP) segment* +
+A portion of Jakarta Pages (JSP) code defined in a separate
file, and imported into a page using the include directive.
*named attribute* +
@@ -11651,9 +11647,9 @@ value is defined using the `` standard action.
*scripting element* +
A declaration, scriptlet, or expression,
-whose tag syntax is defined by the JSP specification, and whose content
-is written according to the scripting language used in the JSP page. The
-JSP specification describes the syntax and semantics for the case where
+whose tag syntax is defined by the Jakarta Pages (JSP) specification, and whose content
+is written according to the scripting language used in the Jakarta Pages (JSP) page. The
+Jakarta Pages (JSP) specification describes the syntax and semantics for the case where
the language page attribute is `java`.
*scripting expression* +
@@ -11664,8 +11660,8 @@ by the `<%=` and `%>` characters.
*scriptlet* +
An scripting element containing any code
-fragment that is valid in the scripting language used in the JSP page.
-The JSP specification describes what is a valid scriptlet for the case
+fragment that is valid in the scripting language used in the Jakarta Pages (JSP) page.
+The Jakarta Pages (JSP) specification describes what is a valid scriptlet for the case
where the language page attribute is `java`. Syntactically a
scriptlet is delimited by the `<%` and `%>` characters.
@@ -11676,13 +11672,13 @@ A tag handler that implements the
*tag* +
A piece of text between a left angle
bracket and a right angle bracket that has a name, can have attributes,
-and is part of an element in a JSP page. Tag names are known to the JSP
-translator, either because the name is part of the JSP specification (in
+and is part of an element in a Jakarta Pages (JSP) page. Tag names are known to the Jakarta Pages (JSP)
+translator, either because the name is part of the Jakarta Pages (JSP) specification (in
the case of a standard action), or because it has been introduced using
a Tag Library (in the case of custom action).
*tag file* +
-A text-based document that uses fixed template data and JSP elements to
+A text-based document that uses fixed template data and Jakarta Pages (JSP) elements to
define a custom action. The semantics of a tag file are realized at
runtime by a tag handler.
@@ -11695,7 +11691,7 @@ An XML document describing a tag library.
*Tag Library Provider* +
A vendor that provides a tag library. Typical
-examples may be a JSP container vendor, a development group within a
+examples may be a Jakarta Pages (JSP) container vendor, a development group within a
corporation, a component vendor, or a service vendor that wants to
provide easier use of their services.
@@ -11717,9 +11713,9 @@ application, and in a Jakarta EE environment, the security and resource
mappings.
*web component* +
-A servlet class or JSP page that runs in a
-JSP container and provides services in response to requests.
+A servlet class or Jakarta Pages (JSP) page that runs in a
+Jakarta Pages (JSP) container and provides services in response to requests.
*Web Container Provider* +
-A vendor that provides a servlet and JSP
+A vendor that provides a servlet and Jakarta Pages (JSP)
container that support the corresponding component contracts.
diff --git a/spec/src/main/asciidoc/server-pages-spec.adoc b/spec/src/main/asciidoc/server-pages-spec.adoc
index 820ed7ac..c9dfe6e9 100644
--- a/spec/src/main/asciidoc/server-pages-spec.adoc
+++ b/spec/src/main/asciidoc/server-pages-spec.adoc
@@ -1,9 +1,9 @@
//
-// Copyright (c) 2017, 2023 Contributors to the Eclipse Foundation
+// Copyright (c) 2017, 2026 Contributors to the Eclipse Foundation
//
-= Jakarta Server Pages
-:authors: Jakarta Server Pages Team, https://projects.eclipse.org/projects/ee4j.jsp
+= Jakarta Pages
+:authors: Jakarta Pages Team, https://projects.eclipse.org/projects/ee4j.jsp
:email: https://dev.eclipse.org/mailman/listinfo/jsp-dev
:version-label!:
:doctype: book
diff --git a/tck/docs/assertions/JakartaServerPagesJavadocAssertions.html b/tck/docs/assertions/JakartaServerPagesJavadocAssertions.html
index 901b86a6..e77c4a34 100644
--- a/tck/docs/assertions/JakartaServerPagesJavadocAssertions.html
+++ b/tck/docs/assertions/JakartaServerPagesJavadocAssertions.html
@@ -51,7 +51,7 @@ Jakarta Server Pages - 3.1
| ID | Return | Method/Field | Description | Required | Deprecated | Testable |
-| JSP:JAVADOC:1 | ErrorData | jakarta.servlet.jsp.ErrorData.ErrorData
+ | PAGES:JAVADOC:1 | ErrorData | jakarta.servlet.jsp.ErrorData.ErrorData
(
Throwable
@@ -66,7 +66,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:2 | Throwable | jakarta.servlet.jsp.ErrorData.getThrowable
+ | PAGES:JAVADOC:2 | Throwable | jakarta.servlet.jsp.ErrorData.getThrowable
| Returns the Throwable that caused the error
| true |
@@ -74,7 +74,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:3 | int | jakarta.servlet.jsp.ErrorData.getStatusCode
+ | PAGES:JAVADOC:3 | int | jakarta.servlet.jsp.ErrorData.getStatusCode
| Returns the status code of the error
| true |
@@ -82,7 +82,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:4 | String | jakarta.servlet.jsp.ErrorData.getRequestURI
+ | PAGES:JAVADOC:4 | String | jakarta.servlet.jsp.ErrorData.getRequestURI
| Returns the request URI
| true |
@@ -90,7 +90,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:5 | String | jakarta.servlet.jsp.ErrorData.getServletName
+ | PAGES:JAVADOC:5 | String | jakarta.servlet.jsp.ErrorData.getServletName
| Returns the name of the servlet invoked
| true |
@@ -98,7 +98,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:6 | SkipPageException | jakarta.servlet.jsp.SkipPageException.SkipPageException
+ | PAGES:JAVADOC:6 | SkipPageException | jakarta.servlet.jsp.SkipPageException.SkipPageException
| Creates a SkipPageException with no message.
| true |
@@ -106,7 +106,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:7 | SkipPageException | jakarta.servlet.jsp.SkipPageException.SkipPageException
+ | PAGES:JAVADOC:7 | SkipPageException | jakarta.servlet.jsp.SkipPageException.SkipPageException
(
String
@@ -118,7 +118,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:8 | SkipPageException | jakarta.servlet.jsp.SkipPageException.SkipPageException
+ | PAGES:JAVADOC:8 | SkipPageException | jakarta.servlet.jsp.SkipPageException.SkipPageException
(
String
@@ -131,7 +131,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:9 | SkipPageException | jakarta.servlet.jsp.SkipPageException.SkipPageException
+ | PAGES:JAVADOC:9 | SkipPageException | jakarta.servlet.jsp.SkipPageException.SkipPageException
(
Throwable
@@ -143,7 +143,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:10 | PageContext | jakarta.servlet.jsp.PageContext.PageContext
+ | PAGES:JAVADOC:10 | PageContext | jakarta.servlet.jsp.PageContext.PageContext
|
| true |
@@ -151,7 +151,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:11 | void | jakarta.servlet.jsp.PageContext.initialize
+ | PAGES:JAVADOC:11 | void | jakarta.servlet.jsp.PageContext.initialize
(
Servlet
@@ -162,7 +162,7 @@ Jakarta Server Pages - 3.1
, 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.
+ | The initialize method is called to initialize an uninitialized PageContext so that it may be used by a Jakarta Pages (JSP) page 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 |
@@ -170,7 +170,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:12 | void | jakarta.servlet.jsp.PageContext.initialize
+ | PAGES:JAVADOC:12 | void | jakarta.servlet.jsp.PageContext.initialize
(
Servlet
@@ -188,7 +188,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:13 | void | jakarta.servlet.jsp.PageContext.initialize
+ | PAGES:JAVADOC:13 | void | jakarta.servlet.jsp.PageContext.initialize
(
Servlet
@@ -206,7 +206,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:14 | void | jakarta.servlet.jsp.PageContext.initialize
+ | PAGES:JAVADOC:14 | void | jakarta.servlet.jsp.PageContext.initialize
(
Servlet
@@ -224,7 +224,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:15 | void | jakarta.servlet.jsp.PageContext.release
+ | PAGES: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.
@@ -233,7 +233,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:16 | HttpSession | jakarta.servlet.jsp.PageContext.getSession
+ | PAGES:JAVADOC:16 | HttpSession | jakarta.servlet.jsp.PageContext.getSession
| The current value of the session object (an HttpSession).
| true |
@@ -241,7 +241,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:17 | Object | jakarta.servlet.jsp.PageContext.getPage
+ | PAGES: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 |
@@ -249,7 +249,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:18 | ServletRequest | jakarta.servlet.jsp.PageContext.getRequest
+ | PAGES:JAVADOC:18 | ServletRequest | jakarta.servlet.jsp.PageContext.getRequest
| The current value of the request object (a ServletRequest).
| true |
@@ -257,7 +257,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:19 | ServletResponse | jakarta.servlet.jsp.PageContext.getResponse
+ | PAGES:JAVADOC:19 | ServletResponse | jakarta.servlet.jsp.PageContext.getResponse
| The current value of the response object (a ServletResponse).
| true |
@@ -265,7 +265,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:20 | Exception | jakarta.servlet.jsp.PageContext.getException
+ | PAGES:JAVADOC:20 | Exception | jakarta.servlet.jsp.PageContext.getException
| The current value of the exception object (an Exception).
| true |
@@ -273,7 +273,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:21 | ServletConfig | jakarta.servlet.jsp.PageContext.getServletConfig
+ | PAGES:JAVADOC:21 | ServletConfig | jakarta.servlet.jsp.PageContext.getServletConfig
| The ServletConfig instance.
| true |
@@ -281,7 +281,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:22 | ServletContext | jakarta.servlet.jsp.PageContext.getServletContext
+ | PAGES:JAVADOC:22 | ServletContext | jakarta.servlet.jsp.PageContext.getServletContext
| The ServletContext instance.
| true |
@@ -289,37 +289,37 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:23 | void | jakarta.servlet.jsp.PageContext.forward
+ | PAGES: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 |
+ | 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 Jakarta Pages (JSP) page. | true |
| true |
-| JSP:JAVADOC:24 | void | jakarta.servlet.jsp.PageContext.forward
+ | PAGES: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 |
+ | 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 Jakarta Pages (JSP) page. | true |
| true |
-| JSP:JAVADOC:25 | void | jakarta.servlet.jsp.PageContext.forward
+ | PAGES: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 |
+ | It is only valid to call this method from a Thread executing within a _jspService(...) method of a Jakarta Pages (JSP) page. 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
+ | PAGES:JAVADOC:26 | void | jakarta.servlet.jsp.PageContext.forward
(
String
@@ -331,7 +331,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:27 | void | jakarta.servlet.jsp.PageContext.forward
+ | PAGES:JAVADOC:27 | void | jakarta.servlet.jsp.PageContext.forward
(
String
@@ -343,7 +343,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:29 | void | jakarta.servlet.jsp.PageContext.forward
+ | PAGES:JAVADOC:29 | void | jakarta.servlet.jsp.PageContext.forward
(
String
@@ -355,37 +355,37 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:31 | void | jakarta.servlet.jsp.PageContext.include
+ | PAGES: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 |
+ | 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 Jakarta Pages (JSP) page 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 Jakarta Pages (JSP) page. | true |
| true |
-| JSP:JAVADOC:32 | void | jakarta.servlet.jsp.PageContext.include
+ | PAGES: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 |
+ | 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 Jakarta Pages (JSP) page 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 Jakarta Pages (JSP) page. | true |
| true |
-| JSP:JAVADOC:33 | void | jakarta.servlet.jsp.PageContext.include
+ | PAGES: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 |
+ | It is only valid to call this method from a Thread executing within a _jspService(...) method of a Jakarta Pages (JSP) page. | true |
| false |
-| JSP:JAVADOC:34 | void | jakarta.servlet.jsp.PageContext.include
+ | PAGES:JAVADOC:34 | void | jakarta.servlet.jsp.PageContext.include
(
String
@@ -397,7 +397,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:35 | void | jakarta.servlet.jsp.PageContext.include
+ | PAGES:JAVADOC:35 | void | jakarta.servlet.jsp.PageContext.include
(
String
@@ -409,42 +409,42 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:38 | void | jakarta.servlet.jsp.PageContext.include
+ | PAGES: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 |
+ | 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 Jakarta Pages (JSP) page. | true |
| true |
-| JSP:JAVADOC:39 | void | jakarta.servlet.jsp.PageContext.include
+ | PAGES: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 |
+ | 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 Jakarta Pages (JSP) page. | true |
| true |
-| JSP:JAVADOC:40 | void | jakarta.servlet.jsp.PageContext.include
+ | PAGES: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.
+ 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 Jakarta Pages (JSP) page 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
+ | PAGES:JAVADOC:385 | void | jakarta.servlet.jsp.PageContext.include
(
String
@@ -457,18 +457,18 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:41 | void | jakarta.servlet.jsp.PageContext.include
+ | PAGES: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 |
+ | It is only valid to call this method from a Thread executing within a _jspService(...) method of a Jakarta Pages (JSP) page. | true |
| false |
-| JSP:JAVADOC:42 | void | jakarta.servlet.jsp.PageContext.include
+ | PAGES:JAVADOC:42 | void | jakarta.servlet.jsp.PageContext.include
(
String
@@ -481,7 +481,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:43 | void | jakarta.servlet.jsp.PageContext.include
+ | PAGES:JAVADOC:43 | void | jakarta.servlet.jsp.PageContext.include
(
String
@@ -494,17 +494,17 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:46 | void | jakarta.servlet.jsp.PageContext.handlePageException
+ | PAGES: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 |
+ | This method is intended to process an unhandled "page" level exception by forwarding the exception to the specified error page for this Jakarta Pages (JSP) page. | true |
| true |
-| JSP:JAVADOC:47 | void | jakarta.servlet.jsp.PageContext.handlePageException
+ | PAGES:JAVADOC:47 | void | jakarta.servlet.jsp.PageContext.handlePageException
(
Exception
@@ -514,17 +514,17 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:48 | void | jakarta.servlet.jsp.PageContext.handlePageException
+ | PAGES: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 |
+ | A Jakarta Pages (JSP) page 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
+ | PAGES:JAVADOC:49 | void | jakarta.servlet.jsp.PageContext.handlePageException
(
Exception
@@ -536,7 +536,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:50 | void | jakarta.servlet.jsp.PageContext.handlePageException
+ | PAGES:JAVADOC:50 | void | jakarta.servlet.jsp.PageContext.handlePageException
(
Exception
@@ -548,7 +548,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:51 | void | jakarta.servlet.jsp.PageContext.handlePageException
+ | PAGES:JAVADOC:51 | void | jakarta.servlet.jsp.PageContext.handlePageException
(
Exception
@@ -560,19 +560,19 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:53 | void | jakarta.servlet.jsp.PageContext.handlePageException
+ | PAGES: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.
+ 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 Jakarta Pages (JSP) page.
| true |
| true |
-| JSP:JAVADOC:54 | void | jakarta.servlet.jsp.PageContext.handlePageException
+ | PAGES:JAVADOC:54 | void | jakarta.servlet.jsp.PageContext.handlePageException
(
Throwable
@@ -584,17 +584,17 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:55 | void | jakarta.servlet.jsp.PageContext.handlePageException
+ | PAGES: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 |
+ | A Jakarta Pages (JSP) page 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
+ | PAGES:JAVADOC:56 | void | jakarta.servlet.jsp.PageContext.handlePageException
(
Throwable
@@ -606,7 +606,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:57 | void | jakarta.servlet.jsp.PageContext.handlePageException
+ | PAGES:JAVADOC:57 | void | jakarta.servlet.jsp.PageContext.handlePageException
(
Throwable
@@ -618,7 +618,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:58 | void | jakarta.servlet.jsp.PageContext.handlePageException
+ | PAGES:JAVADOC:58 | void | jakarta.servlet.jsp.PageContext.handlePageException
(
Throwable
@@ -630,7 +630,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:59 | void | jakarta.servlet.jsp.PageContext.handlePageException
+ | PAGES:JAVADOC:59 | void | jakarta.servlet.jsp.PageContext.handlePageException
(
Throwable
@@ -642,7 +642,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:60 | BodyContent | jakarta.servlet.jsp.PageContext.pushBody
+ | PAGES: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 |
@@ -650,7 +650,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:61 | JspWriter | jakarta.servlet.jsp.PageContext.popBody
+ | PAGES: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 |
@@ -658,7 +658,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:62 | ErrorData | jakarta.servlet.jsp.PageContext.getErrorData
+ | PAGES:JAVADOC:62 | ErrorData | jakarta.servlet.jsp.PageContext.getErrorData
| Provides convenient access to error information.
| true |
@@ -666,7 +666,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:63 | void | jakarta.servlet.jsp.JspWriter.newLine
+ | PAGES: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.
@@ -675,7 +675,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:64 | void | jakarta.servlet.jsp.JspWriter.newLine
+ | PAGES:JAVADOC:64 | void | jakarta.servlet.jsp.JspWriter.newLine
throws
IOException
| If an I/O error occurs | true |
@@ -683,7 +683,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:65 | void | jakarta.servlet.jsp.JspWriter.print
+ | PAGES:JAVADOC:65 | void | jakarta.servlet.jsp.JspWriter.print
(
boolean
@@ -698,7 +698,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:66 | void | jakarta.servlet.jsp.JspWriter.print
+ | PAGES:JAVADOC:66 | void | jakarta.servlet.jsp.JspWriter.print
(
boolean
@@ -710,7 +710,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:67 | void | jakarta.servlet.jsp.JspWriter.print
+ | PAGES:JAVADOC:67 | void | jakarta.servlet.jsp.JspWriter.print
(
char
@@ -724,7 +724,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:68 | void | jakarta.servlet.jsp.JspWriter.print
+ | PAGES:JAVADOC:68 | void | jakarta.servlet.jsp.JspWriter.print
(
char
@@ -736,7 +736,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:69 | void | jakarta.servlet.jsp.JspWriter.print
+ | PAGES:JAVADOC:69 | void | jakarta.servlet.jsp.JspWriter.print
(
int
@@ -752,7 +752,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:70 | void | jakarta.servlet.jsp.JspWriter.print
+ | PAGES:JAVADOC:70 | void | jakarta.servlet.jsp.JspWriter.print
(
int
@@ -764,7 +764,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:71 | void | jakarta.servlet.jsp.JspWriter.print
+ | PAGES:JAVADOC:71 | void | jakarta.servlet.jsp.JspWriter.print
(
long
@@ -780,7 +780,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:72 | void | jakarta.servlet.jsp.JspWriter.print
+ | PAGES:JAVADOC:72 | void | jakarta.servlet.jsp.JspWriter.print
(
long
@@ -792,7 +792,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:73 | void | jakarta.servlet.jsp.JspWriter.print
+ | PAGES:JAVADOC:73 | void | jakarta.servlet.jsp.JspWriter.print
(
float
@@ -808,7 +808,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:74 | void | jakarta.servlet.jsp.JspWriter.print
+ | PAGES:JAVADOC:74 | void | jakarta.servlet.jsp.JspWriter.print
(
float
@@ -820,7 +820,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:75 | void | jakarta.servlet.jsp.JspWriter.print
+ | PAGES:JAVADOC:75 | void | jakarta.servlet.jsp.JspWriter.print
(
double
@@ -836,7 +836,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:76 | void | jakarta.servlet.jsp.JspWriter.print
+ | PAGES:JAVADOC:76 | void | jakarta.servlet.jsp.JspWriter.print
(
double
@@ -848,7 +848,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:77 | void | jakarta.servlet.jsp.JspWriter.print
+ | PAGES:JAVADOC:77 | void | jakarta.servlet.jsp.JspWriter.print
(
char[]
@@ -862,7 +862,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:78 | void | jakarta.servlet.jsp.JspWriter.print
+ | PAGES:JAVADOC:78 | void | jakarta.servlet.jsp.JspWriter.print
(
char[]
@@ -874,7 +874,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:79 | void | jakarta.servlet.jsp.JspWriter.print
+ | PAGES:JAVADOC:79 | void | jakarta.servlet.jsp.JspWriter.print
(
char[]
@@ -886,7 +886,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:80 | void | jakarta.servlet.jsp.JspWriter.print
+ | PAGES:JAVADOC:80 | void | jakarta.servlet.jsp.JspWriter.print
(
String
@@ -900,7 +900,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:81 | void | jakarta.servlet.jsp.JspWriter.print
+ | PAGES:JAVADOC:81 | void | jakarta.servlet.jsp.JspWriter.print
(
String
@@ -912,7 +912,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:82 | void | jakarta.servlet.jsp.JspWriter.print
+ | PAGES:JAVADOC:82 | void | jakarta.servlet.jsp.JspWriter.print
(
Object
@@ -928,7 +928,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:83 | void | jakarta.servlet.jsp.JspWriter.print
+ | PAGES:JAVADOC:83 | void | jakarta.servlet.jsp.JspWriter.print
(
Object
@@ -940,7 +940,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:84 | void | jakarta.servlet.jsp.JspWriter.println
+ | PAGES: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').
@@ -949,7 +949,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:85 | void | jakarta.servlet.jsp.JspWriter.println
+ | PAGES:JAVADOC:85 | void | jakarta.servlet.jsp.JspWriter.println
throws
IOException
| If an error occured while writing | true |
@@ -957,7 +957,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:86 | void | jakarta.servlet.jsp.JspWriter.println
+ | PAGES:JAVADOC:86 | void | jakarta.servlet.jsp.JspWriter.println
(
boolean
@@ -972,7 +972,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:87 | void | jakarta.servlet.jsp.JspWriter.println
+ | PAGES:JAVADOC:87 | void | jakarta.servlet.jsp.JspWriter.println
(
boolean
@@ -984,7 +984,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:88 | void | jakarta.servlet.jsp.JspWriter.println
+ | PAGES:JAVADOC:88 | void | jakarta.servlet.jsp.JspWriter.println
(
char
@@ -999,7 +999,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:89 | void | jakarta.servlet.jsp.JspWriter.println
+ | PAGES:JAVADOC:89 | void | jakarta.servlet.jsp.JspWriter.println
(
char
@@ -1011,7 +1011,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:90 | void | jakarta.servlet.jsp.JspWriter.println
+ | PAGES:JAVADOC:90 | void | jakarta.servlet.jsp.JspWriter.println
(
int
@@ -1026,7 +1026,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:91 | void | jakarta.servlet.jsp.JspWriter.println
+ | PAGES:JAVADOC:91 | void | jakarta.servlet.jsp.JspWriter.println
(
int
@@ -1038,7 +1038,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:92 | void | jakarta.servlet.jsp.JspWriter.println
+ | PAGES:JAVADOC:92 | void | jakarta.servlet.jsp.JspWriter.println
(
long
@@ -1053,7 +1053,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:93 | void | jakarta.servlet.jsp.JspWriter.println
+ | PAGES:JAVADOC:93 | void | jakarta.servlet.jsp.JspWriter.println
(
long
@@ -1065,7 +1065,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:94 | void | jakarta.servlet.jsp.JspWriter.println
+ | PAGES:JAVADOC:94 | void | jakarta.servlet.jsp.JspWriter.println
(
float
@@ -1080,7 +1080,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:95 | void | jakarta.servlet.jsp.JspWriter.println
+ | PAGES:JAVADOC:95 | void | jakarta.servlet.jsp.JspWriter.println
(
float
@@ -1092,7 +1092,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:96 | void | jakarta.servlet.jsp.JspWriter.println
+ | PAGES:JAVADOC:96 | void | jakarta.servlet.jsp.JspWriter.println
(
double
@@ -1107,7 +1107,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:97 | void | jakarta.servlet.jsp.JspWriter.println
+ | PAGES:JAVADOC:97 | void | jakarta.servlet.jsp.JspWriter.println
(
double
@@ -1119,7 +1119,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:98 | void | jakarta.servlet.jsp.JspWriter.println
+ | PAGES:JAVADOC:98 | void | jakarta.servlet.jsp.JspWriter.println
(
char[]
@@ -1132,7 +1132,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:99 | void | jakarta.servlet.jsp.JspWriter.println
+ | PAGES:JAVADOC:99 | void | jakarta.servlet.jsp.JspWriter.println
(
char[]
@@ -1144,7 +1144,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:100 | void | jakarta.servlet.jsp.JspWriter.println
+ | PAGES:JAVADOC:100 | void | jakarta.servlet.jsp.JspWriter.println
(
String
@@ -1159,7 +1159,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:101 | void | jakarta.servlet.jsp.JspWriter.println
+ | PAGES:JAVADOC:101 | void | jakarta.servlet.jsp.JspWriter.println
(
String
@@ -1171,7 +1171,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:102 | void | jakarta.servlet.jsp.JspWriter.println
+ | PAGES:JAVADOC:102 | void | jakarta.servlet.jsp.JspWriter.println
(
Object
@@ -1186,7 +1186,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:103 | void | jakarta.servlet.jsp.JspWriter.println
+ | PAGES:JAVADOC:103 | void | jakarta.servlet.jsp.JspWriter.println
(
Object
@@ -1198,7 +1198,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:104 | void | jakarta.servlet.jsp.JspWriter.clear
+ | PAGES: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.
@@ -1207,7 +1207,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:105 | void | jakarta.servlet.jsp.JspWriter.clear
+ | PAGES:JAVADOC:105 | void | jakarta.servlet.jsp.JspWriter.clear
throws
IOException
| If an I/O error occurs | true |
@@ -1215,7 +1215,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:106 | void | jakarta.servlet.jsp.JspWriter.clearBuffer
+ | PAGES: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.
@@ -1224,7 +1224,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:107 | void | jakarta.servlet.jsp.JspWriter.clearBuffer
+ | PAGES:JAVADOC:107 | void | jakarta.servlet.jsp.JspWriter.clearBuffer
throws
IOException
| If an I/O error occurs | true |
@@ -1232,7 +1232,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:108 | void | jakarta.servlet.jsp.JspWriter.flush
+ | PAGES: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.
@@ -1241,7 +1241,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:109 | void | jakarta.servlet.jsp.JspWriter.flush
+ | PAGES:JAVADOC:109 | void | jakarta.servlet.jsp.JspWriter.flush
throws
IOException
| If an I/O error occurs | true |
@@ -1249,16 +1249,16 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:110 | void | jakarta.servlet.jsp.JspWriter.close
+ | PAGES: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.
+ This method needs not be invoked explicitly for the initial JspWriter as the code generated by the Jakarta Pages (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
+ | PAGES:JAVADOC:111 | void | jakarta.servlet.jsp.JspWriter.close
throws
IOException
| If an I/O error occurs | true |
@@ -1266,7 +1266,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:112 | int | jakarta.servlet.jsp.JspWriter.getBufferSize
+ | PAGES:JAVADOC:112 | int | jakarta.servlet.jsp.JspWriter.getBufferSize
| This method returns the size of the buffer used by the JspWriter.
| true |
@@ -1274,7 +1274,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:113 | int | jakarta.servlet.jsp.JspWriter.getRemaining
+ | PAGES:JAVADOC:113 | int | jakarta.servlet.jsp.JspWriter.getRemaining
| This method returns the number of unused bytes in the buffer.
| true |
@@ -1282,7 +1282,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:114 | boolean | jakarta.servlet.jsp.JspWriter.isAutoFlush
+ | PAGES:JAVADOC:114 | boolean | jakarta.servlet.jsp.JspWriter.isAutoFlush
| This method indicates whether the JspWriter is autoFlushing.
| true |
@@ -1290,7 +1290,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:115 | JspTagException | jakarta.servlet.jsp.JspTagException.JspTagException
+ | PAGES:JAVADOC:115 | JspTagException | jakarta.servlet.jsp.JspTagException.JspTagException
(
String
@@ -1303,7 +1303,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:116 | JspTagException | jakarta.servlet.jsp.JspTagException.JspTagException
+ | PAGES:JAVADOC:116 | JspTagException | jakarta.servlet.jsp.JspTagException.JspTagException
| Constructs a new JspTagException with no message.
| true |
@@ -1311,25 +1311,25 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:117 | JspTagException | jakarta.servlet.jsp.JspTagException.JspTagException
+ | PAGES: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.
+ | Constructs a new JspTagException when the Jakarta Pages (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
+ | PAGES: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.
+ | Constructs a new Jakarta Pages (JSP) Tag exception when the Jakarta Pages (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 |
@@ -1337,7 +1337,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:119 | JspFactory | jakarta.servlet.jsp.JspFactory.JspFactory
+ | PAGES:JAVADOC:119 | JspFactory | jakarta.servlet.jsp.JspFactory.JspFactory
|
| true |
@@ -1345,20 +1345,20 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:120 | void | jakarta.servlet.jsp.JspFactory.setDefaultFactory
+ | PAGES: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.
+ It is illegal for any principal other than the Jakarta Pages (JSP) Engine runtime to call this method.
| true |
| false |
-| JSP:JAVADOC:121 | JspFactory | jakarta.servlet.jsp.JspFactory.getDefaultFactory
+ | PAGES:JAVADOC:121 | JspFactory | jakarta.servlet.jsp.JspFactory.getDefaultFactory
| Returns the default factory for this implementation.
| true |
@@ -1366,7 +1366,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:122 | PageContext | jakarta.servlet.jsp.JspFactory.getPageContext
+ | PAGES:JAVADOC:122 | PageContext | jakarta.servlet.jsp.JspFactory.getPageContext
(
Servlet
@@ -1378,7 +1378,7 @@ Jakarta Server Pages - 3.1
, 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().
+ This method is typically called early in the processing of the _jspService() method of a Jakarta Pages (JSP) page 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 |
@@ -1386,21 +1386,21 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:123 | void | jakarta.servlet.jsp.JspFactory.releasePageContext
+ | PAGES: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.
+ Results in PageContext.release() being invoked. This method should be invoked prior to returning from the _jspService() method of a Jakarta Pages (JSP) page implementation class.
| true |
| true |
-| JSP:JAVADOC:124 | JspEngineInfo | jakarta.servlet.jsp.JspFactory.getEngineInfo
- | called to get implementation-specific information on the current JSP engine.
+ | PAGES:JAVADOC:124 | JspEngineInfo | jakarta.servlet.jsp.JspFactory.getEngineInfo
+ | called to get implementation-specific information on the current Jakarta Pages (JSP) engine.
| true |
@@ -1408,7 +1408,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:125 | JspException | jakarta.servlet.jsp.JspException.JspException
+ | PAGES:JAVADOC:125 | JspException | jakarta.servlet.jsp.JspException.JspException
| Construct a JspException
| true |
@@ -1416,12 +1416,12 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:126 | JspException | jakarta.servlet.jsp.JspException.JspException
+ | PAGES:JAVADOC:126 | JspException | jakarta.servlet.jsp.JspException.JspException
(
String
)
- | Constructs a new JSP exception with the specified message.
+ | Constructs a new Jakarta Pages (JSP) exception with the specified message.
The message can be written to the server log and/or displayed for the user.
| true |
@@ -1429,25 +1429,25 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:127 | JspException | jakarta.servlet.jsp.JspException.JspException
+ | PAGES: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.
+ | Constructs a new Jakarta Pages (JSP) exception when the Jakarta Pages (JSP) page 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
+ | PAGES: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.
+ | Constructs a new Jakarta Pages (JSP) exception when the Jakarta Pages (JSP) page 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 |
@@ -1455,15 +1455,15 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:129 | Throwable | jakarta.servlet.jsp.JspException.getRootCause
- | Returns the exception that caused this JSP exception.
+ | PAGES:JAVADOC:129 | Throwable | jakarta.servlet.jsp.JspException.getRootCause
+ | Returns the exception that caused this Jakarta Pages (JSP) exception.
| true |
| true |
-| JSP:JAVADOC:130 | JspEngineInfo | jakarta.servlet.jsp.JspEngineInfo.JspEngineInfo
+ | PAGES:JAVADOC:130 | JspEngineInfo | jakarta.servlet.jsp.JspEngineInfo.JspEngineInfo
|
| true |
@@ -1471,8 +1471,8 @@ Jakarta Server Pages - 3.1
| 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.
+ | PAGES:JAVADOC:131 | String | jakarta.servlet.jsp.JspEngineInfo.getSpecificationVersion
+ | Return the version number of the Jakarta Pages (JSP) specification that is supported by this Jakarta Pages (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 |
@@ -1480,7 +1480,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:132 | JspContext | jakarta.servlet.jsp.JspContext.JspContext
+ | PAGES:JAVADOC:132 | JspContext | jakarta.servlet.jsp.JspContext.JspContext
|
| true |
@@ -1488,7 +1488,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:380 | JspWriter | jakarta.servlet.jsp.JspContext.popBody
+ | PAGES: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 |
@@ -1496,7 +1496,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:381 | JspWriter | jakarta.servlet.jsp.JspContext.pushBody
+ | PAGES:JAVADOC:381 | JspWriter | jakarta.servlet.jsp.JspContext.pushBody
(
Writer
@@ -1506,7 +1506,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:133 | void | jakarta.servlet.jsp.JspContext.setAttribute
+ | PAGES:JAVADOC:133 | void | jakarta.servlet.jsp.JspContext.setAttribute
(
String
@@ -1519,7 +1519,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:396 | void | jakarta.servlet.jsp.JspContext.setAttribute
+ | PAGES:JAVADOC:396 | void | jakarta.servlet.jsp.JspContext.setAttribute
(
String
@@ -1532,7 +1532,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:134 | void | jakarta.servlet.jsp.JspContext.setAttribute
+ | PAGES:JAVADOC:134 | void | jakarta.servlet.jsp.JspContext.setAttribute
(
String
@@ -1545,7 +1545,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:135 | void | jakarta.servlet.jsp.JspContext.setAttribute
+ | PAGES:JAVADOC:135 | void | jakarta.servlet.jsp.JspContext.setAttribute
(
String
@@ -1559,7 +1559,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:397 | void | jakarta.servlet.jsp.JspContext.setAttribute
+ | PAGES:JAVADOC:397 | void | jakarta.servlet.jsp.JspContext.setAttribute
(
String
@@ -1573,7 +1573,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:136 | void | jakarta.servlet.jsp.JspContext.setAttribute
+ | PAGES:JAVADOC:136 | void | jakarta.servlet.jsp.JspContext.setAttribute
(
String
@@ -1587,7 +1587,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:398 | void | jakarta.servlet.jsp.JspContext.setAttribute
+ | PAGES:JAVADOC:398 | void | jakarta.servlet.jsp.JspContext.setAttribute
(
String
@@ -1601,7 +1601,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:399 | void | jakarta.servlet.jsp.JspContext.setAttribute
+ | PAGES:JAVADOC:399 | void | jakarta.servlet.jsp.JspContext.setAttribute
(
String
@@ -1615,7 +1615,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:137 | void | jakarta.servlet.jsp.JspContext.setAttribute
+ | PAGES:JAVADOC:137 | void | jakarta.servlet.jsp.JspContext.setAttribute
(
String
@@ -1629,7 +1629,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:138 | Object | jakarta.servlet.jsp.JspContext.getAttribute
+ | PAGES:JAVADOC:138 | Object | jakarta.servlet.jsp.JspContext.getAttribute
(
String
@@ -1641,7 +1641,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:139 | Object | jakarta.servlet.jsp.JspContext.getAttribute
+ | PAGES:JAVADOC:139 | Object | jakarta.servlet.jsp.JspContext.getAttribute
(
String
@@ -1653,7 +1653,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:141 | Object | jakarta.servlet.jsp.JspContext.getAttribute
+ | PAGES:JAVADOC:141 | Object | jakarta.servlet.jsp.JspContext.getAttribute
(
String
@@ -1666,7 +1666,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:142 | Object | jakarta.servlet.jsp.JspContext.getAttribute
+ | PAGES:JAVADOC:142 | Object | jakarta.servlet.jsp.JspContext.getAttribute
(
String
@@ -1679,7 +1679,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:143 | Object | jakarta.servlet.jsp.JspContext.getAttribute
+ | PAGES:JAVADOC:143 | Object | jakarta.servlet.jsp.JspContext.getAttribute
(
String
@@ -1692,7 +1692,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:390 | Object | jakarta.servlet.jsp.JspContext.getAttribute
+ | PAGES:JAVADOC:390 | Object | jakarta.servlet.jsp.JspContext.getAttribute
(
String
@@ -1705,7 +1705,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:144 | Object | jakarta.servlet.jsp.JspContext.findAttribute
+ | PAGES:JAVADOC:144 | Object | jakarta.servlet.jsp.JspContext.findAttribute
(
String
@@ -1717,7 +1717,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:387 | Object | jakarta.servlet.jsp.JspContext.findAttribute
+ | PAGES:JAVADOC:387 | Object | jakarta.servlet.jsp.JspContext.findAttribute
(
String
@@ -1731,7 +1731,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:145 | void | jakarta.servlet.jsp.JspContext.removeAttribute
+ | PAGES:JAVADOC:145 | void | jakarta.servlet.jsp.JspContext.removeAttribute
(
String
@@ -1743,7 +1743,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:391 | void | jakarta.servlet.jsp.JspContext.removeAttribute
+ | PAGES:JAVADOC:391 | void | jakarta.servlet.jsp.JspContext.removeAttribute
(
String
@@ -1757,7 +1757,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:146 | void | jakarta.servlet.jsp.JspContext.removeAttribute
+ | PAGES:JAVADOC:146 | void | jakarta.servlet.jsp.JspContext.removeAttribute
(
String
@@ -1770,7 +1770,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:392 | void | jakarta.servlet.jsp.JspContext.removeAttribute
+ | PAGES:JAVADOC:392 | void | jakarta.servlet.jsp.JspContext.removeAttribute
(
String
@@ -1785,7 +1785,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:393 | void | jakarta.servlet.jsp.JspContext.removeAttribute
+ | PAGES:JAVADOC:393 | void | jakarta.servlet.jsp.JspContext.removeAttribute
(
String
@@ -1800,7 +1800,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:394 | void | jakarta.servlet.jsp.JspContext.removeAttribute
+ | PAGES:JAVADOC:394 | void | jakarta.servlet.jsp.JspContext.removeAttribute
(
String
@@ -1815,7 +1815,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:147 | int | jakarta.servlet.jsp.JspContext.getAttributesScope
+ | PAGES:JAVADOC:147 | int | jakarta.servlet.jsp.JspContext.getAttributesScope
(
String
@@ -1827,7 +1827,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:389 | int | jakarta.servlet.jsp.JspContext.getAttributesScope
+ | PAGES:JAVADOC:389 | int | jakarta.servlet.jsp.JspContext.getAttributesScope
(
String
@@ -1841,7 +1841,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:148 | Enumeration | jakarta.servlet.jsp.JspContext.getAttributeNamesInScope
+ | PAGES:JAVADOC:148 | Enumeration | jakarta.servlet.jsp.JspContext.getAttributeNamesInScope
(
int
@@ -1853,7 +1853,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:387 | Enumeration | jakarta.servlet.jsp.JspContext.getAttributeNamesInScope
+ | PAGES:JAVADOC:387 | Enumeration | jakarta.servlet.jsp.JspContext.getAttributeNamesInScope
(
int
@@ -1867,7 +1867,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:388 | Enumeration | jakarta.servlet.jsp.JspContext.getAttributeNamesInScope
+ | PAGES:JAVADOC:388 | Enumeration | jakarta.servlet.jsp.JspContext.getAttributeNamesInScope
(
int
@@ -1881,7 +1881,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:149 | JspWriter | jakarta.servlet.jsp.JspContext.getOut
+ | PAGES:JAVADOC:149 | JspWriter | jakarta.servlet.jsp.JspContext.getOut
| The current value of the out object (a JspWriter).
| true |
@@ -1889,56 +1889,56 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:150 | ExpressionEvaluator | jakarta.servlet.jsp.JspContext.getExpressionEvaluator
+ | PAGES: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.
+ The Jakarta Pages (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
+ | PAGES:JAVADOC:151 | VariableResolver | jakarta.servlet.jsp.JspContext.getVariableResolver
+ | Returns an instance of a VariableResolver that provides access to the implicit objects specified in the Jakarta Pages (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.
+ | PAGES:JAVADOC:152 | void | jakarta.servlet.jsp.JspPage.jspInit
+ | The jspInit() method is invoked when the Jakarta Pages (JSP) page is initialized.
+ It is the responsibility of the Jakarta Pages (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 Jakarta Pages (JSP) page can override this method by including a definition for it in a declaration element. A Jakarta Pages (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.
+ | PAGES:JAVADOC:153 | void | jakarta.servlet.jsp.JspPage.jspDestroy
+ | The jspDestroy() method is invoked when the Jakarta Pages (JSP) page is about to be destroyed.
+ A Jakarta Pages (JSP) page can override this method by including a definition for it in a declaration element. A Jakarta Pages (JSP) page should redefine the destroy() method from Servlet.
| true |
| false |
-| JSP:JAVADOC:154 | void | jakarta.servlet.jsp.HttpJspPage._jspService
+ | PAGES: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.
+ | The _jspService() method corresponds to the body of the Jakarta Pages (JSP) page.
+ This method is defined automatically by the Jakarta Pages (JSP) container and should never be defined by the Jakarta Pages (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 Jakarta Pages (JSP) specification.
| true |
| false |
-| JSP:JAVADOC:155 | void | jakarta.servlet.jsp.HttpJspPage._jspService
+ | PAGES:JAVADOC:155 | void | jakarta.servlet.jsp.HttpJspPage._jspService
(
HttpServletRequest
@@ -1946,12 +1946,12 @@ Jakarta Server Pages - 3.1
)
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 |
+ | Thrown if an error occurred during the processing of the Jakarta Pages (JSP) page and that the container should take appropriate action to clean up the request. | true |
| false |
-| JSP:JAVADOC:156 | void | jakarta.servlet.jsp.HttpJspPage._jspService
+ | PAGES:JAVADOC:156 | void | jakarta.servlet.jsp.HttpJspPage._jspService
(
HttpServletRequest
@@ -1964,7 +1964,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:157 | ELParseException | jakarta.servlet.jsp.el.ELParseException.ELParseException
+ | PAGES:JAVADOC:157 | ELParseException | jakarta.servlet.jsp.el.ELParseException.ELParseException
| Creates an ELParseException with no detail message.
| true |
@@ -1972,7 +1972,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:158 | ELParseException | jakarta.servlet.jsp.el.ELParseException.ELParseException
+ | PAGES:JAVADOC:158 | ELParseException | jakarta.servlet.jsp.el.ELParseException.ELParseException
(
String
@@ -1984,7 +1984,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:159 | ELException | jakarta.servlet.jsp.el.ELException.ELException
+ | PAGES:JAVADOC:159 | ELException | jakarta.servlet.jsp.el.ELException.ELException
| Creates an ELException with no detail message.
| true |
@@ -1992,7 +1992,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:160 | ELException | jakarta.servlet.jsp.el.ELException.ELException
+ | PAGES:JAVADOC:160 | ELException | jakarta.servlet.jsp.el.ELException.ELException
(
String
@@ -2004,7 +2004,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:161 | ELException | jakarta.servlet.jsp.el.ELException.ELException
+ | PAGES:JAVADOC:161 | ELException | jakarta.servlet.jsp.el.ELException.ELException
(
Throwable
@@ -2016,7 +2016,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:162 | ELException | jakarta.servlet.jsp.el.ELException.ELException
+ | PAGES:JAVADOC:162 | ELException | jakarta.servlet.jsp.el.ELException.ELException
(
String
@@ -2029,7 +2029,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:163 | Throwable | jakarta.servlet.jsp.el.ELException.getRootCause
+ | PAGES:JAVADOC:163 | Throwable | jakarta.servlet.jsp.el.ELException.getRootCause
| Returns the root cause
| true |
@@ -2037,7 +2037,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:165 | Method | jakarta.servlet.jsp.el.FunctionMapper.resolveFunction
+ | PAGES:JAVADOC:165 | Method | jakarta.servlet.jsp.el.FunctionMapper.resolveFunction
(
String
@@ -2051,7 +2051,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:384 | Object | jakarta.servlet.jsp.el.VariableResolver.resolveVariable
+ | PAGES:JAVADOC:384 | Object | jakarta.servlet.jsp.el.VariableResolver.resolveVariable
(
String
@@ -2064,7 +2064,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:167 | Object | jakarta.servlet.jsp.el.VariableResolver.resolveVariable
+ | PAGES:JAVADOC:167 | Object | jakarta.servlet.jsp.el.VariableResolver.resolveVariable
(
String
@@ -2077,13 +2077,13 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:379 | ExpressionEvaluator | jakarta.servlet.jsp.el.ExpressionEvaluator.ExpressionEvaluator
+ | PAGES:JAVADOC:379 | ExpressionEvaluator | jakarta.servlet.jsp.el.ExpressionEvaluator.ExpressionEvaluator
| Default constructor. | true |
| false |
-| JSP:JAVADOC:168 | Expression | jakarta.servlet.jsp.el.ExpressionEvaluator.parseExpression
+ | PAGES:JAVADOC:168 | Expression | jakarta.servlet.jsp.el.ExpressionEvaluator.parseExpression
(
String
@@ -2096,7 +2096,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:169 | Expression | jakarta.servlet.jsp.el.ExpressionEvaluator.parseExpression
+ | PAGES:JAVADOC:169 | Expression | jakarta.servlet.jsp.el.ExpressionEvaluator.parseExpression
(
String
@@ -2111,7 +2111,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:170 | Expression | jakarta.servlet.jsp.el.ExpressionEvaluator.parseExpression
+ | PAGES:JAVADOC:170 | Expression | jakarta.servlet.jsp.el.ExpressionEvaluator.parseExpression
(
String
@@ -2126,7 +2126,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:171 | Object | jakarta.servlet.jsp.el.ExpressionEvaluator.evaluate
+ | PAGES:JAVADOC:171 | Object | jakarta.servlet.jsp.el.ExpressionEvaluator.evaluate
(
String
@@ -2140,7 +2140,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:172 | Object | jakarta.servlet.jsp.el.ExpressionEvaluator.evaluate
+ | PAGES:JAVADOC:172 | Object | jakarta.servlet.jsp.el.ExpressionEvaluator.evaluate
(
String
@@ -2154,7 +2154,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:173 | Object | jakarta.servlet.jsp.el.ExpressionEvaluator.evaluate
+ | PAGES:JAVADOC:173 | Object | jakarta.servlet.jsp.el.ExpressionEvaluator.evaluate
(
String
@@ -2170,13 +2170,13 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:378 | Expression | jakarta.servlet.jsp.el.Expression.Expression
+ | PAGES:JAVADOC:378 | Expression | jakarta.servlet.jsp.el.Expression.Expression
| Default constructor | true |
| false |
-| JSP:JAVADOC:174 | Object | jakarta.servlet.jsp.el.Expression.evaluate
+ | PAGES:JAVADOC:174 | Object | jakarta.servlet.jsp.el.Expression.evaluate
(
VariableResolver
@@ -2186,7 +2186,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:175 | Object | jakarta.servlet.jsp.el.Expression.evaluate
+ | PAGES:JAVADOC:175 | Object | jakarta.servlet.jsp.el.Expression.evaluate
(
VariableResolver
@@ -2198,7 +2198,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:176 | Object | jakarta.servlet.jsp.el.Expression.evaluate
+ | PAGES:JAVADOC:176 | Object | jakarta.servlet.jsp.el.Expression.evaluate
(
VariableResolver
@@ -2210,7 +2210,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:177 | VariableInfo | jakarta.servlet.jsp.tagext.VariableInfo.VariableInfo
+ | PAGES:JAVADOC:177 | VariableInfo | jakarta.servlet.jsp.tagext.VariableInfo.VariableInfo
(
String
@@ -2225,7 +2225,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:178 | String | jakarta.servlet.jsp.tagext.VariableInfo.getVarName
+ | PAGES:JAVADOC:178 | String | jakarta.servlet.jsp.tagext.VariableInfo.getVarName
| Returns the name of the scripting variable
| true |
@@ -2233,7 +2233,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:179 | String | jakarta.servlet.jsp.tagext.VariableInfo.getClassName
+ | PAGES:JAVADOC:179 | String | jakarta.servlet.jsp.tagext.VariableInfo.getClassName
| Returns the type of this variable
| true |
@@ -2241,7 +2241,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:180 | boolean | jakarta.servlet.jsp.tagext.VariableInfo.getDeclare
+ | PAGES: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.
@@ -2250,7 +2250,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:181 | int | jakarta.servlet.jsp.tagext.VariableInfo.getScope
+ | PAGES:JAVADOC:181 | int | jakarta.servlet.jsp.tagext.VariableInfo.getScope
| Returns the lexical scope of the variable.
@@ -2261,7 +2261,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:182 | ValidationMessage | jakarta.servlet.jsp.tagext.ValidationMessage.ValidationMessage
+ | PAGES:JAVADOC:182 | ValidationMessage | jakarta.servlet.jsp.tagext.ValidationMessage.ValidationMessage
(
String
@@ -2275,7 +2275,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:183 | String | jakarta.servlet.jsp.tagext.ValidationMessage.getId
+ | PAGES:JAVADOC:183 | String | jakarta.servlet.jsp.tagext.ValidationMessage.getId
| Get the jsp:id.
Null means that there is no information available.
@@ -2284,7 +2284,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:184 | String | jakarta.servlet.jsp.tagext.ValidationMessage.getMessage
+ | PAGES:JAVADOC:184 | String | jakarta.servlet.jsp.tagext.ValidationMessage.getMessage
| Get the localized validation message.
| true |
@@ -2292,7 +2292,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:185 | TagVariableInfo | jakarta.servlet.jsp.tagext.TagVariableInfo.TagVariableInfo
+ | PAGES:JAVADOC:185 | TagVariableInfo | jakarta.servlet.jsp.tagext.TagVariableInfo.TagVariableInfo
(
String
@@ -2308,7 +2308,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:187 | String | jakarta.servlet.jsp.tagext.TagVariableInfo.getNameGiven
+ | PAGES:JAVADOC:187 | String | jakarta.servlet.jsp.tagext.TagVariableInfo.getNameGiven
| The body of the <name-given> element
| true |
@@ -2316,7 +2316,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:188 | String | jakarta.servlet.jsp.tagext.TagVariableInfo.getNameFromAttribute
+ | PAGES: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.
@@ -2325,7 +2325,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:189 | String | jakarta.servlet.jsp.tagext.TagVariableInfo.getClassName
+ | PAGES:JAVADOC:189 | String | jakarta.servlet.jsp.tagext.TagVariableInfo.getClassName
| The body of the <class-name> element.
| true |
@@ -2333,7 +2333,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:190 | boolean | jakarta.servlet.jsp.tagext.TagVariableInfo.getDeclare
+ | PAGES:JAVADOC:190 | boolean | jakarta.servlet.jsp.tagext.TagVariableInfo.getDeclare
| The body of the <declare> element
| true |
@@ -2341,7 +2341,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:191 | int | jakarta.servlet.jsp.tagext.TagVariableInfo.getScope
+ | PAGES:JAVADOC:191 | int | jakarta.servlet.jsp.tagext.TagVariableInfo.getScope
| The body of the <scope> element
| true |
@@ -2349,30 +2349,30 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:193 | TagSupport | jakarta.servlet.jsp.tagext.TagSupport.TagSupport
+ | PAGES: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.
+ This constructor is called by the code generated by the Jakarta Pages (JSP) translator.
| true |
| true |
-| JSP:JAVADOC:194 | Tag | jakarta.servlet.jsp.tagext.TagSupport.findAncestorWithClass
+ | PAGES: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.
+ 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 Jakarta 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
+ | PAGES:JAVADOC:195 | int | jakarta.servlet.jsp.tagext.TagSupport.doStartTag
| Default processing of the start tag, returning SKIP_BODY.
@@ -2381,7 +2381,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:196 | int | jakarta.servlet.jsp.tagext.TagSupport.doStartTag
+ | PAGES:JAVADOC:196 | int | jakarta.servlet.jsp.tagext.TagSupport.doStartTag
throws
JspException
| if an error occurs while processing this tag | true |
@@ -2389,7 +2389,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:197 | int | jakarta.servlet.jsp.tagext.TagSupport.doEndTag
+ | PAGES:JAVADOC:197 | int | jakarta.servlet.jsp.tagext.TagSupport.doEndTag
| Default processing of the end tag returning EVAL_PAGE.
@@ -2398,7 +2398,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:198 | int | jakarta.servlet.jsp.tagext.TagSupport.doEndTag
+ | PAGES:JAVADOC:198 | int | jakarta.servlet.jsp.tagext.TagSupport.doEndTag
throws
JspException
| if an error occurs while processing this tag | true |
@@ -2406,7 +2406,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:199 | int | jakarta.servlet.jsp.tagext.TagSupport.doAfterBody
+ | PAGES:JAVADOC:199 | int | jakarta.servlet.jsp.tagext.TagSupport.doAfterBody
| Default processing for a body
@@ -2415,7 +2415,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:200 | int | jakarta.servlet.jsp.tagext.TagSupport.doAfterBody
+ | PAGES:JAVADOC:200 | int | jakarta.servlet.jsp.tagext.TagSupport.doAfterBody
throws
JspException
| if an error occurs while processing this tag | true |
@@ -2423,7 +2423,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:201 | void | jakarta.servlet.jsp.tagext.TagSupport.release
+ | PAGES:JAVADOC:201 | void | jakarta.servlet.jsp.tagext.TagSupport.release
| Release state.
@@ -2432,7 +2432,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:202 | void | jakarta.servlet.jsp.tagext.TagSupport.setParent
+ | PAGES:JAVADOC:202 | void | jakarta.servlet.jsp.tagext.TagSupport.setParent
(
Tag
@@ -2445,7 +2445,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:203 | Tag | jakarta.servlet.jsp.tagext.TagSupport.getParent
+ | PAGES:JAVADOC:203 | Tag | jakarta.servlet.jsp.tagext.TagSupport.getParent
| The Tag instance most closely enclosing this tag instance.
@@ -2454,7 +2454,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:204 | void | jakarta.servlet.jsp.tagext.TagSupport.setId
+ | PAGES:JAVADOC:204 | void | jakarta.servlet.jsp.tagext.TagSupport.setId
(
String
@@ -2466,7 +2466,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:205 | String | jakarta.servlet.jsp.tagext.TagSupport.getId
+ | PAGES:JAVADOC:205 | String | jakarta.servlet.jsp.tagext.TagSupport.getId
| The value of the id attribute of this tag; or null.
| true |
@@ -2474,7 +2474,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:206 | void | jakarta.servlet.jsp.tagext.TagSupport.setPageContext
+ | PAGES:JAVADOC:206 | void | jakarta.servlet.jsp.tagext.TagSupport.setPageContext
(
PageContext
@@ -2487,7 +2487,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:207 | void | jakarta.servlet.jsp.tagext.TagSupport.setValue
+ | PAGES:JAVADOC:207 | void | jakarta.servlet.jsp.tagext.TagSupport.setValue
(
String
@@ -2500,7 +2500,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:208 | Object | jakarta.servlet.jsp.tagext.TagSupport.getValue
+ | PAGES:JAVADOC:208 | Object | jakarta.servlet.jsp.tagext.TagSupport.getValue
(
String
@@ -2512,7 +2512,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:209 | void | jakarta.servlet.jsp.tagext.TagSupport.removeValue
+ | PAGES:JAVADOC:209 | void | jakarta.servlet.jsp.tagext.TagSupport.removeValue
(
String
@@ -2524,7 +2524,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:210 | Enumeration | jakarta.servlet.jsp.tagext.TagSupport.getValues
+ | PAGES:JAVADOC:210 | Enumeration | jakarta.servlet.jsp.tagext.TagSupport.getValues
| Enumerate the keys for the values kept by this tag handler.
| true |
@@ -2532,7 +2532,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:211 | TagLibraryValidator | jakarta.servlet.jsp.tagext.TagLibraryValidator.TagLibraryValidator
+ | PAGES:JAVADOC:211 | TagLibraryValidator | jakarta.servlet.jsp.tagext.TagLibraryValidator.TagLibraryValidator
|
| true |
@@ -2540,7 +2540,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:212 | void | jakarta.servlet.jsp.tagext.TagLibraryValidator.setInitParameters
+ | PAGES:JAVADOC:212 | void | jakarta.servlet.jsp.tagext.TagLibraryValidator.setInitParameters
(
Map
@@ -2553,7 +2553,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:213 | Map | jakarta.servlet.jsp.tagext.TagLibraryValidator.getInitParameters
+ | PAGES: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.
@@ -2562,37 +2562,37 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:214 | ValidationMessage[] | jakarta.servlet.jsp.tagext.TagLibraryValidator.validate
+ | PAGES: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.
+ | Validate a Jakarta Pages (JSP) page.
+ This will get invoked once per directive in the Jakarta Pages (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
+ | PAGES: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).
+ | Validate a Jakarta Pages (JSP) page.
+ This will get invoked once per directive in the Jakarta Pages (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
+ | PAGES:JAVADOC:215 | void | jakarta.servlet.jsp.tagext.TagLibraryValidator.release
| Release any data kept by this instance for validation purposes
| true |
@@ -2600,7 +2600,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:216 | String | jakarta.servlet.jsp.tagext.TagLibraryInfo.getURI
+ | PAGES:JAVADOC:216 | String | jakarta.servlet.jsp.tagext.TagLibraryInfo.getURI
| The value of the uri attribute from the taglib directive for this library.
| true |
@@ -2608,7 +2608,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:218 | String | jakarta.servlet.jsp.tagext.TagLibraryInfo.getPrefixString
+ | PAGES:JAVADOC:218 | String | jakarta.servlet.jsp.tagext.TagLibraryInfo.getPrefixString
| The prefix assigned to this taglib from the taglib directive
| true |
@@ -2616,7 +2616,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:219 | String | jakarta.servlet.jsp.tagext.TagLibraryInfo.getShortName
+ | PAGES: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.
@@ -2625,7 +2625,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:220 | String | jakarta.servlet.jsp.tagext.TagLibraryInfo.getReliableURN
+ | PAGES: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.
@@ -2634,7 +2634,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:221 | String | jakarta.servlet.jsp.tagext.TagLibraryInfo.getInfoString
+ | PAGES:JAVADOC:221 | String | jakarta.servlet.jsp.tagext.TagLibraryInfo.getInfoString
| Information (documentation) for this TLD.
| true |
@@ -2642,8 +2642,8 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:222 | String | jakarta.servlet.jsp.tagext.TagLibraryInfo.getRequiredVersion
- | A string describing the required version of the JSP container.
+ | PAGES:JAVADOC:222 | String | jakarta.servlet.jsp.tagext.TagLibraryInfo.getRequiredVersion
+ | A string describing the required version of the Jakarta Pages (JSP) container.
| true |
@@ -2651,7 +2651,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:223 | TagInfo[] | jakarta.servlet.jsp.tagext.TagLibraryInfo.getTags
+ | PAGES:JAVADOC:223 | TagInfo[] | jakarta.servlet.jsp.tagext.TagLibraryInfo.getTags
| An array describing the tags that are defined in this tag library.
| true |
@@ -2659,7 +2659,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:224 | TagFileInfo[] | jakarta.servlet.jsp.tagext.TagLibraryInfo.getTagFiles
+ | PAGES:JAVADOC:224 | TagFileInfo[] | jakarta.servlet.jsp.tagext.TagLibraryInfo.getTagFiles
| An array describing the tag files that are defined in this tag library.
| true |
@@ -2667,7 +2667,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:225 | TagInfo | jakarta.servlet.jsp.tagext.TagLibraryInfo.getTag
+ | PAGES:JAVADOC:225 | TagInfo | jakarta.servlet.jsp.tagext.TagLibraryInfo.getTag
(
String
@@ -2680,7 +2680,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:226 | TagFileInfo | jakarta.servlet.jsp.tagext.TagLibraryInfo.getTagFile
+ | PAGES:JAVADOC:226 | TagFileInfo | jakarta.servlet.jsp.tagext.TagLibraryInfo.getTagFile
(
String
@@ -2693,7 +2693,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:227 | FunctionInfo[] | jakarta.servlet.jsp.tagext.TagLibraryInfo.getFunctions
+ | PAGES:JAVADOC:227 | FunctionInfo[] | jakarta.servlet.jsp.tagext.TagLibraryInfo.getFunctions
| An array describing the functions that are defined in this tag library.
| true |
@@ -2701,7 +2701,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:228 | FunctionInfo | jakarta.servlet.jsp.tagext.TagLibraryInfo.getFunction
+ | PAGES:JAVADOC:228 | FunctionInfo | jakarta.servlet.jsp.tagext.TagLibraryInfo.getFunction
(
String
@@ -2713,7 +2713,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:229 | TagInfo | jakarta.servlet.jsp.tagext.TagInfo.TagInfo
+ | PAGES:JAVADOC:229 | TagInfo | jakarta.servlet.jsp.tagext.TagInfo.TagInfo
(
String
@@ -2725,14 +2725,14 @@ Jakarta Server Pages - 3.1
, 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.
+ This class is to be instantiated only from the TagLibrary code under request from some Jakarta Pages (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
+ | PAGES:JAVADOC:230 | TagInfo | jakarta.servlet.jsp.tagext.TagInfo.TagInfo
(
String
@@ -2748,14 +2748,14 @@ Jakarta Server Pages - 3.1
, 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.
+ This class is to be instantiated only from the TagLibrary code under request from some Jakarta Pages (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
+ | PAGES:JAVADOC:231 | TagInfo | jakarta.servlet.jsp.tagext.TagInfo.TagInfo
(
String
@@ -2772,14 +2772,14 @@ Jakarta Server Pages - 3.1
, 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.
+ This class is to be instantiated only from the TagLibrary code under request from some Jakarta Pages (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
+ | PAGES:JAVADOC:232 | String | jakarta.servlet.jsp.tagext.TagInfo.getTagName
| The name of the Tag.
| true |
@@ -2787,7 +2787,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:233 | TagAttributeInfo[] | jakarta.servlet.jsp.tagext.TagInfo.getAttributes
+ | PAGES: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.
@@ -2796,7 +2796,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:234 | VariableInfo[] | jakarta.servlet.jsp.tagext.TagInfo.getVariableInfo
+ | PAGES:JAVADOC:234 | VariableInfo[] | jakarta.servlet.jsp.tagext.TagInfo.getVariableInfo
(
TagData
@@ -2809,7 +2809,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:235 | boolean | jakarta.servlet.jsp.tagext.TagInfo.isValid
+ | PAGES:JAVADOC:235 | boolean | jakarta.servlet.jsp.tagext.TagInfo.isValid
(
TagData
@@ -2822,7 +2822,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:236 | ValidationMessage[] | jakarta.servlet.jsp.tagext.TagInfo.validate
+ | PAGES:JAVADOC:236 | ValidationMessage[] | jakarta.servlet.jsp.tagext.TagInfo.validate
(
TagData
@@ -2835,7 +2835,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:237 | void | jakarta.servlet.jsp.tagext.TagInfo.setTagExtraInfo
+ | PAGES:JAVADOC:237 | void | jakarta.servlet.jsp.tagext.TagInfo.setTagExtraInfo
(
TagExtraInfo
@@ -2847,7 +2847,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:238 | TagExtraInfo | jakarta.servlet.jsp.tagext.TagInfo.getTagExtraInfo
+ | PAGES:JAVADOC:238 | TagExtraInfo | jakarta.servlet.jsp.tagext.TagInfo.getTagExtraInfo
| The instance (if any) for extra tag information
| true |
@@ -2855,7 +2855,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:239 | String | jakarta.servlet.jsp.tagext.TagInfo.getTagClassName
+ | PAGES:JAVADOC:239 | String | jakarta.servlet.jsp.tagext.TagInfo.getTagClassName
| Name of the class that provides the handler for this tag.
| true |
@@ -2863,15 +2863,15 @@ Jakarta Server Pages - 3.1
| 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.
+ | PAGES: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 default of JSP will be returned.
| true |
| true |
-| JSP:JAVADOC:241 | String | jakarta.servlet.jsp.tagext.TagInfo.getInfoString
+ | PAGES:JAVADOC:241 | String | jakarta.servlet.jsp.tagext.TagInfo.getInfoString
| The information string for the tag.
| true |
@@ -2879,7 +2879,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:242 | void | jakarta.servlet.jsp.tagext.TagInfo.setTagLibrary
+ | PAGES:JAVADOC:242 | void | jakarta.servlet.jsp.tagext.TagInfo.setTagLibrary
(
TagLibraryInfo
@@ -2892,7 +2892,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:243 | TagLibraryInfo | jakarta.servlet.jsp.tagext.TagInfo.getTagLibrary
+ | PAGES:JAVADOC:243 | TagLibraryInfo | jakarta.servlet.jsp.tagext.TagInfo.getTagLibrary
| The instance of TabLibraryInfo we belong to.
| true |
@@ -2900,7 +2900,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:244 | String | jakarta.servlet.jsp.tagext.TagInfo.getDisplayName
+ | PAGES:JAVADOC:244 | String | jakarta.servlet.jsp.tagext.TagInfo.getDisplayName
| Get the displayName or null if not defined.
| true |
@@ -2908,7 +2908,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:245 | String | jakarta.servlet.jsp.tagext.TagInfo.getSmallIcon
+ | PAGES:JAVADOC:245 | String | jakarta.servlet.jsp.tagext.TagInfo.getSmallIcon
| Get the path to the small icon
| true |
@@ -2916,7 +2916,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:246 | String | jakarta.servlet.jsp.tagext.TagInfo.getLargeIcon
+ | PAGES:JAVADOC:246 | String | jakarta.servlet.jsp.tagext.TagInfo.getLargeIcon
| Get the path to the large icon
| true |
@@ -2924,7 +2924,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:247 | TagVariableInfo[] | jakarta.servlet.jsp.tagext.TagInfo.getTagVariableInfos
+ | PAGES:JAVADOC:247 | TagVariableInfo[] | jakarta.servlet.jsp.tagext.TagInfo.getTagVariableInfos
| Get TagVariableInfo objects associated with this TagInfo
| true |
@@ -2932,7 +2932,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:248 | boolean | jakarta.servlet.jsp.tagext.TagInfo.hasDynamicAttributes
+ | PAGES:JAVADOC:248 | boolean | jakarta.servlet.jsp.tagext.TagInfo.hasDynamicAttributes
| Get dynamicAttributes associated with this TagInfo
| true |
@@ -2940,7 +2940,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:258 | TagFileInfo | jakarta.servlet.jsp.tagext.TagFileInfo.TagFileInfo
+ | PAGES:JAVADOC:258 | TagFileInfo | jakarta.servlet.jsp.tagext.TagFileInfo.TagFileInfo
(
String
@@ -2948,14 +2948,14 @@ Jakarta Server Pages - 3.1
, 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.
+ This class is to be instantiated only from the TagLibrary code under request from some Jakarta Pages (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
+ | PAGES:JAVADOC:259 | String | jakarta.servlet.jsp.tagext.TagFileInfo.getName
| The unique action name of this tag.
| true |
@@ -2963,7 +2963,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:260 | String | jakarta.servlet.jsp.tagext.TagFileInfo.getPath
+ | PAGES:JAVADOC:260 | String | jakarta.servlet.jsp.tagext.TagFileInfo.getPath
| Where to find the .tag file implementing this action.
| true |
@@ -2971,7 +2971,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:261 | TagInfo | jakarta.servlet.jsp.tagext.TagFileInfo.getTagInfo
+ | PAGES:JAVADOC:261 | TagInfo | jakarta.servlet.jsp.tagext.TagFileInfo.getTagInfo
| Returns information about this tag, parsed from the directives in the tag file.
| true |
@@ -2979,7 +2979,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:262 | TagExtraInfo | jakarta.servlet.jsp.tagext.TagExtraInfo.TagExtraInfo
+ | PAGES:JAVADOC:262 | TagExtraInfo | jakarta.servlet.jsp.tagext.TagExtraInfo.TagExtraInfo
|
| true |
@@ -2987,7 +2987,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:263 | VariableInfo[] | jakarta.servlet.jsp.tagext.TagExtraInfo.getVariableInfo
+ | PAGES:JAVADOC:263 | VariableInfo[] | jakarta.servlet.jsp.tagext.TagExtraInfo.getVariableInfo
(
TagData
@@ -3000,7 +3000,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:264 | boolean | jakarta.servlet.jsp.tagext.TagExtraInfo.isValid
+ | PAGES:JAVADOC:264 | boolean | jakarta.servlet.jsp.tagext.TagExtraInfo.isValid
(
TagData
@@ -3014,7 +3014,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:265 | ValidationMessage[] | jakarta.servlet.jsp.tagext.TagExtraInfo.validate
+ | PAGES:JAVADOC:265 | ValidationMessage[] | jakarta.servlet.jsp.tagext.TagExtraInfo.validate
(
TagData
@@ -3027,7 +3027,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:266 | void | jakarta.servlet.jsp.tagext.TagExtraInfo.setTagInfo
+ | PAGES:JAVADOC:266 | void | jakarta.servlet.jsp.tagext.TagExtraInfo.setTagInfo
(
TagInfo
@@ -3039,7 +3039,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:267 | TagInfo | jakarta.servlet.jsp.tagext.TagExtraInfo.getTagInfo
+ | PAGES:JAVADOC:267 | TagInfo | jakarta.servlet.jsp.tagext.TagExtraInfo.getTagInfo
| Get the TagInfo for this class.
| true |
@@ -3047,7 +3047,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:268 | TagData | jakarta.servlet.jsp.tagext.TagData.TagData
+ | PAGES:JAVADOC:268 | TagData | jakarta.servlet.jsp.tagext.TagData.TagData
(
Object[][]
@@ -3060,7 +3060,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:269 | TagData | jakarta.servlet.jsp.tagext.TagData.TagData
+ | PAGES:JAVADOC:269 | TagData | jakarta.servlet.jsp.tagext.TagData.TagData
(
Hashtable
@@ -3073,7 +3073,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:270 | String | jakarta.servlet.jsp.tagext.TagData.getId
+ | PAGES:JAVADOC:270 | String | jakarta.servlet.jsp.tagext.TagData.getId
| The value of the tag's id attribute.
| true |
@@ -3081,7 +3081,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:271 | Object | jakarta.servlet.jsp.tagext.TagData.getAttribute
+ | PAGES:JAVADOC:271 | Object | jakarta.servlet.jsp.tagext.TagData.getAttribute
(
String
@@ -3091,7 +3091,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:272 | void | jakarta.servlet.jsp.tagext.TagData.setAttribute
+ | PAGES:JAVADOC:272 | void | jakarta.servlet.jsp.tagext.TagData.setAttribute
(
String
@@ -3104,7 +3104,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:273 | String | jakarta.servlet.jsp.tagext.TagData.getAttributeString
+ | PAGES:JAVADOC:273 | String | jakarta.servlet.jsp.tagext.TagData.getAttributeString
(
String
@@ -3116,7 +3116,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:274 | String | jakarta.servlet.jsp.tagext.TagData.getAttributeString
+ | PAGES:JAVADOC:274 | String | jakarta.servlet.jsp.tagext.TagData.getAttributeString
(
String
@@ -3128,7 +3128,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:275 | Enumeration | jakarta.servlet.jsp.tagext.TagData.getAttributes
+ | PAGES:JAVADOC:275 | Enumeration | jakarta.servlet.jsp.tagext.TagData.getAttributes
| Enumerates the attributes.
| true |
@@ -3136,7 +3136,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:276 | TagAttributeInfo | jakarta.servlet.jsp.tagext.TagAttributeInfo.TagAttributeInfo
+ | PAGES:JAVADOC:276 | TagAttributeInfo | jakarta.servlet.jsp.tagext.TagAttributeInfo.TagAttributeInfo
(
String
@@ -3145,14 +3145,14 @@ Jakarta Server Pages - 3.1
, 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).
+ This class is to be instantiated only from the TagLibrary code under request from some Jakarta Pages (JSP) code that is parsing a TLD (Tag Library Descriptor).
| true |
| true |
-| JSP:JAVADOC:277 | TagAttributeInfo | jakarta.servlet.jsp.tagext.TagAttributeInfo.TagAttributeInfo
+ | PAGES:JAVADOC:277 | TagAttributeInfo | jakarta.servlet.jsp.tagext.TagAttributeInfo.TagAttributeInfo
(
String
@@ -3162,14 +3162,14 @@ Jakarta Server Pages - 3.1
, 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).
+ This class is to be instantiated only from the TagLibrary code under request from some Jakarta Pages (JSP) code that is parsing a TLD (Tag Library Descriptor).
| true |
| true |
-| JSP:JAVADOC:278 | String | jakarta.servlet.jsp.tagext.TagAttributeInfo.getName
+ | PAGES:JAVADOC:278 | String | jakarta.servlet.jsp.tagext.TagAttributeInfo.getName
| The name of this attribute.
| true |
@@ -3177,7 +3177,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:279 | String | jakarta.servlet.jsp.tagext.TagAttributeInfo.getTypeName
+ | PAGES:JAVADOC:279 | String | jakarta.servlet.jsp.tagext.TagAttributeInfo.getTypeName
| The type (as a String) of this attribute.
| true |
@@ -3185,7 +3185,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:280 | boolean | jakarta.servlet.jsp.tagext.TagAttributeInfo.canBeRequestTime
+ | PAGES:JAVADOC:280 | boolean | jakarta.servlet.jsp.tagext.TagAttributeInfo.canBeRequestTime
| Whether this attribute can hold a request-time value.
| true |
@@ -3193,7 +3193,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:281 | boolean | jakarta.servlet.jsp.tagext.TagAttributeInfo.isRequired
+ | PAGES:JAVADOC:281 | boolean | jakarta.servlet.jsp.tagext.TagAttributeInfo.isRequired
| Whether this attribute is required.
| true |
@@ -3201,7 +3201,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:282 | TagAttributeInfo | jakarta.servlet.jsp.tagext.TagAttributeInfo.getIdAttribute
+ | PAGES:JAVADOC:282 | TagAttributeInfo | jakarta.servlet.jsp.tagext.TagAttributeInfo.getIdAttribute
(
TagAttributeInfo[]
@@ -3213,7 +3213,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:283 | boolean | jakarta.servlet.jsp.tagext.TagAttributeInfo.isFragment
+ | PAGES:JAVADOC:283 | boolean | jakarta.servlet.jsp.tagext.TagAttributeInfo.isFragment
| Whether this attribute is of type JspFragment
| true |
@@ -3221,7 +3221,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:284 | String | jakarta.servlet.jsp.tagext.TagAttributeInfo.toString
+ | PAGES:JAVADOC:284 | String | jakarta.servlet.jsp.tagext.TagAttributeInfo.toString
| Returns a String representation of this TagAttributeInfo, suitable for debugging purposes.
| true |
@@ -3229,7 +3229,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:285 | TagAdapter | jakarta.servlet.jsp.tagext.TagAdapter.TagAdapter
+ | PAGES:JAVADOC:285 | TagAdapter | jakarta.servlet.jsp.tagext.TagAdapter.TagAdapter
(
SimpleTag
@@ -3241,7 +3241,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:286 | void | jakarta.servlet.jsp.tagext.TagAdapter.setPageContext
+ | PAGES:JAVADOC:286 | void | jakarta.servlet.jsp.tagext.TagAdapter.setPageContext
(
PageContext
@@ -3253,7 +3253,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:287 | void | jakarta.servlet.jsp.tagext.TagAdapter.setPageContext
+ | PAGES:JAVADOC:287 | void | jakarta.servlet.jsp.tagext.TagAdapter.setPageContext
(
PageContext
@@ -3265,7 +3265,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:288 | void | jakarta.servlet.jsp.tagext.TagAdapter.setParent
+ | PAGES:JAVADOC:288 | void | jakarta.servlet.jsp.tagext.TagAdapter.setParent
(
Tag
@@ -3278,7 +3278,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:289 | void | jakarta.servlet.jsp.tagext.TagAdapter.setParent
+ | PAGES:JAVADOC:289 | void | jakarta.servlet.jsp.tagext.TagAdapter.setParent
(
Tag
@@ -3290,7 +3290,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:290 | Tag | jakarta.servlet.jsp.tagext.TagAdapter.getParent
+ | PAGES: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).
@@ -3299,7 +3299,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:291 | JspTag | jakarta.servlet.jsp.tagext.TagAdapter.getAdaptee
+ | PAGES: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.
@@ -3308,7 +3308,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:292 | int | jakarta.servlet.jsp.tagext.TagAdapter.doStartTag
+ | PAGES:JAVADOC:292 | int | jakarta.servlet.jsp.tagext.TagAdapter.doStartTag
| Must not be called.
| true |
@@ -3316,7 +3316,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:293 | int | jakarta.servlet.jsp.tagext.TagAdapter.doStartTag
+ | PAGES:JAVADOC:293 | int | jakarta.servlet.jsp.tagext.TagAdapter.doStartTag
throws
JspException
| never thrown | true |
@@ -3324,7 +3324,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:294 | int | jakarta.servlet.jsp.tagext.TagAdapter.doStartTag
+ | PAGES:JAVADOC:294 | int | jakarta.servlet.jsp.tagext.TagAdapter.doStartTag
throws
UnsupportedOperationException
| Must not be called | true |
@@ -3332,7 +3332,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:295 | int | jakarta.servlet.jsp.tagext.TagAdapter.doEndTag
+ | PAGES:JAVADOC:295 | int | jakarta.servlet.jsp.tagext.TagAdapter.doEndTag
| Must not be called.
| true |
@@ -3340,7 +3340,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:296 | int | jakarta.servlet.jsp.tagext.TagAdapter.doEndTag
+ | PAGES:JAVADOC:296 | int | jakarta.servlet.jsp.tagext.TagAdapter.doEndTag
throws
JspException
| never thrown | true |
@@ -3348,7 +3348,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:297 | int | jakarta.servlet.jsp.tagext.TagAdapter.doEndTag
+ | PAGES:JAVADOC:297 | int | jakarta.servlet.jsp.tagext.TagAdapter.doEndTag
throws
UnsupportedOperationException
| Must not be called | true |
@@ -3356,7 +3356,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:298 | void | jakarta.servlet.jsp.tagext.TagAdapter.release
+ | PAGES:JAVADOC:298 | void | jakarta.servlet.jsp.tagext.TagAdapter.release
| Must not be called.
| true |
@@ -3364,7 +3364,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:299 | void | jakarta.servlet.jsp.tagext.TagAdapter.release
+ | PAGES:JAVADOC:299 | void | jakarta.servlet.jsp.tagext.TagAdapter.release
throws
UnsupportedOperationException
| Must not be called | true |
@@ -3372,7 +3372,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:300 | SimpleTagSupport | jakarta.servlet.jsp.tagext.SimpleTagSupport.SimpleTagSupport
+ | PAGES:JAVADOC:300 | SimpleTagSupport | jakarta.servlet.jsp.tagext.SimpleTagSupport.SimpleTagSupport
|
| true |
@@ -3380,7 +3380,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:301 | void | jakarta.servlet.jsp.tagext.SimpleTagSupport.doTag
+ | PAGES:JAVADOC:301 | void | jakarta.servlet.jsp.tagext.SimpleTagSupport.doTag
| Default processing of the tag does nothing.
@@ -3389,7 +3389,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:302 | void | jakarta.servlet.jsp.tagext.SimpleTagSupport.doTag
+ | PAGES: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 |
@@ -3397,7 +3397,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:303 | void | jakarta.servlet.jsp.tagext.SimpleTagSupport.doTag
+ | PAGES: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 |
@@ -3405,7 +3405,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:304 | void | jakarta.servlet.jsp.tagext.SimpleTagSupport.doTag
+ | PAGES: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 |
@@ -3413,7 +3413,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:305 | void | jakarta.servlet.jsp.tagext.SimpleTagSupport.setParent
+ | PAGES:JAVADOC:305 | void | jakarta.servlet.jsp.tagext.SimpleTagSupport.setParent
(
JspTag
@@ -3425,7 +3425,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:306 | JspTag | jakarta.servlet.jsp.tagext.SimpleTagSupport.getParent
+ | PAGES:JAVADOC:306 | JspTag | jakarta.servlet.jsp.tagext.SimpleTagSupport.getParent
| Returns the parent of this tag, for collaboration purposes.
| true |
@@ -3433,12 +3433,12 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:307 | void | jakarta.servlet.jsp.tagext.SimpleTagSupport.setJspContext
+ | PAGES:JAVADOC:307 | void | jakarta.servlet.jsp.tagext.SimpleTagSupport.setJspContext
(
JspContext
)
- | Stores the provided JSP context in the protected jspContext field.
+ | Stores the provided Jakarta Pages (JSP) context in the protected jspContext field.
| true |
@@ -3446,7 +3446,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:308 | JspContext | jakarta.servlet.jsp.tagext.SimpleTagSupport.getJspContext
+ | PAGES:JAVADOC:308 | JspContext | jakarta.servlet.jsp.tagext.SimpleTagSupport.getJspContext
| Returns the page context passed in by the container via setJspContext.
| true |
@@ -3454,7 +3454,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:309 | void | jakarta.servlet.jsp.tagext.SimpleTagSupport.setJspBody
+ | PAGES:JAVADOC:309 | void | jakarta.servlet.jsp.tagext.SimpleTagSupport.setJspBody
(
JspFragment
@@ -3467,7 +3467,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:310 | JspFragment | jakarta.servlet.jsp.tagext.SimpleTagSupport.getJspBody
+ | PAGES:JAVADOC:310 | JspFragment | jakarta.servlet.jsp.tagext.SimpleTagSupport.getJspBody
| Returns the body passed in by the container via setJspBody
| true |
@@ -3475,21 +3475,21 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:311 | JspTag | jakarta.servlet.jsp.tagext.SimpleTagSupport.findAncestorWithClass
+ | PAGES: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.
+ 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 Jakarta 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
+ | PAGES:JAVADOC:312 | PageData | jakarta.servlet.jsp.tagext.PageData.PageData
|
| true |
@@ -3497,16 +3497,16 @@ Jakarta Server Pages - 3.1
| 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.
+ | PAGES:JAVADOC:313 | InputStream | jakarta.servlet.jsp.tagext.PageData.getInputStream
+ | Returns an input stream on the XML view of a Jakarta Pages (JSP) page. The stream is encoded in UTF-8.
+ Recall tht the XML view of a Jakarta Pages (JSP) page has the include directives expanded.
| true |
| true |
-| JSP:JAVADOC:314 | FunctionInfo | jakarta.servlet.jsp.tagext.FunctionInfo.FunctionInfo
+ | PAGES:JAVADOC:314 | FunctionInfo | jakarta.servlet.jsp.tagext.FunctionInfo.FunctionInfo
(
String
@@ -3520,7 +3520,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:315 | String | jakarta.servlet.jsp.tagext.FunctionInfo.getName
+ | PAGES:JAVADOC:315 | String | jakarta.servlet.jsp.tagext.FunctionInfo.getName
| The name of the function.
| true |
@@ -3528,7 +3528,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:316 | String | jakarta.servlet.jsp.tagext.FunctionInfo.getFunctionClass
+ | PAGES:JAVADOC:316 | String | jakarta.servlet.jsp.tagext.FunctionInfo.getFunctionClass
| The class of the function.
| true |
@@ -3536,7 +3536,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:317 | String | jakarta.servlet.jsp.tagext.FunctionInfo.getFunctionSignature
+ | PAGES:JAVADOC:317 | String | jakarta.servlet.jsp.tagext.FunctionInfo.getFunctionSignature
| The signature of the function.
| true |
@@ -3544,16 +3544,16 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:318 | BodyTagSupport | jakarta.servlet.jsp.tagext.BodyTagSupport.BodyTagSupport
+ | PAGES: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.
+ This constructor is called by the code generated by the Jakarta Pages (JSP) translator.
| true |
| true |
-| JSP:JAVADOC:319 | int | jakarta.servlet.jsp.tagext.BodyTagSupport.doStartTag
+ | PAGES:JAVADOC:319 | int | jakarta.servlet.jsp.tagext.BodyTagSupport.doStartTag
| Default processing of the start tag returning EVAL_BODY_BUFFERED
@@ -3562,7 +3562,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:320 | int | jakarta.servlet.jsp.tagext.BodyTagSupport.doStartTag
+ | PAGES:JAVADOC:320 | int | jakarta.servlet.jsp.tagext.BodyTagSupport.doStartTag
throws
JspException
| if an error occurred while processing this tag | true |
@@ -3570,7 +3570,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:321 | int | jakarta.servlet.jsp.tagext.BodyTagSupport.doEndTag
+ | PAGES:JAVADOC:321 | int | jakarta.servlet.jsp.tagext.BodyTagSupport.doEndTag
| Default processing of the end tag returning EVAL_PAGE.
@@ -3579,7 +3579,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:322 | int | jakarta.servlet.jsp.tagext.BodyTagSupport.doEndTag
+ | PAGES:JAVADOC:322 | int | jakarta.servlet.jsp.tagext.BodyTagSupport.doEndTag
throws
JspException
| if an error occurred while processing this tag | true |
@@ -3587,7 +3587,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:323 | void | jakarta.servlet.jsp.tagext.BodyTagSupport.setBodyContent
+ | PAGES:JAVADOC:323 | void | jakarta.servlet.jsp.tagext.BodyTagSupport.setBodyContent
(
BodyContent
@@ -3602,7 +3602,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:324 | void | jakarta.servlet.jsp.tagext.BodyTagSupport.doInitBody
+ | PAGES:JAVADOC:324 | void | jakarta.servlet.jsp.tagext.BodyTagSupport.doInitBody
| Prepare for evaluation of the body just before the first body evaluation: no action.
@@ -3613,7 +3613,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:325 | void | jakarta.servlet.jsp.tagext.BodyTagSupport.doInitBody
+ | PAGES:JAVADOC:325 | void | jakarta.servlet.jsp.tagext.BodyTagSupport.doInitBody
throws
JspException
| if an error occurred while processing this tag | true |
@@ -3621,7 +3621,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:326 | int | jakarta.servlet.jsp.tagext.BodyTagSupport.doAfterBody
+ | PAGES: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).
@@ -3632,7 +3632,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:327 | int | jakarta.servlet.jsp.tagext.BodyTagSupport.doAfterBody
+ | PAGES:JAVADOC:327 | int | jakarta.servlet.jsp.tagext.BodyTagSupport.doAfterBody
throws
JspException
| if an error occurred while processing this tag | true |
@@ -3640,7 +3640,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:328 | void | jakarta.servlet.jsp.tagext.BodyTagSupport.release
+ | PAGES:JAVADOC:328 | void | jakarta.servlet.jsp.tagext.BodyTagSupport.release
| Release state.
@@ -3649,7 +3649,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:329 | BodyContent | jakarta.servlet.jsp.tagext.BodyTagSupport.getBodyContent
+ | PAGES:JAVADOC:329 | BodyContent | jakarta.servlet.jsp.tagext.BodyTagSupport.getBodyContent
| Get current bodyContent.
| true |
@@ -3657,7 +3657,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:330 | JspWriter | jakarta.servlet.jsp.tagext.BodyTagSupport.getPreviousOut
+ | PAGES:JAVADOC:330 | JspWriter | jakarta.servlet.jsp.tagext.BodyTagSupport.getPreviousOut
| Get surrounding out JspWriter.
| true |
@@ -3665,7 +3665,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:331 | void | jakarta.servlet.jsp.tagext.BodyContent.flush
+ | PAGES: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.
@@ -3674,7 +3674,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:332 | void | jakarta.servlet.jsp.tagext.BodyContent.flush
+ | PAGES:JAVADOC:332 | void | jakarta.servlet.jsp.tagext.BodyContent.flush
throws
IOException
| always thrown | true |
@@ -3682,7 +3682,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:333 | void | jakarta.servlet.jsp.tagext.BodyContent.clearBody
+ | PAGES:JAVADOC:333 | void | jakarta.servlet.jsp.tagext.BodyContent.clearBody
| Clear the body without throwing any exceptions.
| true |
@@ -3690,7 +3690,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:334 | Reader | jakarta.servlet.jsp.tagext.BodyContent.getReader
+ | PAGES:JAVADOC:334 | Reader | jakarta.servlet.jsp.tagext.BodyContent.getReader
| Return the value of this BodyContent as a Reader.
| true |
@@ -3698,7 +3698,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:335 | String | jakarta.servlet.jsp.tagext.BodyContent.getString
+ | PAGES:JAVADOC:335 | String | jakarta.servlet.jsp.tagext.BodyContent.getString
| Return the value of the BodyContent as a String.
| true |
@@ -3706,7 +3706,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:336 | void | jakarta.servlet.jsp.tagext.BodyContent.writeOut
+ | PAGES:JAVADOC:336 | void | jakarta.servlet.jsp.tagext.BodyContent.writeOut
(
Writer
@@ -3719,7 +3719,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:337 | void | jakarta.servlet.jsp.tagext.BodyContent.writeOut
+ | PAGES:JAVADOC:337 | void | jakarta.servlet.jsp.tagext.BodyContent.writeOut
(
Writer
@@ -3731,7 +3731,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:338 | JspWriter | jakarta.servlet.jsp.tagext.BodyContent.getEnclosingWriter
+ | PAGES:JAVADOC:338 | JspWriter | jakarta.servlet.jsp.tagext.BodyContent.getEnclosingWriter
| Get the enclosing JspWriter.
| true |
@@ -3739,7 +3739,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:339 | void | jakarta.servlet.jsp.tagext.TryCatchFinally.doCatch
+ | PAGES:JAVADOC:339 | void | jakarta.servlet.jsp.tagext.TryCatchFinally.doCatch
(
Throwable
@@ -3752,7 +3752,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:340 | void | jakarta.servlet.jsp.tagext.TryCatchFinally.doCatch
+ | PAGES:JAVADOC:340 | void | jakarta.servlet.jsp.tagext.TryCatchFinally.doCatch
(
Throwable
@@ -3764,7 +3764,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:341 | void | jakarta.servlet.jsp.tagext.TryCatchFinally.doFinally
+ | PAGES: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.
@@ -3773,35 +3773,35 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:342 | void | jakarta.servlet.jsp.tagext.Tag.setPageContext
+ | PAGES: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().
+ This method is invoked by the Jakarta Pages (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
+ | PAGES: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.
+ Invoked by the Jakarta Pages (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
+ | PAGES: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.
+ 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 Jakarta standard tag library.
| true |
@@ -3809,37 +3809,37 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:345 | int | jakarta.servlet.jsp.tagext.Tag.doStartTag
+ | PAGES: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.
+ This method is invoked by the Jakarta Pages (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
+ | PAGES: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.
+ This method is invoked by the Jakarta Pages (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
+ | PAGES: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.
+ This method is invoked by the Jakarta Pages (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 Jakarta Pages (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 |
+ | PAGES:JAVADOC:348 | int | jakarta.servlet.jsp.tagext.Tag.doStartTag
+ | The Jakarta Pages (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
+ | PAGES:JAVADOC:349 | int | jakarta.servlet.jsp.tagext.Tag.doStartTag
throws
JspException
| if an error occurred while processing this tag | true |
@@ -3847,38 +3847,38 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:350 | int | jakarta.servlet.jsp.tagext.Tag.doEndTag
+ | PAGES: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.
+ This method is invoked by the Jakarta Pages (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
+ | PAGES: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.
+ This method is invoked by the Jakarta Pages (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
+ | PAGES: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().
+ This method is invoked by the Jakarta Pages (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 Jakarta Pages (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 |
+ | PAGES:JAVADOC:353 | int | jakarta.servlet.jsp.tagext.Tag.doEndTag
+ | The Jakarta Pages (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
+ | PAGES:JAVADOC:354 | int | jakarta.servlet.jsp.tagext.Tag.doEndTag
throws
JspException
| if an error occurred while processing this tag | true |
@@ -3886,16 +3886,16 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:355 | void | jakarta.servlet.jsp.tagext.Tag.release
+ | PAGES: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.
+ The page compiler guarantees that Jakarta Pages (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
+ | PAGES: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.
@@ -3904,13 +3904,13 @@ Jakarta Server Pages - 3.1
| 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 |
+ | PAGES:JAVADOC:400 | void | jakarta.servlet.jsp.tagext.SimpleTag.doTag
+ | The Jakarta Pages (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
+ | PAGES:JAVADOC:357 | void | jakarta.servlet.jsp.tagext.SimpleTag.doTag
throws
JspException
| If an error occurred while processing this tag. | true |
@@ -3918,7 +3918,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:358 | void | jakarta.servlet.jsp.tagext.SimpleTag.doTag
+ | PAGES:JAVADOC:358 | void | jakarta.servlet.jsp.tagext.SimpleTag.doTag
throws
IOException
| If there was an error writing to the output stream. | true |
@@ -3926,7 +3926,7 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:359 | void | jakarta.servlet.jsp.tagext.SimpleTag.doTag
+ | PAGES: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 |
@@ -3934,7 +3934,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:360 | void | jakarta.servlet.jsp.tagext.SimpleTag.setParent
+ | PAGES:JAVADOC:360 | void | jakarta.servlet.jsp.tagext.SimpleTag.setParent
(
JspTag
@@ -3946,7 +3946,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:361 | JspTag | jakarta.servlet.jsp.tagext.SimpleTag.getParent
+ | PAGES:JAVADOC:361 | JspTag | jakarta.servlet.jsp.tagext.SimpleTag.getParent
| Returns the parent of this tag, for collaboration purposes.
| true |
@@ -3954,12 +3954,12 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:362 | void | jakarta.servlet.jsp.tagext.SimpleTag.setJspContext
+ | PAGES:JAVADOC:362 | void | jakarta.servlet.jsp.tagext.SimpleTag.setJspContext
(
JspContext
)
- | Stores the provided JSP context in the protected jspContext field.
+ | Stores the provided Jakarta Pages (JSP) context in the protected jspContext field.
| true |
@@ -3967,20 +3967,20 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:363 | void | jakarta.servlet.jsp.tagext.SimpleTag.setJspBody
+ | PAGES: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().
+ This method is invoked by the Jakarta Pages (JSP) page implementation object prior to doTag().
| true |
| true |
-| JSP:JAVADOC:403 | JspFragment | jakarta.servlet.jsp.tagext.JspFragment.JspFragment
+ | PAGES:JAVADOC:403 | JspFragment | jakarta.servlet.jsp.tagext.JspFragment.JspFragment
|
| true |
@@ -3988,13 +3988,13 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:404 | JspContext | jakarta.servlet.jsp.tagext.JspFragment.getJspContext
+ | PAGES: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
+ | PAGES:JAVADOC:382 | void | jakarta.servlet.jsp.tagext.JspFragment.invoke
(
Writer
@@ -4004,7 +4004,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:401 | void | jakarta.servlet.jsp.tagext.JspFragment.invoke
+ | PAGES:JAVADOC:401 | void | jakarta.servlet.jsp.tagext.JspFragment.invoke
(
Writer
@@ -4016,7 +4016,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:402 | void | jakarta.servlet.jsp.tagext.JspFragment.invoke
+ | PAGES:JAVADOC:402 | void | jakarta.servlet.jsp.tagext.JspFragment.invoke
(
Writer
@@ -4028,7 +4028,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:367 | void | jakarta.servlet.jsp.tagext.JspFragment.invoke
+ | PAGES:JAVADOC:367 | void | jakarta.servlet.jsp.tagext.JspFragment.invoke
(
Writer
@@ -4040,31 +4040,31 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:368 | int | jakarta.servlet.jsp.tagext.IterationTag.doAfterBody
+ | PAGES: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.
+ This method is invoked by the Jakarta Pages (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
+ | PAGES: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).
+ This method is invoked by the Jakarta Pages (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
+ | PAGES: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.
+ This method is invoked by the Jakarta Pages (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
+ | PAGES:JAVADOC:370 | int | jakarta.servlet.jsp.tagext.IterationTag.doAfterBody
throws
JspException
|
@@ -4074,15 +4074,15 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:371 | int | jakarta.servlet.jsp.tagext.IterationTag.doAfterBody
+ | PAGES: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().
+ The Jakarta Pages (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
+ | PAGES:JAVADOC:372 | void | jakarta.servlet.jsp.tagext.DynamicAttributes.setDynamicAttribute
(
String
@@ -4096,7 +4096,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:373 | void | jakarta.servlet.jsp.tagext.DynamicAttributes.setDynamicAttribute
+ | PAGES:JAVADOC:373 | void | jakarta.servlet.jsp.tagext.DynamicAttributes.setDynamicAttribute
(
String
@@ -4110,27 +4110,27 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:374 | void | jakarta.servlet.jsp.tagext.BodyTag.setBodyContent
+ | PAGES: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.
+ This method is invoked by the Jakarta Pages (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
+ | PAGES: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.
+ This method is invoked by the Jakarta Pages (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
+ | PAGES: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 |
@@ -4138,13 +4138,13 @@ Jakarta Server Pages - 3.1
| 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 |
+ | PAGES:JAVADOC:377 | void | jakarta.servlet.jsp.tagext.BodyTag.doInitBody
+ | The Jakarta Pages (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
+ | PAGES:JAVADOC:378 | void | jakarta.servlet.jsp.tagext.BodyTag.doInitBody
throws
JspException
| If an error occurred while processing this tag | true |
@@ -4152,21 +4152,21 @@ Jakarta Server Pages - 3.1
| false |
-| JSP:JAVADOC:406 | void | jakarta.servlet.jsp.HttpJspPage._jspService
+ | PAGES: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.
+ | The _jspService()method corresponds to the body of the Jakarta Pages (JSP) page.
+ This method is defined automatically by the Jakarta Pages (JSP) container and should never be defined by the Jakarta Pages (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 Jakarta Pages (JSP) specification.
| true |
| true |
-| JSP:JAVADOC:407 | void | jakarta.servlet.jsp.HttpJspPage._jspService
+ | PAGES:JAVADOC:407 | void | jakarta.servlet.jsp.HttpJspPage._jspService
(
HttpServletRequest
@@ -4174,12 +4174,12 @@ Jakarta Server Pages - 3.1
)
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 |
+ | Thrown if an error occurred during the processing of the Jakarta Pages (JSP) page and that the container should take appropriate action to clean up the request. | true |
| true |
-| JSP:JAVADOC:408 | void | jakarta.servlet.jsp.HttpJspPage._jspService
+ | PAGES:JAVADOC:408 | void | jakarta.servlet.jsp.HttpJspPage._jspService
(
HttpServletRequest
@@ -4192,40 +4192,40 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:409 | void | jakarta.servlet.jsp.JspApplicationContext.addELContextListener
+ | PAGES: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.
+ At a minimum, the ELContext objects created will contain a reference to the JspContext for this request, which is added by the Jakarta Pages (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
+ | PAGES: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.
+ | Adds an ELResolver to affect the way EL variables and properties are resolved for EL expressions appearing in Jakarta Pages (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.
+ 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 Jakarta Pages (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 Jakarta Pages (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
+ | PAGES: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 |
@@ -4233,13 +4233,13 @@ Jakarta Server Pages - 3.1
| 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.
+ | PAGES:JAVADOC:412 | VariableResolver | jakarta.servlet.jsp.JspContext.getVariableResolver
+ | Returns an instance of a VariableResolver that provides access to the implicit objects specified in the Jakarta Pages (JSP) specification using this JspContext as the context object.
| true | true | true |
-| JSP:JAVADOC:413 | JspFactory | jakarta.servlet.jsp.JspFactory.getDefaultFactory
+ | PAGES:JAVADOC:413 | JspFactory | jakarta.servlet.jsp.JspFactory.getDefaultFactory
| Returns the default factory for this implementation.
| true |
@@ -4247,8 +4247,8 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:414 | JspEngineInfo | jakarta.servlet.jsp.JspFactory.getEngineInfo
- | called to get implementation-specific information on the current JSP engine.
+ | PAGES:JAVADOC:414 | JspEngineInfo | jakarta.servlet.jsp.JspFactory.getEngineInfo
+ | called to get implementation-specific information on the current Jakarta Pages (JSP) engine.
| true |
@@ -4256,7 +4256,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:415 | JspApplicationContext | jakarta.servlet.jsp.JspFactory.getJspApplicationContext
+ | PAGES:JAVADOC:415 | JspApplicationContext | jakarta.servlet.jsp.JspFactory.getJspApplicationContext
(
ServletContext
@@ -4268,7 +4268,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:416 | PageContext | jakarta.servlet.jsp.JspFactory.getPageContext
+ | PAGES:JAVADOC:416 | PageContext | jakarta.servlet.jsp.JspFactory.getPageContext
(
Servlet
@@ -4280,7 +4280,7 @@ Jakarta Server Pages - 3.1
, 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().
+ This method is typically called early in the processing of the _jspService() method of a Jakarta Pages (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 |
@@ -4288,7 +4288,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:417 | JspFactory | jakarta.servlet.jsp.JspFactory.JspFactory
+ | PAGES:JAVADOC:417 | JspFactory | jakarta.servlet.jsp.JspFactory.JspFactory
| Sole constructor.
(For invocation by subclass constructors, typically implicit.)
@@ -4297,33 +4297,33 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:418 | void | jakarta.servlet.jsp.JspFactory.releasePageContext
+ | PAGES: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.
+ Results in PageContext.release() being invoked. This method should be invoked prior to returning from the _jspService() method of a Jakarta Pages (JSP) page implementation class.
| true |
| true |
-| JSP:JAVADOC:419 | void | jakarta.servlet.jsp.JspFactory.setDefaultFactory
+ | PAGES: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.
+ It is illegal for any principal other than the Jakarta Pages (JSP) Engine runtime to call this method.
| true |
| true |
-| JSP:JAVADOC:420 | Class | jakarta.servlet.jsp.el.ImplicitObjectELResolver.getCommonPropertyType
+ | PAGES:JAVADOC:420 | Class | jakarta.servlet.jsp.el.ImplicitObjectELResolver.getCommonPropertyType
(
ELContext
@@ -4337,31 +4337,31 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:421 | Iterator | jakarta.servlet.jsp.el.ImplicitObjectELResolver.getFeatureDescriptors
+ | PAGES: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.
+ | If the base object is null, and the property matches the name of a Jakarta Pages (JSP) implicit object, returns an Iterator containing FeatureDescriptor objects with information about each Jakarta Pages (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.
+ Otherwise, returns null. The Iterator returned must contain one instance of java.beans.FeatureDescriptor for each of the EL implicit objects defined by the Jakarta Pages (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
+ | PAGES: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().
+ | If the base object is null, and the property matches the name of a Jakarta Pages (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 |
@@ -4369,14 +4369,14 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:423 | Object | jakarta.servlet.jsp.el.ImplicitObjectELResolver.getValue
+ | PAGES: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.
+ | If the base object is null, and the property matches the name of a Jakarta Pages (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 |
@@ -4384,7 +4384,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:424 | ImplicitObjectELResolver | jakarta.servlet.jsp.el.ImplicitObjectELResolver.ImplicitObjectELResolver
+ | PAGES:JAVADOC:424 | ImplicitObjectELResolver | jakarta.servlet.jsp.el.ImplicitObjectELResolver.ImplicitObjectELResolver
|
| true |
@@ -4392,14 +4392,14 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:425 | boolean | jakarta.servlet.jsp.el.ImplicitObjectELResolver.isReadOnly
+ | PAGES: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.
+ | If the base object is null, and the property matches the name of a Jakarta Pages (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 |
@@ -4407,7 +4407,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:426 | void | jakarta.servlet.jsp.el.ImplicitObjectELResolver.setValue
+ | PAGES:JAVADOC:426 | void | jakarta.servlet.jsp.el.ImplicitObjectELResolver.setValue
(
ELContext
@@ -4415,7 +4415,7 @@ Jakarta Server Pages - 3.1
, 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.
+ | If the base object is null, and the property matches the name of a Jakarta Pages (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 |
@@ -4423,7 +4423,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:427 | Class | jakarta.servlet.jsp.el.ScopedAttributeELResolver.getCommonPropertyType
+ | PAGES:JAVADOC:427 | Class | jakarta.servlet.jsp.el.ScopedAttributeELResolver.getCommonPropertyType
(
ELContext
@@ -4437,7 +4437,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:428 | Iterator | jakarta.servlet.jsp.el.ScopedAttributeELResolver.getFeatureDescriptors
+ | PAGES:JAVADOC:428 | Iterator | jakarta.servlet.jsp.el.ScopedAttributeELResolver.getFeatureDescriptors
(
ELContext
@@ -4454,7 +4454,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:429 | Class | jakarta.servlet.jsp.el.ScopedAttributeELResolver.getType
+ | PAGES:JAVADOC:429 | Class | jakarta.servlet.jsp.el.ScopedAttributeELResolver.getType
(
ELContext
@@ -4469,7 +4469,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:430 | Object | jakarta.servlet.jsp.el.ScopedAttributeELResolver.getValue
+ | PAGES:JAVADOC:430 | Object | jakarta.servlet.jsp.el.ScopedAttributeELResolver.getValue
(
ELContext
@@ -4484,7 +4484,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:431 | boolean | jakarta.servlet.jsp.el.ScopedAttributeELResolver.isReadOnly
+ | PAGES:JAVADOC:431 | boolean | jakarta.servlet.jsp.el.ScopedAttributeELResolver.isReadOnly
(
ELContext
@@ -4499,7 +4499,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:432 | ScopedAttributeELResolver | jakarta.servlet.jsp.el.ScopedAttributeELResolver.ScopedAttributeELResolver
+ | PAGES:JAVADOC:432 | ScopedAttributeELResolver | jakarta.servlet.jsp.el.ScopedAttributeELResolver.ScopedAttributeELResolver
|
| true |
@@ -4507,7 +4507,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:433 | void | jakarta.servlet.jsp.el.ScopedAttributeELResolver.setValue
+ | PAGES:JAVADOC:433 | void | jakarta.servlet.jsp.el.ScopedAttributeELResolver.setValue
(
ELContext
@@ -4523,7 +4523,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:434 | void | jakarta.servlet.jsp.tagext.JspIdConsumer.setJspId
+ | PAGES:JAVADOC:434 | void | jakarta.servlet.jsp.tagext.JspIdConsumer.setJspId
(
String
@@ -4536,7 +4536,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:435 | TagAttributeInfo | jakarta.servlet.jsp.tagext.TagAttributeInfo.TagAttributeInfo
+ | PAGES:JAVADOC:435 | TagAttributeInfo | jakarta.servlet.jsp.tagext.TagAttributeInfo.TagAttributeInfo
(
String
@@ -4551,14 +4551,14 @@ Jakarta Server Pages - 3.1
, 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).
+ This class is to be instantiated only from the TagLibrary code under request from some Jakarta Pages (JSP) code that is parsing a TLD (Tag Library Descriptor).
| true |
| true |
-| JSP:JAVADOC:436 | boolean | jakarta.servlet.jsp.tagext.TagAttributeInfo.isDeferredValue
+ | PAGES: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.
@@ -4567,7 +4567,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:437 | boolean | jakarta.servlet.jsp.tagext.TagAttributeInfo.isDeferredMethod
+ | PAGES: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.
@@ -4576,7 +4576,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:438 | String | jakarta.servlet.jsp.tagext.TagAttributeInfo.getExpectedTypeName
+ | PAGES: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.
@@ -4585,7 +4585,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:439 | String | jakarta.servlet.jsp.tagext.TagAttributeInfo.getMethodSignature
+ | PAGES: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.
@@ -4594,7 +4594,7 @@ Jakarta Server Pages - 3.1
| true |
-| JSP:JAVADOC:440 | TagLibraryInfo[] | jakarta.servlet.jsp.tagext.TagLibraryInfo.getTagLibraryInfos
+ | PAGES: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.
diff --git a/tck/docs/assertions/JakartaServerPagesSpecAssertions.html b/tck/docs/assertions/JakartaServerPagesSpecAssertions.html
index 21c51430..4bc200dc 100644
--- a/tck/docs/assertions/JakartaServerPagesSpecAssertions.html
+++ b/tck/docs/assertions/JakartaServerPagesSpecAssertions.html
@@ -51,4938 +51,4938 @@ Jakarta Server Pages - 3.1
| 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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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.
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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.
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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 |
+ | PAGES: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:
+ | PAGES: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.
diff --git a/tck/docs/userguide/src/main/jbake/content/attributes.conf b/tck/docs/userguide/src/main/jbake/content/attributes.conf
index 48cd05f9..217513b9 100644
--- a/tck/docs/userguide/src/main/jbake/content/attributes.conf
+++ b/tck/docs/userguide/src/main/jbake/content/attributes.conf
@@ -1,6 +1,5 @@
-:TechnologyFullName: Jakarta Server Pages
-:TechnologyShortName: Server Pages
-:LegacyAcronym: JSP
+:TechnologyFullName: Jakarta Pages
+:TechnologyShortName: Pages
:TechnologyVersion: 4.0
:ReleaseDate: March 2024
:CopyrightDates: 2017, 2024
diff --git a/tck/docs/userguide/src/main/jbake/content/title.inc b/tck/docs/userguide/src/main/jbake/content/title.inc
index afe281cc..1a196542 100644
--- a/tck/docs/userguide/src/main/jbake/content/title.inc
+++ b/tck/docs/userguide/src/main/jbake/content/title.inc
@@ -4,10 +4,7 @@ This is included at the tail end of the Title page.
The following section should be customized for the technology.
This is provided to allow each technology to customize legacy acronym names
that are used in this TCK.
-Be sure to customize LegacyAcronym in attributes.conf
Add additional lines as needed for acronyms found in your TCK user guide.
///////////////////////////////////////////////////////////////////////
-References in this document to {LegacyAcronym} refer to the {TechnologyFullName} unless otherwise noted.
-
References in this document to JSTL refer to the Jakarta Standard Tag Library unless otherwise noted.
\ No newline at end of file
diff --git a/tck/pom.xml b/tck/pom.xml
index 5116de6c..ece8d77b 100644
--- a/tck/pom.xml
+++ b/tck/pom.xml
@@ -65,7 +65,7 @@
- JSP dev mailing list
+ Jakarta Pages (JSP) dev mailing list
jsp-dev@eclipse.org
https://accounts.eclipse.org/mailing-list/jsp-dev
https://accounts.eclipse.org/mailing-list/jsp-dev
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/el/implicitobjelresolver/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/el/implicitobjelresolver/URLClientIT.java
index 2357125b..ada4ed1f 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/el/implicitobjelresolver/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/el/implicitobjelresolver/URLClientIT.java
@@ -76,8 +76,8 @@ public static WebArchive createDeployment() {
/*
* @testName: implicitObjElResolverTest
*
- * @assertion_ids: JSP:JAVADOC:420; JSP:JAVADOC:421; JSP:JAVADOC:422;
- * JSP:JAVADOC:423; JSP:JAVADOC:425; JSP:JAVADOC:426
+ * @assertion_ids: PAGES:JAVADOC:420; PAGES:JAVADOC:421; PAGES:JAVADOC:422;
+ * PAGES:JAVADOC:423; PAGES:JAVADOC:425; PAGES:JAVADOC:426
*
* @test_Strategy: Obtain an ImplicitObjectELResolver via the PageContext and
* verify that API calls work as expected: setValue() setValue() throws
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/el/scopedattrelresolver/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/el/scopedattrelresolver/URLClientIT.java
index f503b3d1..e17facd9 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/el/scopedattrelresolver/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/el/scopedattrelresolver/URLClientIT.java
@@ -76,8 +76,8 @@ public static WebArchive createDeployment() {
/*
* @testName: scopedAttrElResolverTest
*
- * @assertion_ids: JSP:JAVADOC:427; JSP:JAVADOC:428; JSP:JAVADOC:429;
- * JSP:JAVADOC:430; JSP:JAVADOC:431; JSP:JAVADOC:433
+ * @assertion_ids: PAGES:JAVADOC:427; PAGES:JAVADOC:428; PAGES:JAVADOC:429;
+ * PAGES:JAVADOC:430; PAGES:JAVADOC:431; PAGES:JAVADOC:433
*
* @test_Strategy: Obtain an ScopedAttributeELResolver via the PageContext and
* verify that API calls work as expected: setValue() getValue() getType()
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/errordata/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/errordata/URLClientIT.java
index 10c67863..5fcf742f 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/errordata/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/errordata/URLClientIT.java
@@ -72,7 +72,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: errorDataConstructorTest
*
- * @assertion_ids: JSP:JAVADOC:1
+ * @assertion_ids: PAGES:JAVADOC:1
*
* @test_Strategy: Validate proper construction of ErrorData object directly
* via API.
@@ -87,7 +87,7 @@ public void errorDataConstructorTest() throws Exception {
/*
* @testName: errorDataGetThrowableTest
*
- * @assertion_ids: JSP:JAVADOC:2
+ * @assertion_ids: PAGES:JAVADOC:2
*
* @test_Strategy: Validate behavior of ErrorData.getThrowable().
*/
@@ -100,7 +100,7 @@ public void errorDataGetThrowableTest() throws Exception {
/*
* @testName: errorDataGetStatusCodeTest
*
- * @assertion_ids: JSP:JAVADOC:3
+ * @assertion_ids: PAGES:JAVADOC:3
*
* @test_Strategy: Validate behavior of ErrorData.getStatusCode().
*/
@@ -113,7 +113,7 @@ public void errorDataGetStatusCodeTest() throws Exception {
/*
* @testName: errorDataGetRequestURITest
*
- * @assertion_ids: JSP:JAVADOC:4
+ * @assertion_ids: PAGES:JAVADOC:4
*
* @test_Strategy: Validate behavior of ErrorData.getRequestURI()
*/
@@ -126,7 +126,7 @@ public void errorDataGetRequestURITest() throws Exception {
/*
* @testName: errorDataGetServletNameTest
*
- * @assertion_ids: JSP:JAVADOC:5
+ * @assertion_ids: PAGES:JAVADOC:5
*
* @test_Strategy: Validate behavior of ErrorData.getServletName().
*/
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/jspapplicationcontext/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/jspapplicationcontext/URLClientIT.java
index 286be18d..d0931064 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/jspapplicationcontext/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/jspapplicationcontext/URLClientIT.java
@@ -25,8 +25,6 @@
import ee.jakarta.tck.pages.common.util.JspTestUtil;
import java.io.IOException;
-import java.io.InputStream;
-
import org.jboss.arquillian.container.test.api.Deployment;
import org.jboss.arquillian.junit5.ArquillianExtension;
import org.jboss.shrinkwrap.api.ShrinkWrap;
@@ -56,7 +54,7 @@ public static WebArchive createDeployment() throws IOException {
WebArchive archive = ShrinkWrap.create(WebArchive.class, "jsp_jspapplicationcontext_web.war");
archive.addClasses(FooELResolver.class, InstallFooListener.class,
- JspTestUtil.class);
+ JspTestUtil.class);
archive.setWebXML(URLClientIT.class.getClassLoader().getResource(packagePath+"/jsp_jspapplicationcontext_web.xml"));
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/AddELResolverTest.jsp")), "AddELResolverTest.jsp");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/IllegalStateExceptionTest.jsp")), "IllegalStateExceptionTest.jsp");
@@ -64,19 +62,19 @@ public static WebArchive createDeployment() throws IOException {
return archive;
}
-
+
/* Run tests */
// ============================================ Tests ======
/*
* @testName: addELResolverTest
- *
- * @assertion_ids: JSP:JAVADOC:410
- *
+ *
+ * @assertion_ids: PAGES:JAVADOC:410
+ *
* @test_Strategy: Validate the behavior of
* JspApplicationContext.addELResolver() Verify that once an ELResolver has
- * been registered with the JSP container it performs as expected.
+ * been registered with the Jakarta Pages container it performs as expected.
*/
@Test
public void addELResolverTest() throws Exception {
@@ -88,9 +86,9 @@ public void addELResolverTest() throws Exception {
/*
* @testName: invokeIllegalStateExceptionTest
- *
- * @assertion_ids: JSP:JAVADOC:410
- *
+ *
+ * @assertion_ids: PAGES:JAVADOC:410
+ *
* @test_Strategy: Validate the behavior of
* JspApplicationContext.addELResolver() throws IllegalStateException Verify
* that once an application has received a request from the clienT, A call to
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/jspengineinfo/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/jspengineinfo/URLClientIT.java
index 5979a130..3f5c1048 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/jspengineinfo/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/jspengineinfo/URLClientIT.java
@@ -70,7 +70,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: jspEngineInfoGetSpecificationVersionTest
*
- * @assertion_ids: JSP:JAVADOC:131
+ * @assertion_ids: PAGES:JAVADOC:131
*
* @test_Strategy: Validate the behavior of
* JspEngineInfo.getSpecificationVersion().
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/jspexception/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/jspexception/URLClientIT.java
index 1cca8cb5..3c407e2f 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/jspexception/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/jspexception/URLClientIT.java
@@ -63,7 +63,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: jspExceptionDefaultCtorTest
*
- * @assertion_ids: JSP:JAVADOC:125
+ * @assertion_ids: PAGES:JAVADOC:125
*
* @test_Strategy: Validate default constructor of JspException
*/
@@ -76,7 +76,7 @@ public void jspExceptionDefaultCtorTest() throws Exception {
/*
* @testName: jspExceptionMessageCtorTest
*
- * @assertion_ids: JSP:JAVADOC:126
+ * @assertion_ids: PAGES:JAVADOC:126
*
* @test_Strategy: Validate contructor taking single string argument as the
* message of the Exception.
@@ -90,7 +90,7 @@ public void jspExceptionMessageCtorTest() throws Exception {
/*
* @testName: jspExceptionCauseCtorTest
*
- * @assertion_ids: JSP:JAVADOC:128
+ * @assertion_ids: PAGES:JAVADOC:128
*
* @test_Strategy: Validate constructor taking a Throwable signifying the root
* cause of the this JspException.
@@ -104,7 +104,7 @@ public void jspExceptionCauseCtorTest() throws Exception {
/*
* @testName: jspExceptionCauseMessageCtorTest
*
- * @assertion_ids: JSP:JAVADOC:127
+ * @assertion_ids: PAGES:JAVADOC:127
*
* @test_Strategy: Validate constructor taking both a message and a Throwable
* signifying the root cause of the JspException.
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/jspfactory/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/jspfactory/URLClientIT.java
index 0002780f..38be1f3b 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/jspfactory/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/jspfactory/URLClientIT.java
@@ -73,7 +73,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: jspFactoryGetDefaultFactoryTest
*
- * @assertion_ids: JSP:JAVADOC:121
+ * @assertion_ids: PAGES:JAVADOC:121
*
* @test_Strategy: Validate the behavior of JspFactory.getDefaultFactory().
*/
@@ -86,7 +86,7 @@ public void jspFactoryGetDefaultFactoryTest() throws Exception {
/*
* @testName: jspFactoryGetPageContextTest
*
- * @assertion_ids: JSP:JAVADOC:122
+ * @assertion_ids: PAGES:JAVADOC:122
*
* @test_Strategy: Validate the behavior of JspFactory.getPageContext().
*/
@@ -99,7 +99,7 @@ public void jspFactoryGetPageContextTest() throws Exception {
/*
* @testName: jspFactoryGetEngineInfoTest
*
- * @assertion_ids: JSP:JAVADOC:124
+ * @assertion_ids: PAGES:JAVADOC:124
*
* @test_Strategy: Validate the behavior of JspFactory.getEngineInfo().
*/
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/jsptagexception/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/jsptagexception/URLClientIT.java
index b4cbf240..cecb5794 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/jsptagexception/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/jsptagexception/URLClientIT.java
@@ -70,7 +70,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: jspTagExceptionDefaultCtorTest
*
- * @assertion_ids: JSP:JAVADOC:116
+ * @assertion_ids: PAGES:JAVADOC:116
*
* @test_Strategy: Validate default constructor of JspTagException
*/
@@ -83,7 +83,7 @@ public void jspTagExceptionDefaultCtorTest() throws Exception {
/*
* @testName: jspTagExceptionMessageCtorTest
*
- * @assertion_ids: JSP:JAVADOC:115
+ * @assertion_ids: PAGES:JAVADOC:115
*
* @test_Strategy: Validate contructor taking single string argument as the
* message of the Exception.
@@ -97,7 +97,7 @@ public void jspTagExceptionMessageCtorTest() throws Exception {
/*
* @testName: jspTagExceptionCauseCtorTest
*
- * @assertion_ids: JSP:JAVADOC:118
+ * @assertion_ids: PAGES:JAVADOC:118
*
* @test_Strategy: Validate constructor taking a Throwable signifying the root
* cause of the this JspTagException.
@@ -111,7 +111,7 @@ public void jspTagExceptionCauseCtorTest() throws Exception {
/*
* @testName: jspTagExceptionCauseMessageCtorTest
*
- * @assertion_ids: JSP:JAVADOC:117
+ * @assertion_ids: PAGES:JAVADOC:117
*
* @test_Strategy: Validate constructor taking both a message and a Throwable
* signifying the root cause of the JspTagException.
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/jspwriter/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/jspwriter/URLClientIT.java
index 5bcce506..f74ee24e 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/jspwriter/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/jspwriter/URLClientIT.java
@@ -80,7 +80,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: jspWriterNewLineTest
*
- * @assertion_ids: JSP:JAVADOC:63
+ * @assertion_ids: PAGES:JAVADOC:63
*
* @test_Strategy: Validate the behavior of JspWriter.newLine().
*/
@@ -95,7 +95,7 @@ public void jspWriterNewLineTest() throws Exception {
/*
* @testName: jspWriterPrintBooleanTest
*
- * @assertion_ids: JSP:JAVADOC:65
+ * @assertion_ids: PAGES:JAVADOC:65
*
* @test_Strategy: Validate the behavior of JspWriter.print(boolean).
*/
@@ -109,7 +109,7 @@ public void jspWriterPrintBooleanTest() throws Exception {
/*
* @testName: jspWriterPrintCharTest
*
- * @assertion_ids: JSP:JAVADOC:67
+ * @assertion_ids: PAGES:JAVADOC:67
*
* @test_Strategy: Validate the behavior of JspWriter.print(char).
*/
@@ -123,7 +123,7 @@ public void jspWriterPrintCharTest() throws Exception {
/*
* @testName: jspWriterPrintIntTest
*
- * @assertion_ids: JSP:JAVADOC:69
+ * @assertion_ids: PAGES:JAVADOC:69
*
* @test_Strategy: Validate the behavior of JspWriter.print(int).
*/
@@ -139,7 +139,7 @@ public void jspWriterPrintIntTest() throws Exception {
/*
* @testName: jspWriterPrintLongTest
*
- * @assertion_ids: JSP:JAVADOC:71
+ * @assertion_ids: PAGES:JAVADOC:71
*
* @test_Strategy: Validate the behavior of JspWriter.print(long).
*/
@@ -155,7 +155,7 @@ public void jspWriterPrintLongTest() throws Exception {
/*
* @testName: jspWriterPrintFloatTest
*
- * @assertion_ids: JSP:JAVADOC:73
+ * @assertion_ids: PAGES:JAVADOC:73
*
* @test_Strategy: Validate the behavior of JspWriter.print(Float).
*/
@@ -171,7 +171,7 @@ public void jspWriterPrintFloatTest() throws Exception {
/*
* @testName: jspWriterPrintDoubleTest
*
- * @assertion_ids: JSP:JAVADOC:75
+ * @assertion_ids: PAGES:JAVADOC:75
*
* @test_Strategy: Validate the behavior of JspWriter.print(double).
*/
@@ -187,7 +187,7 @@ public void jspWriterPrintDoubleTest() throws Exception {
/*
* @testName: jspWriterPrintCharArrayTest
*
- * @assertion_ids: JSP:JAVADOC:77
+ * @assertion_ids: PAGES:JAVADOC:77
*
* @test_Strategy: Validate the behavior of JspWriter.print(char[]).
*/
@@ -202,7 +202,7 @@ public void jspWriterPrintCharArrayTest() throws Exception {
/*
* @testName: jspWriterPrintStringTest
*
- * @assertion_ids: JSP:JAVADOC:80
+ * @assertion_ids: PAGES:JAVADOC:80
*
* @test_Strategy: Validate the behavior of JspWriter.print(String).
*/
@@ -216,7 +216,7 @@ public void jspWriterPrintStringTest() throws Exception {
/*
* @testName: jspWriterPrintNullStringTest
*
- * @assertion_ids: JSP:JAVADOC:80
+ * @assertion_ids: PAGES:JAVADOC:80
*
* @test_Strategy: Validate the behavior of JspWriter.print(String) where the
* argument is null.
@@ -231,7 +231,7 @@ public void jspWriterPrintNullStringTest() throws Exception {
/*
* @testName: jspWriterPrintObjectTest
*
- * @assertion_ids: JSP:JAVADOC:82
+ * @assertion_ids: PAGES:JAVADOC:82
*
* @test_Strategy: Validate the behavior of JspWriter.print(Object).
*/
@@ -245,7 +245,7 @@ public void jspWriterPrintObjectTest() throws Exception {
/*
* @testName: jspWriterPrintlnTest
*
- * @assertion_ids: JSP:JAVADOC:84
+ * @assertion_ids: PAGES:JAVADOC:84
*
* @test_Strategy: Validate the behavior of JspWriter.println().
*/
@@ -260,7 +260,7 @@ public void jspWriterPrintlnTest() throws Exception {
/*
* @testName: jspWriterPrintlnBooleanTest
*
- * @assertion_ids: JSP:JAVADOC:86
+ * @assertion_ids: PAGES:JAVADOC:86
*
* @test_Strategy: Validate the behavior of JspWriter.println(boolean).
*/
@@ -275,7 +275,7 @@ public void jspWriterPrintlnBooleanTest() throws Exception {
/*
* @testName: jspWriterPrintlnCharTest
*
- * @assertion_ids: JSP:JAVADOC:88
+ * @assertion_ids: PAGES:JAVADOC:88
*
* @test_Strategy: Validate the behavior of JspWriter.println(char).
*/
@@ -290,7 +290,7 @@ public void jspWriterPrintlnCharTest() throws Exception {
/*
* @testName: jspWriterPrintlnIntTest
*
- * @assertion_ids: JSP:JAVADOC:90
+ * @assertion_ids: PAGES:JAVADOC:90
*
* @test_Strategy: Validate the behavior of JspWriter.println(int).
*/
@@ -307,7 +307,7 @@ public void jspWriterPrintlnIntTest() throws Exception {
/*
* @testName: jspWriterPrintlnLongTest
*
- * @assertion_ids: JSP:JAVADOC:92
+ * @assertion_ids: PAGES:JAVADOC:92
*
* @test_Strategy: Validate the behavior of JspWriter.println(long).
*/
@@ -324,7 +324,7 @@ public void jspWriterPrintlnLongTest() throws Exception {
/*
* @testName: jspWriterPrintlnFloatTest
*
- * @assertion_ids: JSP:JAVADOC:94
+ * @assertion_ids: PAGES:JAVADOC:94
*
* @test_Strategy: Validate the behavior of JspWriter.println(float).
*/
@@ -341,7 +341,7 @@ public void jspWriterPrintlnFloatTest() throws Exception {
/*
* @testName: jspWriterPrintlnDoubleTest
*
- * @assertion_ids: JSP:JAVADOC:96
+ * @assertion_ids: PAGES:JAVADOC:96
*
* @test_Strategy: Validate the behavior of JspWriter.println(double).
*/
@@ -358,7 +358,7 @@ public void jspWriterPrintlnDoubleTest() throws Exception {
/*
* @testName: jspWriterPrintlnCharArrayTest
*
- * @assertion_ids: JSP:JAVADOC:98
+ * @assertion_ids: PAGES:JAVADOC:98
*
* @test_Strategy: Validate the behavior of JspWriter.println(double).
*/
@@ -375,7 +375,7 @@ public void jspWriterPrintlnCharArrayTest() throws Exception {
/*
* @testName: jspWriterPrintlnStringTest
*
- * @assertion_ids: JSP:JAVADOC:100
+ * @assertion_ids: PAGES:JAVADOC:100
*
* @test_Strategy: Validate the behavior of JspWriter.println(String).
*/
@@ -392,7 +392,7 @@ public void jspWriterPrintlnStringTest() throws Exception {
/*
* @testName: jspWriterPrintlnNullStringTest
*
- * @assertion_ids: JSP:JAVADOC:100
+ * @assertion_ids: PAGES:JAVADOC:100
*
* @test_Strategy: Validate the behavior of JspWriter.println(String) where
* the argument is null.
@@ -407,7 +407,7 @@ public void jspWriterPrintlnNullStringTest() throws Exception {
/*
* @testName: jspWriterPrintlnObjectTest
*
- * @assertion_ids: JSP:JAVADOC:102
+ * @assertion_ids: PAGES:JAVADOC:102
*
* @test_Strategy: Validate the behavior of JspWriter.println(Object).
*/
@@ -424,7 +424,7 @@ public void jspWriterPrintlnObjectTest() throws Exception {
/*
* @testName: jspWriterClearTest
*
- * @assertion_ids: JSP:JAVADOC:104
+ * @assertion_ids: PAGES:JAVADOC:104
*
* @test_Strategy: Validate the behavior of JspWriter.clear().
*/
@@ -437,7 +437,7 @@ public void jspWriterClearTest() throws Exception {
/*
* @testName: jspWriterClearIOExceptionTest
*
- * @assertion_ids: JSP:JAVADOC:105
+ * @assertion_ids: PAGES:JAVADOC:105
*
* @test_Strategy: Validate the behavior of JspWriter.clear(). An IOException
* must be thrown if the response has been committed, and JspWriter.clear() is
@@ -452,7 +452,7 @@ public void jspWriterClearIOExceptionTest() throws Exception {
/*
* @testName: jspWriterClearBufferTest
*
- * @assertion_ids: JSP:JAVADOC:106
+ * @assertion_ids: PAGES:JAVADOC:106
*
* @test_Strategy: Validate the behavior of JspWriter.clearBuffer().
*/
@@ -465,7 +465,7 @@ public void jspWriterClearBufferTest() throws Exception {
/*
* @testName: jspWriterFlushTest
*
- * @assertion_ids: JSP:JAVADOC:108
+ * @assertion_ids: PAGES:JAVADOC:108
*
* @test_Strategy: Validate the behavior of JspWriter.flush().
*/
@@ -478,7 +478,7 @@ public void jspWriterFlushTest() throws Exception {
/*
* @testName: jspWriterCloseTest
*
- * @assertion_ids: JSP:JAVADOC:110;JSP:JAVADOC:109
+ * @assertion_ids: PAGES:JAVADOC:110;PAGES:JAVADOC:109
*
* @test_Strategy: Validate the behavior of JspWriter.close().
*/
@@ -498,7 +498,7 @@ public void jspWriterCloseTest() throws Exception {
/*
* @testName: jspWriterGetBufferSizeTest
*
- * @assertion_ids: JSP:JAVADOC:112
+ * @assertion_ids: PAGES:JAVADOC:112
*
* @test_Strategy: Validate the behavior of JspWriter.getBufferSize().
*/
@@ -511,7 +511,7 @@ public void jspWriterGetBufferSizeTest() throws Exception {
/*
* @testName: jspWriterGetRemainingTest
*
- * @assertion_ids: JSP:JAVADOC:113
+ * @assertion_ids: PAGES:JAVADOC:113
*
* @test_Strategy: Validate the behavior of JspWriter.getRemaining().
*/
@@ -524,7 +524,7 @@ public void jspWriterGetRemainingTest() throws Exception {
/*
* @testName: jspWriterIsAutoFlushTest
*
- * @assertion_ids: JSP:JAVADOC:114
+ * @assertion_ids: PAGES:JAVADOC:114
*
* @test_Strategy: Validate the behavior of JspWriter.isAutoFlush().
*/
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/pagecontext/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/pagecontext/URLClientIT.java
index 13e2f95a..edf0c430 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/pagecontext/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/pagecontext/URLClientIT.java
@@ -65,7 +65,7 @@ public static WebArchive createDeployment() throws IOException {
/**
* @testName: pageContextGetSessionTest
- * @assertion_ids: JSP:JAVADOC:16
+ * @assertion_ids: PAGES:JAVADOC:16
* @test_Strategy: Validate PageContext.getSession().
*/
@Test
@@ -77,7 +77,7 @@ public void pageContextGetSessionTest() throws Exception {
/**
* @testName: pageContextGetPageTest
- * @assertion_ids: JSP:JAVADOC:17
+ * @assertion_ids: PAGES:JAVADOC:17
* @test_Strategy: Validate PageContext.getPage().
*/
@Test
@@ -89,7 +89,7 @@ public void pageContextGetPageTest() throws Exception {
/**
* @testName: pageContextGetRequestTest
- * @assertion_ids: JSP:JAVADOC:18
+ * @assertion_ids: PAGES:JAVADOC:18
* @test_Strategy: Validate PageContext.getRequest().
*/
@Test
@@ -101,7 +101,7 @@ public void pageContextGetRequestTest() throws Exception {
/**
* @testName: pageContextGetResponseTest
- * @assertion_ids: JSP:JAVADOC:19
+ * @assertion_ids: PAGES:JAVADOC:19
* @test_Strategy: Validate PageContext.getResponse().
*/
@Test
@@ -113,7 +113,7 @@ public void pageContextGetResponseTest() throws Exception {
/**
* @testName: pageContextGetExceptionTest
- * @assertion_ids: JSP:JAVADOC:20
+ * @assertion_ids: PAGES:JAVADOC:20
* @test_Strategy: Validate PageContext.getException().
*/
@Test
@@ -129,7 +129,7 @@ public void pageContextGetExceptionTest() throws Exception {
/**
* @testName: pageContextGetServletConfigTest
- * @assertion_ids: JSP:JAVADOC:21
+ * @assertion_ids: PAGES:JAVADOC:21
* @test_Strategy: Validate PageContext.getServletConfig().
*/
@Test
@@ -141,7 +141,7 @@ public void pageContextGetServletConfigTest() throws Exception {
/**
* @testName: pageContextGetServletContextTest
- * @assertion_ids: JSP:JAVADOC:22
+ * @assertion_ids: PAGES:JAVADOC:22
* @test_Strategy: Validate PageContext.getServletContext().
*/
@Test
@@ -153,7 +153,7 @@ public void pageContextGetServletContextTest() throws Exception {
/**
* @testName: pageContextForwardContextPathTest
- * @assertion_ids: JSP:JAVADOC:23
+ * @assertion_ids: PAGES:JAVADOC:23
* @test_Strategy: Validate PageContext.forward() passing in a resource
* identified by a context-relative path.
*/
@@ -166,7 +166,7 @@ public void pageContextForwardContextPathTest() throws Exception {
/**
* @testName: pageContextForwardPagePathTest
- * @assertion_ids: JSP:JAVADOC:24
+ * @assertion_ids: PAGES:JAVADOC:24
* @test_Strategy: Validate PageContext.forward() passing in a resource
* identified by a page-relative path.
*/
@@ -181,7 +181,7 @@ public void pageContextForwardPagePathTest() throws Exception {
* -- Removed due to the way we capture the exception. -- testName:
* pageContextForwardServletExceptionTest
*
- * @assertion_ids: JSP:JAVADOC:26
+ * @assertion_ids: PAGES:JAVADOC:26
* @test_Strategy: Validate PageContext.forward() throws a ServletException if
* a ServletException occurs during the forward process.
*
@@ -196,7 +196,7 @@ public void pageContextForwardPagePathTest() throws Exception {
* -- Removed due to the way we capture the exception. -- testName:
* pageContextForwardIOExceptionTest
*
- * @assertion_ids: JSP:JAVADOC:27
+ * @assertion_ids: PAGES:JAVADOC:27
* @test_Strategy: Validate PageContext.forward() throws an IOExcpetion if an
* IOException occurs during the forward process.
*
@@ -209,7 +209,7 @@ public void pageContextForwardPagePathTest() throws Exception {
/**
* @testName: pageContextForwardIllegalStateExceptionTest
- * @assertion_ids: JSP:JAVADOC:29
+ * @assertion_ids: PAGES:JAVADOC:29
* @test_Strategy: Valdiate PageContext.forward() throws an
* IllegalStateException if ServletResponse is not in the
* proper state to perform a forward.
@@ -225,7 +225,7 @@ public void pageContextForwardIllegalStateExceptionTest() throws Exception {
/**
* @testName: pageContextIncludeContextPathTest
- * @assertion_ids: JSP:JAVADOC:31
+ * @assertion_ids: PAGES:JAVADOC:31
* @test_Strategy: Validate PageContext.include() where the inclusion resource
* is identified by a context-relative path.
*/
@@ -238,7 +238,7 @@ public void pageContextIncludeContextPathTest() throws Exception {
/**
* @testName: pageContextIncludePagePathTest
- * @assertion_ids: JSP:JAVADOC:32
+ * @assertion_ids: PAGES:JAVADOC:32
* @test_Strategy: Validate PageContext.include() where the inclusion resource
* is identified by a page-relative path.
*/
@@ -251,7 +251,7 @@ public void pageContextIncludePagePathTest() throws Exception {
/**
* @testName: pageContextIncludeFlushTrueTest
- * @assertion_ids: JSP:JAVADOC:40;JSP:JAVADOC:39
+ * @assertion_ids: PAGES:JAVADOC:40;PAGES:JAVADOC:39
* @test_Strategy: Validate PageContext.include() with flush argument provided
* and set to true. Response should be commited after the
* flush. Test validates this by perfoming an action against
@@ -269,7 +269,7 @@ public void pageContextIncludeFlushTrueTest() throws Exception {
/**
* @testName: pageContextIncludeFlushFalseTest
- * @assertion_ids: JSP:JAVADOC:385;JSP:JAVADOC:38
+ * @assertion_ids: PAGES:JAVADOC:385;PAGES:JAVADOC:38
* @test_Strategy: Validate PageContext.include() with flush argument provided
* and set to false. Response should not have been flushed.
* Verify by preforming an action against the response that
@@ -288,7 +288,7 @@ public void pageContextIncludeFlushFalseTest() throws Exception {
/**
* @testName: pageContextHandlePageExceptionExcTest
- * @assertion_ids: JSP:JAVADOC:46
+ * @assertion_ids: PAGES:JAVADOC:46
* @test_Strategy: Validate PageContext.handlePageException(Exception) invokes
* the defined error page.
*/
@@ -302,7 +302,7 @@ public void pageContextHandlePageExceptionExcTest() throws Exception {
/**
* @testName: pageContextHandlePageExceptionThrTest
- * @assertion_ids: JSP:JAVADOC:53
+ * @assertion_ids: PAGES:JAVADOC:53
* @test_Strategy: Validate PageContext.handlePageException(Throwable) invokes
* the defined error page.
*/
@@ -316,7 +316,7 @@ public void pageContextHandlePageExceptionThrTest() throws Exception {
/**
* @testName: pageContextHandlePageExceptionExcNPETest
- * @assertion_ids: JSP:JAVADOC:51
+ * @assertion_ids: PAGES:JAVADOC:51
* @test_Strategy: Validate PageContext.handlePageException(Exception) throws
* a NullPointerException if an null argument is provided.
*/
@@ -329,7 +329,7 @@ public void pageContextHandlePageExceptionExcNPETest() throws Exception {
/**
* @testName: pageContextHandlePageExceptionThrNPETest
- * @assertion_ids: JSP:JAVADOC:58
+ * @assertion_ids: PAGES:JAVADOC:58
* @test_Strategy: Validate PageContext.handlePageException(Throwable) throws
* a NullPointerException if an null argument is provided.
*/
@@ -342,7 +342,7 @@ public void pageContextHandlePageExceptionThrNPETest() throws Exception {
/**
* @testName: pageContextPushPopBodyTest
- * @assertion_ids: JSP:JAVADOC:60;JSP:JAVADOC:61;JSP:JAVADOC:380;JSP:JAVADOC:
+ * @assertion_ids: PAGES:JAVADOC:60;PAGES:JAVADOC:61;PAGES:JAVADOC:380;PAGES:JAVADOC:
* 381
* @test_Strategy: Validate behavior of PageContext.pushBody() and
* PageContext.popBody().
@@ -356,7 +356,7 @@ public void pageContextPushPopBodyTest() throws Exception {
/**
* @testName: pageContextGetErrorDataTest
- * @assertion_ids: JSP:JAVADOC:62
+ * @assertion_ids: PAGES:JAVADOC:62
* @test_Strategy: Validate behavior of PageContext.getErrorData().
*/
@Test
@@ -369,7 +369,7 @@ public void pageContextGetErrorDataTest() throws Exception {
/**
* @testName: pageContextIncludeIOExceptionTest
- * @assertion_ids: JSP:JAVADOC:35
+ * @assertion_ids: PAGES:JAVADOC:35
* @test_Strategy: Validate PageContext.include() throws an IOException if
* included resource throws an IOException.
*/
@@ -382,7 +382,7 @@ public void pageContextIncludeIOExceptionTest() throws Exception {
/**
* @testName: pageContextIncludeServletExceptionTest
- * @assertion_ids: JSP:JAVADOC:34
+ * @assertion_ids: PAGES:JAVADOC:34
* @test_Strategy: Validate PageContext.include() throws a ServletException if
* target resource throws a ServletException.
*/
@@ -395,7 +395,7 @@ public void pageContextIncludeServletExceptionTest() throws Exception {
/**
* @testName: pageContextIncludeFlushIOExceptionTest
- * @assertion_ids: JSP:JAVADOC:43
+ * @assertion_ids: PAGES:JAVADOC:43
* @test_Strategy: Validate PageContext.include() with flush argument
* provided, throws an IOException if the target resource
* cannot be accessed by the caller.
@@ -409,7 +409,7 @@ public void pageContextIncludeFlushIOExceptionTest() throws Exception {
/**
* @testName: pageContextIncludeFlushServletExceptionTest
- * @assertion_ids: JSP:JAVADOC:42
+ * @assertion_ids: PAGES:JAVADOC:42
* @test_Strategy: Validate PageContext.include() with flush argument
* provided, throws a ServletException if the target resource
* cannot be accessed by the caller.
@@ -424,7 +424,7 @@ public void pageContextIncludeFlushServletExceptionTest() throws Exception {
/**
* @testName: pageContextGetSetAttributeTest
- * @assertion_ids: JSP:JAVADOC:133;JSP:JAVADOC:138
+ * @assertion_ids: PAGES:JAVADOC:133;PAGES:JAVADOC:138
* @test_Strategy: Validate PageContext.getAttribute(String),
* PageContext.setAttribute(String). Note: These are inherited
* from JspContext.
@@ -438,7 +438,7 @@ public void pageContextGetSetAttributeTest() throws Exception {
/**
* @testName: pageContextSetAttributeNPETest
- * @assertion_ids: JSP:JAVADOC:134;JSP:JAVADOC:396
+ * @assertion_ids: PAGES:JAVADOC:134;PAGES:JAVADOC:396
* @test_Strategy: Validate a NullPointerException is thrown if the attribute
* name provided is null, but not when the provided value is
* null. Note: This is inherited from JspContext.
@@ -452,7 +452,7 @@ public void pageContextSetAttributeNPETest() throws Exception {
/**
* @testName: pageContextGetSetAttributeInScopeTest
- * @assertion_ids: JSP:JAVADOC:135;JSP:JAVADOC:141
+ * @assertion_ids: PAGES:JAVADOC:135;PAGES:JAVADOC:141
* @test_Strategy: Validate PageContext.getAttribute() and
* PageContext.setAttribute() when provided with scope
* arguments. Note: These are inherited from JspContext.
@@ -466,7 +466,7 @@ public void pageContextGetSetAttributeInScopeTest() throws Exception {
/**
* @testName: pageContextSetAttributeInScopeNPETest
- * @assertion_ids: JSP:JAVADOC:136;JSP:JAVADOC:397
+ * @assertion_ids: PAGES:JAVADOC:136;PAGES:JAVADOC:397
* @test_Strategy: Validate a NullPointerException is thrown if the attribute
* name provided is null, but not when the provided value is
* null. Note: This is inherited from JspContext.
@@ -480,7 +480,7 @@ public void pageContextSetAttributeInScopeNPETest() throws Exception {
/**
* @testName: pageContextSetAttributeInScopeIllegalArgumentExceptionTest
- * @assertion_ids: JSP:JAVADOC:137;JSP:JAVADOC:398
+ * @assertion_ids: PAGES:JAVADOC:137;PAGES:JAVADOC:398
* @test_Strategy: Validate an IllegalArgumentException is thrown if
* PageContext.setAttribute() is provided an invalid scope.
* Note: This is inherited from JspContext.
@@ -496,7 +496,7 @@ public void pageContextSetAttributeInScopeIllegalArgumentExceptionTest()
/**
* @testName: pageContextGetAttributeNPETest
- * @assertion_ids: JSP:JAVADOC:139;JSP:JAVADOC:142
+ * @assertion_ids: PAGES:JAVADOC:139;PAGES:JAVADOC:142
* @test_Strategy: Validate a NullPointerException is thrown if
* PageContext.getAttriubte() is provided a null argument.
* Note: This is inherited from JspContext.
@@ -510,7 +510,7 @@ public void pageContextGetAttributeNPETest() throws Exception {
/**
* @testName: pageContextGetAttributeInScopeIllegalArgumentExceptionTest
- * @assertion_ids: JSP:JAVADOC:143
+ * @assertion_ids: PAGES:JAVADOC:143
* @test_Strategy: Validate an IllegalArgumentException is thrown if
* PageContext.getAttribute() is provided an invalid value for
* scope. Note: This is inherited from JspContext.
@@ -526,7 +526,7 @@ public void pageContextGetAttributeInScopeIllegalArgumentExceptionTest()
/**
* @testName: pageContextFindAttributeTest
- * @assertion_ids: JSP:JAVADOC:144
+ * @assertion_ids: PAGES:JAVADOC:144
* @test_Strategy: Validate behavior of PageContext.findAttribute(). Note:
* This is inherited from JspContext.
*/
@@ -539,7 +539,7 @@ public void pageContextFindAttributeTest() throws Exception {
/**
* @testName: pageContextRemoveAttributeTest
- * @assertion_ids: JSP:JAVADOC:145
+ * @assertion_ids: PAGES:JAVADOC:145
* @test_Strategy: Validate the behavior of PageContext.removeAttribute().
* Note: This is inhertied from JspContext
*/
@@ -552,7 +552,7 @@ public void pageContextRemoveAttributeTest() throws Exception {
/**
* @testName: pageContextRemoveAttributeFromScopeTest
- * @assertion_ids: JSP:JAVADOC:146
+ * @assertion_ids: PAGES:JAVADOC:146
* @test_Strategy: Validate the behavior of PageContext.remoteAttribute() when
* provided a scope. Note: This is inherited from JspContext.
*/
@@ -565,7 +565,7 @@ public void pageContextRemoveAttributeFromScopeTest() throws Exception {
/**
* @testName: pageContextRemoveAttributeFromScopeIllegalScopeTest
- * @assertion_ids: JSP:JAVADOC:392
+ * @assertion_ids: PAGES:JAVADOC:392
* @test_Strategy: Validate an IllegalArgumentException is thrown if the scope
* argument is provided an illegal scope.
*/
@@ -580,7 +580,7 @@ public void pageContextRemoveAttributeFromScopeIllegalScopeTest()
/**
* @testName: pageContextGetAttributeScopeTest
- * @assertion_ids: JSP:JAVADOC:147
+ * @assertion_ids: PAGES:JAVADOC:147
* @test_Strategy: Validate the behavior of PageContext.getAttributeScope().
* Note: This is inherited from JspContext.
*/
@@ -593,7 +593,7 @@ public void pageContextGetAttributeScopeTest() throws Exception {
/**
* @testName: pageContextGetAttributeNamesInScopeTest
- * @assertion_ids: JSP:JAVADOC:148
+ * @assertion_ids: PAGES:JAVADOC:148
* @test_Strategy: Validate the behavior of
* PageContext.getAttributeNamesInScope(). Note: This is
* inherited from JspContext
@@ -607,7 +607,7 @@ public void pageContextGetAttributeNamesInScopeTest() throws Exception {
/**
* @testName: pageContextGetAttributeNamesInScopeIllegalScopeTest
- * @assertion_ids: JSP:JAVADOC:401
+ * @assertion_ids: PAGES:JAVADOC:401
* @test_Strategy: Validate an IllegalArgumentException is thrown if the scope
* argument is provided an illegal scope.
*/
@@ -622,7 +622,7 @@ public void pageContextGetAttributeNamesInScopeIllegalScopeTest()
/**
* @testName: pageContextGetOutTest
- * @assertion_ids: JSP:JAVADOC:149
+ * @assertion_ids: PAGES:JAVADOC:149
* @test_Strategy: Validate the behavior of PageContext.getOut. Note: This is
* inherited from JspContext.
*/
@@ -635,7 +635,7 @@ public void pageContextGetOutTest() throws Exception {
/**
* @testName: pageContextFindAttributeNullNameTest
- * @assertion_ids: JSP:JAVADOC:387
+ * @assertion_ids: PAGES:JAVADOC:387
* @test_Strategy: Validate a NullPointerException is thrown if a null value
* is provided for the name parameter.
*/
@@ -648,7 +648,7 @@ public void pageContextFindAttributeNullNameTest() throws Exception {
/**
* @testName: pageContextGetAttributesScopeNullNameTest
- * @assertion_ids: JSP:JAVADOC:389
+ * @assertion_ids: PAGES:JAVADOC:389
* @test_Strategy: Validate a NullPointerException is thrown if a null value
* is provided to the name argument.
*/
@@ -662,7 +662,7 @@ public void pageContextGetAttributesScopeNullNameTest() throws Exception {
/**
* @testName: pageContextRemoveAttributeNullNameTest
- * @assertion_ids: JSP:JAVADOC:393;JSP:JAVADOC:391
+ * @assertion_ids: PAGES:JAVADOC:393;PAGES:JAVADOC:391
* @test_Strategy: Validate a NullPointerException is thrown if the name
* argument is provided a null value.
*/
@@ -675,7 +675,7 @@ public void pageContextRemoveAttributeNullNameTest() throws Exception {
/**
* @testName: pageContextSetAttributeNullValueTest
- * @assertion_ids: JSP:JAVADOC:396;JSP:JAVADOC:397
+ * @assertion_ids: PAGES:JAVADOC:396;PAGES:JAVADOC:397
* @test_Strategy: Validate that if a null value is provided to either
* setAttribute(String, Object) or setAttribute(String,
* Object, int) it has the same affect as calling
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/skippageexception/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/skippageexception/URLClientIT.java
index 50cb463c..9ae8a3b5 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/skippageexception/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/skippageexception/URLClientIT.java
@@ -70,7 +70,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: skipPageExceptionDefaultCtorTest
*
- * @assertion_ids: JSP:JAVADOC:6
+ * @assertion_ids: PAGES:JAVADOC:6
*
* @test_Strategy: Validate default constructor of SkipPageException
*/
@@ -83,7 +83,7 @@ public void skipPageExceptionDefaultCtorTest() throws Exception {
/*
* @testName: skipPageExceptionMessageCtorTest
*
- * @assertion_ids: JSP:JAVADOC:7
+ * @assertion_ids: PAGES:JAVADOC:7
*
* @test_Strategy: Validate contructor taking single string argument as the
* message of the Exception.
@@ -97,7 +97,7 @@ public void skipPageExceptionMessageCtorTest() throws Exception {
/*
* @testName: skipPageExceptionCauseCtorTest
*
- * @assertion_ids: JSP:JAVADOC:8
+ * @assertion_ids: PAGES:JAVADOC:8
*
* @test_Strategy: Validate constructor taking a Throwable signifying the root
* cause of the this SkipPageException.
@@ -111,7 +111,7 @@ public void skipPageExceptionCauseCtorTest() throws Exception {
/*
* @testName: skipPageExceptionCauseMessageCtorTest
*
- * @assertion_ids: JSP:JAVADOC:9
+ * @assertion_ids: PAGES:JAVADOC:9
*
* @test_Strategy: Validate constructor taking both a message and a Throwable
* signifying the root cause of the SkipPageException.
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/bodycontent/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/bodycontent/URLClientIT.java
index 92fe10c8..a7d1cba5 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/bodycontent/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/bodycontent/URLClientIT.java
@@ -77,7 +77,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: bodyContentFlushTest
*
- * @assertion_ids: JSP:JAVADOC:332
+ * @assertion_ids: PAGES:JAVADOC:332
*
* @test_Strategy: Validates that an IOException is thrown when
* BodyContent.flush() is called.
@@ -93,7 +93,7 @@ public void bodyContentFlushTest() throws Exception {
/*
* @testName: bodyContentClearBodyTest
*
- * @assertion_ids: JSP:JAVADOC:333
+ * @assertion_ids: PAGES:JAVADOC:333
*
* @test_Strategy: Validate that clearBuffer() works as expected.
*/
@@ -108,7 +108,7 @@ public void bodyContentClearBodyTest() throws Exception {
/*
* @testName: bodyContentReadWriteTest
*
- * @assertion_ids: JSP:JAVADOC:334;JSP:JAVADOC:338
+ * @assertion_ids: PAGES:JAVADOC:334;PAGES:JAVADOC:338
*
* @test_Strategy: Validate that a reader can be obtained containing the
* bodycontent of the tag. Using the content that is read in, obtain a writer
@@ -125,7 +125,7 @@ public void bodyContentReadWriteTest() throws Exception {
/*
* @testName: bodyContentWriteOutTest
*
- * @assertion_ids: JSP:JAVADOC:336
+ * @assertion_ids: PAGES:JAVADOC:336
*
* @test_Strategy: Validate the behavior of BodyContent.writeOut().
*/
@@ -140,7 +140,7 @@ public void bodyContentWriteOutTest() throws Exception {
/*
* @testName: bodyContentGetStringTest
*
- * @assertion_ids: JSP:JAVADOC:335
+ * @assertion_ids: PAGES:JAVADOC:335
*
* @test_Strategy: Validate the behavior of BodyContent.getString().
*/
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/bodytagsupport/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/bodytagsupport/URLClientIT.java
index 76c23d09..afef54ea 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/bodytagsupport/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/bodytagsupport/URLClientIT.java
@@ -88,7 +88,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: bodyTagSupportCtorTest
*
- * @assertion_ids: JSP:JAVADOC:318
+ * @assertion_ids: PAGES:JAVADOC:318
*
* @test_Strategy: Validate the constructor of BodyTagSupport
*/
@@ -101,7 +101,7 @@ public void bodyTagSupportCtorTest() throws Exception {
/*
* @testName: bodyTagSupportDoStartTagTest
*
- * @assertion_ids: JSP:JAVADOC:319
+ * @assertion_ids: PAGES:JAVADOC:319
*
* @test_Strategy: Validate the default return value of
* BodyTagSupport.doStartTag() is EVAL_BODY_BUFFERED.
@@ -115,7 +115,7 @@ public void bodyTagSupportDoStartTagTest() throws Exception {
/*
* @testName: bodyTagSupportDoEndTagTest
*
- * @assertion_ids: JSP:JAVADOC:321
+ * @assertion_ids: PAGES:JAVADOC:321
*
* @test_Strategy: Validate the default return value of
* BodyTagSupport.doEndTag() is EVAL_PAGE.
@@ -129,7 +129,7 @@ public void bodyTagSupportDoEndTagTest() throws Exception {
/*
* @testName: bodyTagSupportDoAfterBodyTest
*
- * @assertion_ids: JSP:JAVADOC:326
+ * @assertion_ids: PAGES:JAVADOC:326
*
* @test_Strategy: Validate the default return value of
* BodyTagSupport.doAfterBody() is SKIP_BODY.
@@ -143,7 +143,7 @@ public void bodyTagSupportDoAfterBodyTest() throws Exception {
/*
* @testName: bodyTagSupportGetBodyContentTest
*
- * @assertion_ids: JSP:JAVADOC:323;JSP:JAVADOC:329
+ * @assertion_ids: PAGES:JAVADOC:323;PAGES:JAVADOC:329
*
* @test_Strategy: Validate the behavior of getBodyContent(). This indirectly
* ensures that the container properly called setBodyContent().
@@ -159,7 +159,7 @@ public void bodyTagSupportGetBodyContentTest() throws Exception {
/*
* @testName: bodyTagSupportGetPreviousOutTest
*
- * @assertion_ids: JSP:JAVADOC:330
+ * @assertion_ids: PAGES:JAVADOC:330
*
* @test_Strategy: Validate the behavior of getPreviousOut.
*/
@@ -176,7 +176,7 @@ public void bodyTagSupportGetPreviousOutTest() throws Exception {
* @testName: bodyTagSupportEvalBodyBufferedTest
*
* @assertion_ids:
- * JSP:JAVADOC:346;JSP:JAVADOC:374;JSP:JAVADOC:375;JSP:JAVADOC:324
+ * PAGES:JAVADOC:346;PAGES:JAVADOC:374;PAGES:JAVADOC:375;PAGES:JAVADOC:324
*
* @test_Strategy: Validate that the container properly calls setInitBody()
* then doInitBody() after doStartTag() is called, prior to evaluating the
@@ -193,7 +193,7 @@ public void bodyTagSupportEvalBodyBufferedTest() throws Exception {
/*
* @testName: bodyTagSupportEvalBodyIncludeTest
*
- * @assertion_ids: JSP:JAVADOC:376
+ * @assertion_ids: PAGES:JAVADOC:376
*
* @test_Strategy: Validate that the container doesn't call setBodyContent()
* and doInitBody() if doStartTag() returns EVAL_BODY_INCLUDE.
@@ -209,7 +209,7 @@ public void bodyTagSupportEvalBodyIncludeTest() throws Exception {
/*
* @testName: bodyTagSupportSkipBodyTest
*
- * @assertion_ids: JSP:JAVADOC:402
+ * @assertion_ids: PAGES:JAVADOC:402
*
* @test_Strategy: Validate that the container doesn't call setInitBody() and
* doInitBody() after doStartTag() returns SKIP_BODY.
@@ -225,7 +225,7 @@ public void bodyTagSupportSkipBodyTest() throws Exception {
/*
* @testName: bodyTagSupportEmptyTagTest
*
- * @assertion_ids: JSP:JAVADOC:376;
+ * @assertion_ids: PAGES:JAVADOC:376;
*
* @test_Strategy: Validate that the container only calls setInitBody() and
* doInitBody() if the tag is empty. 1. Empty Tag1: 2. Empty Tag2:
@@ -243,7 +243,7 @@ public void bodyTagSupportEmptyTagTest() throws Exception {
/*
* @testName: bodyTagSupportVariableSynchronizationTest
*
- * @assertion_ids: JSP:JAVADOC:377
+ * @assertion_ids: PAGES:JAVADOC:377
*
* @test_Strategy: Validate scripting variables are properly synchornized.
*/
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/dynamicattributes/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/dynamicattributes/URLClientIT.java
index 4943a108..8c9cf843 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/dynamicattributes/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/dynamicattributes/URLClientIT.java
@@ -80,7 +80,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: dynamicAttributesTest
*
- * @assertion_ids: JSP:JAVADOC:372
+ * @assertion_ids: PAGES:JAVADOC:372
*
* @test_Strategy: Validate undeclared attributes can be set on a tag handler
* for attributes not specified in the TLD.
@@ -97,7 +97,7 @@ public void dynamicAttributesTest() throws Exception {
/*
* @testName: dynamicAttributesExceptionTest
*
- * @assertion_ids: JSP:JAVADOC:372
+ * @assertion_ids: PAGES:JAVADOC:372
*
* @test_Strategy: Validate that if a JspException is thrown by
* setDynamicAttribute(), that doStartTag() or doTag() is not called on the
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/functioninfo/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/functioninfo/URLClientIT.java
index 7025acbc..7772a159 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/functioninfo/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/functioninfo/URLClientIT.java
@@ -86,7 +86,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: functionInfoGetNameTest
*
- * @assertion_ids: JSP:JAVADOC:315
+ * @assertion_ids: PAGES:JAVADOC:315
*
* @test_Strategy: Validate the container properly parses the function
* information in the provided TLD and the method calls, in this case,
@@ -103,7 +103,7 @@ public void functionInfoGetNameTest() throws Exception {
/*
* @testName: functionInfoGetFunctionClassTest
*
- * @assertion_ids: JSP:JAVADOC:316
+ * @assertion_ids: PAGES:JAVADOC:316
*
* @test_Strategy: Validate the container properly parses the function
* information in the provided TLD and the method calls, in this case,
@@ -120,7 +120,7 @@ public void functionInfoGetFunctionClassTest() throws Exception {
/*
* @testName: functionInfoGetFunctionSignatureTest
*
- * @assertion_ids: JSP:JAVADOC:317
+ * @assertion_ids: PAGES:JAVADOC:317
*
* @test_Strategy: Validate the container properly parses the function
* information in the provided TLD and the method calls, in this case,
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/jspidconsumer/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/jspidconsumer/URLClientIT.java
index c7f929d8..2da88c8c 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/jspidconsumer/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/jspidconsumer/URLClientIT.java
@@ -74,7 +74,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: setJspIdTest
*
- * @assertion_ids: JSP:JAVADOC:434
+ * @assertion_ids: PAGES:JAVADOC:434
*
* @test_Strategy: Validate the behavior of JspIdConsumer.setJspId() Implement
* the setJspId() method in a tag handler. Verify that the ID generated
@@ -91,7 +91,7 @@ public void setJspIdTest() throws Exception {
/*
* @testName: multipleJspIdTest
*
- * @assertion_ids: JSP:JAVADOC:434
+ * @assertion_ids: PAGES:JAVADOC:434
*
* @test_Strategy: Validate the behavior of JspIdConsumer.setJspId() Implement
* the setJspId() method in multiple tag handlers. Verify that each tag has a
@@ -108,7 +108,7 @@ public void multipleJspIdTest() throws Exception {
/*
* @testName: sameJspIdTest
*
- * @assertion_ids: JSP:JAVADOC:434
+ * @assertion_ids: PAGES:JAVADOC:434
*
* @test_Strategy: Validate the behavior of JspIdConsumer.setJspId() Implement
* the setJspId() method in a single tag handler. Verify that when the jsp
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/pagedata/PageDataValidator.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/pagedata/PageDataValidator.java
index d353b217..dbf8738f 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/pagedata/PageDataValidator.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/pagedata/PageDataValidator.java
@@ -68,8 +68,8 @@ public PageDataValidator() {
}
/**
- * Validates the XML view of the JSP page using the provided PageData object.
- *
+ * Validates the XML view of the Jakarta Pages page using the provided PageData object.
+ *
* @param prefix
* - the tag library prefix
* @param uri
@@ -118,7 +118,7 @@ public void release() {
/**
* Returns the TVL invocation status.
- *
+ *
* @return true if the TLV has been called, otherwise false
*/
public static boolean wasCalled() {
@@ -156,8 +156,8 @@ private void initializeSaxParserFactory() throws ParserConfigurationException,
}
/**
- * Displays the XML view of a JSP page as seen by the container.
- *
+ * Displays the XML view of a Jakarta Pages page as seen by the container.
+ *
* @param in
* - the InputStream from PageData
*/
@@ -173,12 +173,12 @@ private static void displayXmlView(InputStream in) {
out.write(i);
}
- debug("*************** XML View of JSP Page ***************");
+ debug("********** XML View of Jakarta Pages Page **********");
debug(out.toString());
debug("****************************************************");
} catch (Throwable t) {
debug("[INFO] Unexpected exception while trying to display XML view "
- + "of the JSP page.");
+ + "of the Jakarta Pages page.");
} finally {
try {
bin.close();
@@ -193,7 +193,7 @@ private static void displayXmlView(InputStream in) {
/**
* Utility method to wrap JspTestUtil.debug(). This method will add this
* class' name to the provide message and then delegate to JspTestUtil.
- *
+ *
* @param message
* - a debug message
*/
@@ -203,7 +203,7 @@ private static void debug(String message) {
/**
* An extension to the DefaultHandler to process the elements within the XML
- * view of a JSP page.
+ * view of a Jakarta Pages page.
*/
private static class PageHandler extends DefaultHandler {
@@ -244,7 +244,7 @@ private static class PageHandler extends DefaultHandler {
/**
* The jsp:directive.include element. NOTE: this should
- * not appear in the XML view of a JSP page.
+ * not appear in the XML view of a Jakarta Pages page.
*/
private static final String JSP_INCL_QN = "jsp:directive.include";
@@ -303,7 +303,7 @@ private static class PageHandler extends DefaultHandler {
/**
* Counter indicating that the RT expression present in the
- * pagedata.test element was properly converted from standard JSP
+ * pagedata.test element was properly converted from standard Jakarta Pages
* syntax to syntax supported by XML.
*/
private short _rtExprFound = 0;
@@ -333,7 +333,7 @@ public PageHandler() {
/**
* Handles the start elements found in the XML stream by the parser.
- *
+ *
* @param uri
* - the uri of the namespace
* @param localName
@@ -390,7 +390,7 @@ public void startElement(String uri, String localName, String qName,
String value = attributes.getValue(i).trim();
debug("pagedata:test attribute '" + name + "' value: " + value);
if (value.startsWith("%=") && (value.endsWith("%"))) {
- debug("Converted JSP RT attribute expression was found!");
+ debug("Converted Jakarta Pages RT attribute expression was found!");
_rtExprFound++;
}
}
@@ -424,7 +424,7 @@ public void startElement(String uri, String localName, String qName,
/**
* Checks the instance variables used to count the elements processed and
* based on the values, will return failure messages.
- *
+ *
* @return null of no errors occurred, othersise an array of
* ValidationMessages noting the failures.
*/
@@ -434,77 +434,77 @@ public ValidationMessage[] getParsingResults() {
List messageList = new ArrayList();
if (_scrWasFound == 0) {
messageList.add(
- "Unable to find the jsp:scriptlet element in theXML view of the processed JSP page.\n");
+ "Unable to find the jsp:scriptlet element in the XML view of the processed Jakarta Pages page.\n");
}
if (_scrWasFound > 1) {
messageList.add("Found " + _scrWasFound
- + " jsp:scriplet elements in the XML view of the processed JSP page when 1 was expected.\n");
+ + " jsp:scriplet elements in the XML view of the processed Jakarta Pages page when 1 was expected.\n");
}
if (_declWasFound == 0) {
messageList.add(
- "Unable to find the jsp:declaration element in the XML view of the processed JSP page.\n");
+ "Unable to find the jsp:declaration element in the XML view of the processed Jakarta Pages page.\n");
}
if (_declWasFound > 1) {
messageList.add("Found " + _declWasFound
- + " jsp:declaration elements in the XML view of the processed JSP page when 1 was expected.\n");
+ + " jsp:declaration elements in the XML view of the processed Jakarta Pages page when 1 was expected.\n");
}
if (_exprWasFound == 0) {
messageList.add(
- "Unable to find the jsp:expression element in the XML view of the JSP page.\n");
+ "Unable to find the jsp:expression element in the XML view of the Jakarta Pages page.\n");
}
if (_exprWasFound > 1) {
messageList.add("Found " + _exprWasFound
- + " jsp:scriplet elements in the XML view of the processed JSP page when 1 was expected.\n");
+ + " jsp:scriplet elements in the XML view of the processed Jakarta Pages page when 1 was expected.\n");
}
if (_tagLibWasFound == 0) {
messageList.add(
- "Unable to find the taglib call pagedata:test element in the XML view of the JSP page.\n");
+ "Unable to find the taglib call pagedata:test element in the XML view of the Jakarta Pages page.\n");
}
if (_tagLibWasFound > 1) {
messageList.add("Found " + _tagLibWasFound
- + " pagedata:test elements in the XML view of the processed JSP page when 1 was expected.\n");
+ + " pagedata:test elements in the XML view of the processed Jakarta Pages page when 1 was expected.\n");
}
if (_tagDeclWasFound == 0) {
messageList.add(
"Unable to find the taglib declaration for uri 'http://java.sun.com/tck/jsp/pagedata' in "
- + "the XML view of the JSP page.\n");
+ + "the XML view of the Jakarta Pages page.\n");
}
if (_tagDeclWasFound > 1) {
messageList.add("Found " + _tagDeclWasFound
- + " xmlns:pagedata attributes of the jsp:root element in the XML view of the processed JSP page when 1 was expected.\n");
+ + " xmlns:pagedata attributes of the jsp:root element in the XML view of the processed Jakarta Pages page when 1 was expected.\n");
}
if (_jspRootWasFound == 0) {
messageList.add(
- "Unable to find the jsp:root element in the XML view of the JSP page.\n");
+ "Unable to find the jsp:root element in the XML view of the Jakarta Pages page.\n");
}
if (_jspRootWasFound > 1) {
messageList.add("Found " + _jspRootWasFound
- + " jsp:root elements in the XML view of the processed JSP page when 1 was expected.\n");
+ + " jsp:root elements in the XML view of the processed Jakarta Pages page when 1 was expected.\n");
}
if (_textWasFound == 0) {
messageList.add(
- "Unable to find the jsp:text element in the XML view of the JSP page.\n");
+ "Unable to find the jsp:text element in the XML view of the Jakarta Pages page.\n");
}
if (_pageDirectiveFound == 0) {
messageList.add(
- "Unable to find the jsp:page.directive element in the XML view of the JSP page.\n");
+ "Unable to find the jsp:page.directive element in the XML view of the Jakarta Pages page.\n");
}
if (_pageDirectiveFound > 1) {
messageList.add("Found " + _pageDirectiveFound
- + " jsp:directive.page elements in the XML view of the processed JSP page when 1 was expected.\n");
+ + " jsp:directive.page elements in the XML view of the processed Jakarta Pages page when 1 was expected.\n");
}
if (_includeDirectiveFound != 0) {
messageList.add(
- "Unexpectedly found a jsp:directive.include element in the XML view of the JSP page.\n");
+ "Unexpectedly found a jsp:directive.include element in the XML view of the Jakarta Pages page.\n");
}
if (_jspNameSpaceFound == 0) {
messageList.add(
- "Unable to find JSP namespace xmlns:jsp with URI of 'http://java.sun.com/JSP/Page'"
- + " in the XML view of the JSP page.\n");
+ "Unable to find Jakarta Pages namespace xmlns:jsp with URI of 'http://java.sun.com/JSP/Page'"
+ + " in the XML view of the Jakarta Pages page.\n");
}
if (_jspNameSpaceFound > 1) {
messageList.add("Found " + _jspNameSpaceFound
- + " JSP namespace attributes within the jsp:root element in the XML view of the processed JSP page when 1 was expected.\n");
+ + " Jakarta Pages namespace attributes within the jsp:root element in the XML view of the processed Jakarta Pages page when 1 was expected.\n");
}
if (_rtExprFound == 0) {
messageList.add(
@@ -512,7 +512,7 @@ public ValidationMessage[] getParsingResults() {
}
if (_rtExprFound > 1) {
messageList.add("Found " + _rtExprFound
- + " rt expressions in the XML view of the JSP page, expected only 1.\n");
+ + " rt expressions in the XML view of the Jakarta Pages page, expected only 1.\n");
}
if (_jspRootVersionFound == 0) {
messageList.add(
@@ -542,7 +542,7 @@ public ValidationMessage[] getParsingResults() {
* Checks that the jsp:id attribute exists in the attribute list of the
* specified element. If it doesn't it adds this element name to a list of
* elements that have a similar issue.
- *
+ *
* @param elementName
* - name of the element
* @param attributes
@@ -565,7 +565,7 @@ private void checkJspIdAttribute(String elementName,
/**
* Scans the provided attribute object for the specified attribute name and
* value. If value is null, then only the attribute name is checked.
- *
+ *
* @param attrName
* - name of the attribute to check for
* @param attrValue
@@ -601,7 +601,7 @@ private boolean hasAttribute(String attrName, String attrValue,
/**
* Returns a string representation of the Map containing elements and the
* occurrence count.
- *
+ *
* @param map
* - element map
* @return String representation of the map
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/pagedata/TagFilePageDataValidator.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/pagedata/TagFilePageDataValidator.java
index 81866acf..3f367066 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/pagedata/TagFilePageDataValidator.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/pagedata/TagFilePageDataValidator.java
@@ -68,8 +68,8 @@ public TagFilePageDataValidator() {
}
/**
- * Validates the XML view of the JSP page using the provided PageData object.
- *
+ * Validates the XML view of the Jakarta Pages page using the provided PageData object.
+ *
* @param prefix
* - the tag library prefix
* @param uri
@@ -118,7 +118,7 @@ public void release() {
/**
* Returns the TVL invocation status.
- *
+ *
* @return true if the TLV has been called, otherwise false
*/
public static boolean wasCalled() {
@@ -156,8 +156,8 @@ private void initializeSaxParserFactory() throws ParserConfigurationException,
}
/**
- * Displays the XML view of a JSP page as seen by the container.
- *
+ * Displays the XML view of a Jakarta Pages page as seen by the container.
+ *
* @param in
* - the InputStream from PageData
*/
@@ -193,7 +193,7 @@ private static void displayXmlView(InputStream in) {
/**
* Utility method to wrap JspTestUtil.debug(). This method will add this
* class' name to the provide message and then delegate to JspTestUtil.
- *
+ *
* @param message
* - a debug message
*/
@@ -318,7 +318,7 @@ private class PageHandler extends DefaultHandler {
/**
* Counter indicating that the RT expression present in the
* pagedatatagfile.test element was properly converted from
- * standard JSP syntax to syntax supported by XML.
+ * standard Jakarta Pages syntax to syntax supported by XML.
*/
private short _rtExprFound = 0;
@@ -347,7 +347,7 @@ public PageHandler() {
/**
* Handles the start elements found in the XML stream by the parser.
- *
+ *
* @param uri
* - the uri of the namespace
* @param localName
@@ -405,7 +405,7 @@ public void startElement(String uri, String localName, String qName,
debug("pagedatatagfile:test attribute '" + name + "' value: "
+ value);
if (value.startsWith("%=") && (value.endsWith("%"))) {
- debug("Converted JSP RT attribute expression was found!");
+ debug("Converted Jakarta Pages RT attribute expression was found!");
_rtExprFound++;
}
}
@@ -447,7 +447,7 @@ public void startElement(String uri, String localName, String qName,
/**
* Checks the instance variables used to count the elements processed and
* based on the values, will return failure messages.
- *
+ *
* @return null of no errors occurred, othersise an array of
* ValidationMessages noting the failures.
*/
@@ -538,12 +538,12 @@ public ValidationMessage[] getParsingResults() {
}
if (_jspNameSpaceFound == 0) {
messageList.add(
- "Unable to find JSP namespace xmlns:jsp with URI of 'http://java.sun.com/JSP/Page'"
+ "Unable to find Jakarta Pages namespace xmlns:jsp with URI of 'http://java.sun.com/JSP/Page'"
+ " in the XML view of the tag file.\n");
}
if (_jspNameSpaceFound > 1) {
messageList.add("Found " + _jspNameSpaceFound
- + " JSP namespace attributes within the jsp:root element in the XML view of the processed tag file when 1 was expected.\n");
+ + " Jakarta Pages namespace attributes within the jsp:root element in the XML view of the processed tag file when 1 was expected.\n");
}
if (_rtExprFound == 0) {
messageList.add(
@@ -582,7 +582,7 @@ public ValidationMessage[] getParsingResults() {
* Checks that the jsp:id attribute exists in the attribute list of the
* specified element. If it doesn't it adds this element name to a list of
* elements that have a similar issue.
- *
+ *
* @param elementName
* - name of the element
* @param attributes
@@ -605,7 +605,7 @@ private void checkJspIdAttribute(String elementName,
/**
* Scans the provided attribute object for the specified attribute name and
* value. If value is null, then only the attribute name is checked.
- *
+ *
* @param attrName
* - name of the attribute to check for
* @param attrValue
@@ -641,7 +641,7 @@ private boolean hasAttribute(String attrName, String attrValue,
/**
* Returns a string representation of the Map containing elements and the
* occurence count.
- *
+ *
* @param map
* - element map
* @return String representation of the map
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/pagedata/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/pagedata/URLClientIT.java
index 9c64bb62..90706126 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/pagedata/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/pagedata/URLClientIT.java
@@ -80,16 +80,16 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: pageDataTest
*
- * @assertion_ids: JSP:JAVADOC:313
+ * @assertion_ids: PAGES:JAVADOC:313
*
* @test_Strategy: Validate the following: - We can get an inputstream from
* the PageData object provided to the validation method of the
- * TagLibraryValidator. - Validate the XML view of a JSP page: - page
+ * TagLibraryValidator. - Validate the XML view of a Jakarta Pages page: - page
* directives are jsp:directive.page elements - taglib directives are includes
* in the namespace declaration in the jsp:root element - include directives
* are not present in the XML view - template text is wrapped by jsp:text
* elements - scriptlets are wrapped by jsp:scriptlet elements - declarations
- * are wrapped by jsp:declaration elements - JSP expressions are wrapped by
+ * are wrapped by jsp:declaration elements - Jakarta Pages expressions are wrapped by
* jsp:expression elements - rt expressions are converted from '<%=' '%>' to
* '%=' '%' - Custom taglib usages are passed through - the jsp:root element
* is present - the jsp namespace is present in the jsp:root element.
@@ -107,7 +107,7 @@ public void pageDataTest() throws Exception {
/*
* @testName: pageDataTagFileTest
*
- * @assertion_ids: JSP:JAVADOC:313
+ * @assertion_ids: PAGES:JAVADOC:313
*
* @test_Strategy: same as above.
*/
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/simpletagsupport/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/simpletagsupport/URLClientIT.java
index 3dca40bc..0ef58c5a 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/simpletagsupport/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/simpletagsupport/URLClientIT.java
@@ -108,7 +108,7 @@ public static WebArchive createDeployment() {
/*
* @testName: simpleTagSupportDoTagDefaultTest
*
- * @assertion_ids: JSP:JAVADOC:301;JSP:JAVADOC:356
+ * @assertion_ids: PAGES:JAVADOC:301;PAGES:JAVADOC:356
*
* @test_Strategy: This validates that the default behavior of
* SimpleTagSupport.doTag() does nothing. If this is indeed the case, no
@@ -126,7 +126,7 @@ public void simpleTagSupportDoTagDefaultTest() throws Exception {
/*
* @testName: simpleTagSupportSkipPageExceptionTest
*
- * @assertion_ids: JSP:JAVADOC:304;JSP:JAVADOC:359
+ * @assertion_ids: PAGES:JAVADOC:304;PAGES:JAVADOC:359
*
* @test_Strategy: Validate the containers behavior with regards to: - Simple
* Tag Handler generated from a tag file throws a SkipPageException if an
@@ -149,7 +149,7 @@ public void simpleTagSupportSkipPageExceptionTest() throws Exception {
/*
* @testName: simpleTagSupportGetSetJspContextTest
*
- * @assertion_ids: JSP:JAVADOC:307;JSP:JAVADOC:308;JSP:JAVADOC:362
+ * @assertion_ids: PAGES:JAVADOC:307;PAGES:JAVADOC:308;PAGES:JAVADOC:362
*
* @test_Strategy: Validate that getJspContext() returnes a non-null value as
* the container called setJspContext() prior to invoking doGet().
@@ -165,7 +165,7 @@ public void simpleTagSupportGetSetJspContextTest() throws Exception {
/*
* @testName: simpleTagSupportGetSetJspBodyTest
*
- * @assertion_ids: JSP:JAVADOC:309;JSP:JAVADOC:310;JSP:JAVADOC:363
+ * @assertion_ids: PAGES:JAVADOC:309;PAGES:JAVADOC:310;PAGES:JAVADOC:363
*
* @test_Strategy: Validate that getJspBody() returnes a non-null value as the
* container called setJspBody() prior to invoking doGet().
@@ -181,8 +181,8 @@ public void simpleTagSupportGetSetJspBodyTest() throws Exception {
/*
* @testName: simpleTagSupportGetSetParentTest
*
- * @assertion_ids: JSP:JAVADOC:305;JSP:JAVADOC:306;JSP:JAVADOC:360;
- * JSP:JAVADOC:361
+ * @assertion_ids: PAGES:JAVADOC:305;PAGES:JAVADOC:306;PAGES:JAVADOC:360;
+ * PAGES:JAVADOC:361
*
* @test_Strategy: Validate that getParent() returnes a non-null value as the
* container called setParent() prior to invoking doGet().
@@ -198,7 +198,7 @@ public void simpleTagSupportGetSetParentTest() throws Exception {
/*
* @testName: simpleTagSupportFindAncestorTest
*
- * @assertion_ids: JSP:JAVADOC:311
+ * @assertion_ids: PAGES:JAVADOC:311
*
* @test_Strategy: Validate that findAncestorWithClass() where the validation
* is preformed nested within a SimpleTag handler as well as a Classic Tag
@@ -215,7 +215,7 @@ public void simpleTagSupportFindAncestorTest() throws Exception {
/*
* @testName: simpleTagSupportVariableSynchronizationTest
*
- * @assertion_ids: JSP:JAVADOC:400
+ * @assertion_ids: PAGES:JAVADOC:400
*
* @testStrategy: Validate variable synchronization for AT_END and and
* AT_BEGIN variables occurs after doTag() has been called. This should occur
@@ -233,7 +233,7 @@ public void simpleTagSupportVariableSynchronizationTest() throws Exception {
/*
* @testName: tagHandlerCacheTest
*
- * @assertion_ids: JSP:JAVADOC:300
+ * @assertion_ids: PAGES:JAVADOC:300
*
* @test_Strategy: compare instances of a simple tag handler class across
* different invocations.
@@ -250,7 +250,7 @@ public void tagHandlerCacheTest() throws Exception {
/*
* @testName: emptySetJspBodyTest
*
- * @assertion_ids: JSP:JAVADOC:300
+ * @assertion_ids: PAGES:JAVADOC:300
*
* @test_Strategy: If the action element is empty in the page, setJpsBody
* method is not called at all.
@@ -267,7 +267,7 @@ public void emptySetJspBodyTest() throws Exception {
/*
* @testName: noParentTest
*
- * @assertion_ids: JSP:JAVADOC:300
+ * @assertion_ids: PAGES:JAVADOC:300
*
* @test_Strategy: The container invokes setParent() method only if this tag
* invocation is nested within another tag invocation.
@@ -284,7 +284,7 @@ public void noParentTest() throws Exception {
/*
* @testName: jspFragmentGetJspContextTest
*
- * @assertion_ids: JSP:JAVADOC:300
+ * @assertion_ids: PAGES:JAVADOC:300
*
* @test_Strategy: jspFragment.getJspContext() returns the JspContext that is
* bound to this JspFragment.
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagadapter/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagadapter/URLClientIT.java
index 66aadf66..8c19d936 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagadapter/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagadapter/URLClientIT.java
@@ -85,7 +85,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: tagAdapterCtorTest
*
- * @assertion_ids: JSP:JAVADOC:285
+ * @assertion_ids: PAGES:JAVADOC:285
*
* @test_Strategy: Validates the constructor of the TagAdapter class.
*/
@@ -98,7 +98,7 @@ public void tagAdapterCtorTest() throws Exception {
/*
* @testName: tagAdapterSetPageContextTest
*
- * @assertion_ids: JSP:JAVADOC:287
+ * @assertion_ids: PAGES:JAVADOC:287
*
* @test_Strategy: Validates that an UnsupportedOperationException is thrown
* if a call to TagAdapter.setPageContext() is made.
@@ -112,7 +112,7 @@ public void tagAdapterSetPageContextTest() throws Exception {
/*
* @testName: tagAdapterSetParentTest
*
- * @assertion_ids: JSP:JAVADOC:289
+ * @assertion_ids: PAGES:JAVADOC:289
*
* @test_Strategy: Validates that an UnsupportedOperationException is thrown
* if a call to TagAdapter.setParent() is made.
@@ -126,7 +126,7 @@ public void tagAdapterSetParentTest() throws Exception {
/*
* @testName: tagAdapterGetParentTest
*
- * @assertion_ids: JSP:JAVADOC:290
+ * @assertion_ids: PAGES:JAVADOC:290
*
* @test_Strategy: Validates that getParent always returns
* getAdaptee().getParent()
@@ -140,7 +140,7 @@ public void tagAdapterGetParentTest() throws Exception {
/*
* @testName: tagAdapterDoStartTagTest
*
- * @assertion_ids: JSP:JAVADOC:293;JSP:JAVADOC:294
+ * @assertion_ids: PAGES:JAVADOC:293;PAGES:JAVADOC:294
*
* @test_Strategy: Validates that an UnsupportedOperationException is thrown
* if a call to TagAdapter.doStartTag() is made.
@@ -154,7 +154,7 @@ public void tagAdapterDoStartTagTest() throws Exception {
/*
* @testName: tagAdapterDoEndTagTest
*
- * @assertion_ids: JSP:JAVADOC:296;JSP:JAVADOC:297
+ * @assertion_ids: PAGES:JAVADOC:296;PAGES:JAVADOC:297
*
* @test_Strategy: Validates that an UnsupportedOperationException is thrown
* if a call to TagAdapter.doEndTag() is made.
@@ -168,7 +168,7 @@ public void tagAdapterDoEndTagTest() throws Exception {
/*
* @testName: tagAdapterReleaseTest
*
- * @assertion_ids: JSP:JAVADOC:299
+ * @assertion_ids: PAGES:JAVADOC:299
*
* @test_Strategy: Validates that an UnsupportedOperationException is thrown
* if a call to TagAdapter.release() is made.
@@ -182,12 +182,12 @@ public void tagAdapterReleaseTest() throws Exception {
/*
* @testName: tagAdapterValidationTest
*
- * @assertion_ids: JSP:JAVADOC:286;JSP:JAVADOC:288;JSP:JAVADOC:291;
- * JSP:JAVADOC:292;JSP:JAVADOC:295;JSP:JAVADOC:298; JSP:JAVADOC:290
+ * @assertion_ids: PAGES:JAVADOC:286;PAGES:JAVADOC:288;PAGES:JAVADOC:291;
+ * PAGES:JAVADOC:292;PAGES:JAVADOC:295;PAGES:JAVADOC:298; PAGES:JAVADOC:290
*
* @test_Strategy: This validates that the container properly wraps a
* SimpleTag instance with a TagAdapter when a Classic tag handler is a child
- * of the SimpleTag handler within the JSP Page. This also makes the
+ * of the SimpleTag handler within the Jakarta Pages Page. This also makes the
* assumption, that all of the previous tests passed as it expects an
* UnsupportedOperationException to be thrown if an illegal method call is
* made on the TagAdapter.
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagattributeinfo/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagattributeinfo/URLClientIT.java
index 14c5f9d5..34eef48a 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagattributeinfo/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagattributeinfo/URLClientIT.java
@@ -88,7 +88,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: tagAttributeInfoGetNameTest
*
- * @assertion_ids: JSP:JAVADOC:278
+ * @assertion_ids: PAGES:JAVADOC:278
*
* @test_Strategy: Validate the behavior of TagAttributeInfo.getName().
*/
@@ -103,7 +103,7 @@ public void tagAttributeInfoGetNameTest() throws Exception {
/*
* @testName: tagAttributeInfoGetTypeNameTest
*
- * @assertion_ids: JSP:JAVADOC:279
+ * @assertion_ids: PAGES:JAVADOC:279
*
* @test_Strategy: Validate the behavior of TagAttributeInfo.getTypeName().
*/
@@ -118,7 +118,7 @@ public void tagAttributeInfoGetTypeNameTest() throws Exception {
/*
* @testName: tagAttributeInfoCanBeRequestTimeTest
*
- * @assertion_ids: JSP:JAVADOC:280
+ * @assertion_ids: PAGES:JAVADOC:280
*
* @test_Strategy: Validate the behavior of
* TagAttributeInfo.catBeRequestTime().
@@ -134,7 +134,7 @@ public void tagAttributeInfoCanBeRequestTimeTest() throws Exception {
/*
* @testName: tagAttributeInfoIsRequiredTest
*
- * @assertion_ids: JSP:JAVADOC:281
+ * @assertion_ids: PAGES:JAVADOC:281
*
* @test_Strategy: Validate the behavior of TagAttributeInfo.isRequired().
*/
@@ -149,7 +149,7 @@ public void tagAttributeInfoIsRequiredTest() throws Exception {
/*
* @testName: tagAttributeInfoIsFragmentTest
*
- * @assertion_ids: JSP:JAVADOC:283
+ * @assertion_ids: PAGES:JAVADOC:283
*
* @test_Strategy: Validate the behavior of TagAttributeInfo.siFragment().
*/
@@ -164,7 +164,7 @@ public void tagAttributeInfoIsFragmentTest() throws Exception {
/*
* @testName: tagAttributeInfoToStringTest
*
- * @assertion_ids: JSP:JAVADOC:284
+ * @assertion_ids: PAGES:JAVADOC:284
*
* @test_Strategy: Validate the behavior of TagAttributeInfo.toString().
*/
@@ -179,7 +179,7 @@ public void tagAttributeInfoToStringTest() throws Exception {
/*
* @testName: tagAttributeInfoGetIdAttribute
*
- * @assertion_ids: JSP:JAVADOC:282
+ * @assertion_ids: PAGES:JAVADOC:282
*
* @test_Strategy: Convenience static method that goes through an array of
* TagAttributeInfo objects and looks for "id".
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagdata/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagdata/URLClientIT.java
index c043c69a..db0824ed 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagdata/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagdata/URLClientIT.java
@@ -85,7 +85,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: tagDataGetAttributeTest
*
- * @assertion_ids: JSP:JAVADOC:271
+ * @assertion_ids: PAGES:JAVADOC:271
*
* @test_Strategy: Validate the behavior of TagData.getAttribute().
*/
@@ -100,7 +100,7 @@ public void tagDataGetAttributeTest() throws Exception {
/*
* @testName: tagDataSetAttributeTest
*
- * @assertion_ids: JSP:JAVADOC:272
+ * @assertion_ids: PAGES:JAVADOC:272
*
* @test_Strategy: Validate the behavior of TagData.setAttribute().
*/
@@ -115,7 +115,7 @@ public void tagDataSetAttributeTest() throws Exception {
/*
* @testName: tagDataGetAttributeStringTest
*
- * @assertion_ids: JSP:JAVADOC:273;JSP:JAVADOC:274
+ * @assertion_ids: PAGES:JAVADOC:273;PAGES:JAVADOC:274
*
* @test_Strategy: Validate the behavior of TagData.getAttributeString().
*/
@@ -130,7 +130,7 @@ public void tagDataGetAttributeStringTest() throws Exception {
/*
* @testName: tagDataGetAttributesTest
*
- * @assertion_ids: JSP:JAVADOC:275
+ * @assertion_ids: PAGES:JAVADOC:275
*
* @test_Strategy: Validate the behavior of TagData.getAttributes().
*/
@@ -145,7 +145,7 @@ public void tagDataGetAttributesTest() throws Exception {
/*
* @testName: tagDataConstructorTest
*
- * @assertion_ids: JSP:JAVADOC:268
+ * @assertion_ids: PAGES:JAVADOC:268
*
* @test_Strategy: validate the constructor TagData(Object[][]).
*/
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagextrainfo/TagExtraInfoTEI.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagextrainfo/TagExtraInfoTEI.java
index b3392bb4..eed85ae7 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagextrainfo/TagExtraInfoTEI.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagextrainfo/TagExtraInfoTEI.java
@@ -46,13 +46,13 @@ public TagExtraInfoTEI() {
/**
* Validates that TagExtraInfo instances are properly handled by the
* container.
- *
+ *
* @param tagData
* @return
*/
public ValidationMessage[] validate(TagData tagData) {
- // Checked within the JSP to make sure the TEI was
+ // Checked within the page to make sure the TEI was
// called by the container.
_wasCalled = true;
@@ -123,7 +123,7 @@ public ValidationMessage[] validate(TagData tagData) {
/**
* Used to validate the proper default behavior of TagExtraInfo.validate().
- *
+ *
* @param data
* - a TagData instance
* @return - true of _returnFalse is false, otherwise true.
@@ -139,7 +139,7 @@ public boolean isValid(TagData data) {
/**
* Called within the test pages to verify that the TEI was indeed called.
- *
+ *
* @return true if called, otherwise false
*/
public static boolean teiWasCalled() {
@@ -157,7 +157,7 @@ public static void reset() {
/**
* Wraps JspTestUtil.debug. This also prepends this TEI's classname to the
* debug message.
- *
+ *
* @param message
* - the debug message
*/
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagextrainfo/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagextrainfo/URLClientIT.java
index 804e30ee..b3d89c79 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagextrainfo/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagextrainfo/URLClientIT.java
@@ -84,7 +84,7 @@ public static WebArchive createDeployment() throws IOException {
* @testName: tagExtraInfoTest
*
* @assertion_ids:
- * JSP:JAVADOC:264;JSP:JAVADOC:265;JSP:JAVADOC:266;JSP:JAVADOC:267
+ * PAGES:JAVADOC:264;PAGES:JAVADOC:265;PAGES:JAVADOC:266;PAGES:JAVADOC:267
*
* @test_Strategy: Validate the following: - TagExtraInfo.getTagInfo() returns
* a non-null value as the container called TagExtraInfo.setTagInfo() prior to
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagfileinfo/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagfileinfo/URLClientIT.java
index 19183796..236b2396 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagfileinfo/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagfileinfo/URLClientIT.java
@@ -87,7 +87,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: tagFileInfoGetNameTest
*
- * @assertion_ids: JSP:JAVADOC:259
+ * @assertion_ids: PAGES:JAVADOC:259
*
* @test_Strategy: Validate TagFileInfo.getName returns the expected values
* based on what is defined in the TLD.
@@ -103,7 +103,7 @@ public void tagFileInfoGetNameTest() throws Exception {
/*
* @testName: tagFileInfoGetPathTest
*
- * @assertion_ids: JSP:JAVADOC:260
+ * @assertion_ids: PAGES:JAVADOC:260
*
* @test_Strategy: Validate TagFileInfo.getPath() returns the expected values
* based on what is defined in the TLD.
@@ -119,7 +119,7 @@ public void tagFileInfoGetPathTest() throws Exception {
/*
* @testName: tagFileInfoGetTagInfoTest
*
- * @assertion_ids: JSP:JAVADOC:261
+ * @assertion_ids: PAGES:JAVADOC:261
*
* @test_Strategy: Validate TagFileInfo.getTagInfo() returns the expected
* values based on what is defined in the tag file.
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/taginfo/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/taginfo/URLClientIT.java
index 432e5be0..37e1d94c 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/taginfo/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/taginfo/URLClientIT.java
@@ -91,7 +91,7 @@ public static WebArchive createDeployment() {
/*
* @testName: tagInfoGetTagNameTest
*
- * @assertion_ids: JSP:JAVADOC:232
+ * @assertion_ids: PAGES:JAVADOC:232
*
* @test_Strategy: Validate TagInfo.getTagName() returns the expected values
* based on what is defined in the TLD.
@@ -107,7 +107,7 @@ public void tagInfoGetTagNameTest() throws Exception {
/*
* @testName: tagInfoGetAttributesTest
*
- * @assertion_ids: JSP:JAVADOC:233
+ * @assertion_ids: PAGES:JAVADOC:233
*
* @test_Strategy: Validate TagInfo.getAttributes() returns the expected
* values based on what is defined in the TLD.
@@ -123,7 +123,7 @@ public void tagInfoGetAttributesTest() throws Exception {
/*
* @testName: tagInfoGetTagExtraInfoTest
*
- * @assertion_ids: JSP:JAVADOC:237;JSP:JAVADOC:238
+ * @assertion_ids: PAGES:JAVADOC:237;PAGES:JAVADOC:238
*
* @test_Strategy: Validate TagInfo.getTagExtraInfo() returns the expected
* values based on what is defined in the TLD. This implicitly tests
@@ -140,7 +140,7 @@ public void tagInfoGetTagExtraInfoTest() throws Exception {
/*
* @testName: tagInfoGetTagClassNameTest
*
- * @assertion_ids: JSP:JAVADOC:239
+ * @assertion_ids: PAGES:JAVADOC:239
*
* @test_Strategy: Validate TagInfo.getTagClassName() returns the expected
* values based on what is defined in the TLD.
@@ -156,7 +156,7 @@ public void tagInfoGetTagClassNameTest() throws Exception {
/*
* @testName: tagInfoGetBodyContentTest
*
- * @assertion_ids: JSP:JAVADOC:240
+ * @assertion_ids: PAGES:JAVADOC:240
*
* @test_Strategy: Validate TagInfo.getBodyContent() returns the expected
* values based on what is defined in the TLD.
@@ -172,7 +172,7 @@ public void tagInfoGetBodyContentTest() throws Exception {
/*
* @testName: tagInfoGetInfoStringTest
*
- * @assertion_ids: JSP:JAVADOC:241
+ * @assertion_ids: PAGES:JAVADOC:241
*
* @test_Strategy: Validate TagInfo.getInfoString() returns the expected
* values based on what is defined in the TLD.
@@ -188,7 +188,7 @@ public void tagInfoGetInfoStringTest() throws Exception {
/*
* @testName: tagInfoGetTagLibraryTest
*
- * @assertion_ids: JSP:JAVADOC:242;JSP:JAVADOC:243
+ * @assertion_ids: PAGES:JAVADOC:242;PAGES:JAVADOC:243
*
* @test_Strategy: Validate TagInfo.getAttributes() returns the expected
* values based on what is defined in the TLD. This implicitly tests
@@ -205,7 +205,7 @@ public void tagInfoGetTagLibraryTest() throws Exception {
/*
* @testName: tagInfoGetDisplayNameTest
*
- * @assertion_ids: JSP:JAVADOC:244
+ * @assertion_ids: PAGES:JAVADOC:244
*
* @test_Strategy: Validate TagInfo.getDisplayName() returns the expected
* values based on what is defined in the TLD.
@@ -221,7 +221,7 @@ public void tagInfoGetDisplayNameTest() throws Exception {
/*
* @testName: tagInfoGetSmallIconTest
*
- * @assertion_ids: JSP:JAVADOC:245
+ * @assertion_ids: PAGES:JAVADOC:245
*
* @test_Strategy: Validate TagInfo.getSmallIconName() returns the expected
* values based on what is defined in the TLD.
@@ -237,7 +237,7 @@ public void tagInfoGetSmallIconTest() throws Exception {
/*
* @testName: tagInfoGetLargeIconTest
*
- * @assertion_ids: JSP:JAVADOC:246
+ * @assertion_ids: PAGES:JAVADOC:246
*
* @test_Strategy: Validate TagInfo.getLargeIconName() returns the expected
* values based on what is defined in the TLD.
@@ -253,7 +253,7 @@ public void tagInfoGetLargeIconTest() throws Exception {
/*
* @testName: tagInfoGetTagVariableInfosTest
*
- * @assertion_ids: JSP:JAVADOC:247
+ * @assertion_ids: PAGES:JAVADOC:247
*
* @test_Strategy: Validate TagInfo.getTagVariableInfos() returns the expected
* values based on what is defined in the TLD.
@@ -269,7 +269,7 @@ public void tagInfoGetTagVariableInfosTest() throws Exception {
/*
* @testName: tagInfoHasDynamicAttributesTest
*
- * @assertion_ids: JSP:JAVADOC:248
+ * @assertion_ids: PAGES:JAVADOC:248
*
* @test_Strategy: Validate TagInfo.hasDynamicAttributes() returns the
* expected values based on what is defined in the TLD.
@@ -285,7 +285,7 @@ public void tagInfoHasDynamicAttributesTest() throws Exception {
/*
* @testName: tagInfoSetTagExtraInfoTest
*
- * @assertion_ids: JSP:JAVADOC:237
+ * @assertion_ids: PAGES:JAVADOC:237
*
* @test_Strategy: Set the instance for extra tag information
*/
@@ -300,7 +300,7 @@ public void tagInfoSetTagExtraInfoTest() throws Exception {
/*
* @testName: tagInfoSetTagLibraryTest
*
- * @assertion_ids: JSP:JAVADOC:242
+ * @assertion_ids: PAGES:JAVADOC:242
*
* @test_Strategy: Set the TagLibraryInfo property.
*/
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/taglibraryinfo/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/taglibraryinfo/URLClientIT.java
index 78f6b8aa..3420efe5 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/taglibraryinfo/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/taglibraryinfo/URLClientIT.java
@@ -37,8 +37,6 @@
* generated and a ValidationMessage array will be returned.
*/
import java.io.IOException;
-import java.io.InputStream;
-
import org.jboss.arquillian.container.test.api.Deployment;
import org.jboss.arquillian.junit5.ArquillianExtension;
import org.jboss.shrinkwrap.api.ShrinkWrap;
@@ -72,10 +70,10 @@ public static WebArchive createDeployment() throws IOException {
SimpleTag.class);
archive.setWebXML(URLClientIT.class.getClassLoader().getResource(packagePath+"/jsp_taglibinfo_web.xml"));
- archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/taglibinfo.tld", "taglibinfo.tld");
- archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/taglibinfo2.tld", "taglibinfo2.tld");
- archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/taglibinfo/TagFile1.tag", "tags/taglibinfo/TagFile1.tag");
- archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/taglibinfo/TagFile2.tag", "tags/taglibinfo/TagFile2.tag");
+ archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/taglibinfo.tld", "taglibinfo.tld");
+ archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/taglibinfo2.tld", "taglibinfo2.tld");
+ archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/taglibinfo/TagFile1.tag", "tags/taglibinfo/TagFile1.tag");
+ archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/taglibinfo/TagFile2.tag", "tags/taglibinfo/TagFile2.tag");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/GetFunctionsTest.jsp")), "GetFunctionsTest.jsp");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/GetFunctionTest.jsp")), "GetFunctionTest.jsp");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/GetInfoStringTest.jsp")), "GetInfoStringTest.jsp");
@@ -93,18 +91,18 @@ public static WebArchive createDeployment() throws IOException {
return archive;
}
-
+
/* Run tests */
// ============================================ Tests ======
/*
* @testName: tagLibraryInfoGetURITest
- *
- * @assertion_ids: JSP:JAVADOC:216
- *
+ *
+ * @assertion_ids: PAGES:JAVADOC:216
+ *
* @test_Strategy: Validate that TagLibaryInfo.getURI() returns the URI as
- * defined by the taglib directive within a JSP page.
+ * defined by the taglib directive within a Jakarta Pages page.
*/
@Test
public void tagLibraryInfoGetURITest() throws Exception {
@@ -116,12 +114,12 @@ public void tagLibraryInfoGetURITest() throws Exception {
/*
* @testName: tagLibraryInfoGetPrefixStringTest
- *
- * @assertion_ids: JSP:JAVADOC:218
- *
+ *
+ * @assertion_ids: PAGES:JAVADOC:218
+ *
* @testStrategy: Validate that TagLibraryInfo.getPrefixString() returns the
* prefix as specified by the prefix attribute of the taglib directive within
- * a JSP page.
+ * a Jakarta Pages page.
*/
@Test
public void tagLibraryInfoGetPrefixStringTest() throws Exception {
@@ -133,9 +131,9 @@ public void tagLibraryInfoGetPrefixStringTest() throws Exception {
/*
* @testName: tagLibraryInfoGetShortNameTest
- *
- * @assertion_ids: JSP:JAVADOC:219
- *
+ *
+ * @assertion_ids: PAGES:JAVADOC:219
+ *
* @testStrategy: Validate that TagLibraryInfo.getShortName() returns the
* short name of the tag library as specified by the <short-name>
* element in a TLD.
@@ -150,9 +148,9 @@ public void tagLibraryInfoGetShortNameTest() throws Exception {
/*
* @testName: tagLibraryInfoGetReliableURNTest
- *
- * @assertion_ids: JSP:JAVADOC:220
- *
+ *
+ * @assertion_ids: PAGES:JAVADOC:220
+ *
* @testStrategy: Validate that TagLibraryInfo.getShortName() returns the uri
* of the tag library as specified by the <uri> element in a TLD.
*/
@@ -166,9 +164,9 @@ public void tagLibraryInfoGetReliableURNTest() throws Exception {
/*
* @testName: tagLibraryInfoGetInfoStringTest
- *
- * @assertion_ids: JSP:JAVADOC:221
- *
+ *
+ * @assertion_ids: PAGES:JAVADOC:221
+ *
* @testStrategy: Validate that TagLibraryInfo.getInfoString() returns the
* description of the tag library as specified by the <description>
* element in a TLD.
@@ -183,9 +181,9 @@ public void tagLibraryInfoGetInfoStringTest() throws Exception {
/*
* @testName: tagLibraryInfoGetRequiredVersionTest
- *
- * @assertion_ids: JSP:JAVADOC:222
- *
+ *
+ * @assertion_ids: PAGES:JAVADOC:222
+ *
* @testStrategy: Validate that TagLibraryInfo.getRequiredVersion() returns
* the require version of the tag library as specified by the
* <required-version> element in a TLD.
@@ -200,9 +198,9 @@ public void tagLibraryInfoGetRequiredVersionTest() throws Exception {
/*
* @testName: tagLibraryInfoGetTagsTest
- *
- * @assertion_ids: JSP:JAVADOC:223
- *
+ *
+ * @assertion_ids: PAGES:JAVADOC:223
+ *
* @testStrategy: Validate that TagLibraryInfo.getTags() returns an array of
* TagInfo objects based off the tags defined by the <tag> elements in a
* TLD.
@@ -217,9 +215,9 @@ public void tagLibraryInfoGetTagsTest() throws Exception {
/*
* @testName: tagLibraryInfoGetTagFilesTest
- *
- * @assertion_ids: JSP:JAVADOC:224
- *
+ *
+ * @assertion_ids: PAGES:JAVADOC:224
+ *
* @testStrategy: Validate that TagLibraryInfo.getTagFiles() returns an array
* of TagFileInfo objects based off the tags files defined by the
* <tag-file> elements in a TLD.
@@ -234,9 +232,9 @@ public void tagLibraryInfoGetTagFilesTest() throws Exception {
/*
* @testName: tagLibraryInfoGetTagTest
- *
- * @assertion_ids: JSP:JAVADOC:225
- *
+ *
+ * @assertion_ids: PAGES:JAVADOC:225
+ *
* @testStrategy: Validate that TagLibraryInfo.getTag() returns a TagInfo
* object based off the provided discriminate.
*/
@@ -250,9 +248,9 @@ public void tagLibraryInfoGetTagTest() throws Exception {
/*
* @testName: tagLibraryInfoGetTagFileTest
- *
- * @assertion_ids: JSP:JAVADOC:226
- *
+ *
+ * @assertion_ids: PAGES:JAVADOC:226
+ *
* @testStrategy: Validate that TagLibraryInfo.getTagFile() returns a
* TagFileInfo object based off the provided discriminate.
*/
@@ -266,9 +264,9 @@ public void tagLibraryInfoGetTagFileTest() throws Exception {
/*
* @testName: tagLibraryInfoGetFunctionsTest
- *
- * @assertion_ids: JSP:JAVADOC:227
- *
+ *
+ * @assertion_ids: PAGES:JAVADOC:227
+ *
* @testStrategy: Validate that TagLibraryInfo.getFunctions() returns an array
* of FunctionInfo objects based off the functions defined by the
* <function> elements in a TLD.
@@ -283,9 +281,9 @@ public void tagLibraryInfoGetFunctionsTest() throws Exception {
/*
* @testName: tagLibraryInfoGetFunctionTest
- *
- * @assertion_ids: JSP:JAVADOC:228
- *
+ *
+ * @assertion_ids: PAGES:JAVADOC:228
+ *
* @testStrategy: Validate that TagLibraryInfo.getFunction() returns a
* FunctionInfo object based off the provided discriminate.
*/
@@ -299,11 +297,11 @@ public void tagLibraryInfoGetFunctionTest() throws Exception {
/*
* @testName: tagLibraryInfoGetTagLibraryInfosTest
- *
- * @assertion_ids: JSP:JAVADOC:440
- *
+ *
+ * @assertion_ids: PAGES:JAVADOC:440
+ *
* @testStrategy: Validate TagLibaryInfo.getTagLibraryInfos() returns an array
- * of TagLibraryInfo objects for all taglibraries declared in the JSP.
+ * of TagLibraryInfo objects for all taglibraries declared in the page.
*/
@Test
public void tagLibraryInfoGetTagLibraryInfosTest() throws Exception {
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/taglibraryvalidator/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/taglibraryvalidator/URLClientIT.java
index cdf0b064..80a881d4 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/taglibraryvalidator/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/taglibraryvalidator/URLClientIT.java
@@ -76,7 +76,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: tagLibraryValidatorAPITest
*
- * @assertion_ids: JSP:JAVADOC:212;JSP:JAVADOC:213;JSP:JAVADOC:214
+ * @assertion_ids: PAGES:JAVADOC:212;PAGES:JAVADOC:213;PAGES:JAVADOC:214
*
* @test_Strategy: Validate the setInitParameters(), getInitParameters(), and
* validate() methods of the TagLibraryValidator class. This will verify that
@@ -99,8 +99,8 @@ public void tagLibraryValidatorAPITest() throws Exception {
/*
* @testName: tagLibraryValidatorTranslationFailureTest
*
- * @assertion_ids: JSP:JAVADOC:182;JSP:JAVADOC:183;
- * JSP:JAVADOC:184;JSP:JAVADOC:386
+ * @assertion_ids: PAGES:JAVADOC:182;PAGES:JAVADOC:183;
+ * PAGES:JAVADOC:184;PAGES:JAVADOC:386
*
* @test_Strategy: Validate that a translation error will occur if a non-null
* or non-empty array of ValidationMessages is returned when the validation()
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagsupport/InitializationTag.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagsupport/InitializationTag.java
index 936b55a3..9170d5e1 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagsupport/InitializationTag.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagsupport/InitializationTag.java
@@ -29,7 +29,7 @@
import jakarta.servlet.jsp.tagext.TagSupport;
/**
- * Tag to verify that the JSP implementation object properly initialized any
+ * Tag to verify that the Jakarta Pages page implementation object properly initialized any
* attributes present with the in tag as well as setting the pageContext and
* parent
*/
@@ -68,7 +68,7 @@ public InitializationTag() {
/**
* Returns the value of _attribute1.
- *
+ *
* @return _attribute1
*/
public String getAttribute1() {
@@ -77,7 +77,7 @@ public String getAttribute1() {
/**
* Sets the value for _attribute1.
- *
+ *
* @param attribute1
* - the value for _attribute1
*/
@@ -87,7 +87,7 @@ public void setAttribute1(String attribute1) {
/**
* Returns the value of _attribute2.
- *
+ *
* @return _attribute2
*/
public String getAttribute2() {
@@ -96,7 +96,7 @@ public String getAttribute2() {
/**
* Sets the value for _attribute2.
- *
+ *
* @param attribute2
* - the value for _attribute2
*/
@@ -106,7 +106,7 @@ public void setAttribute2(String attribute2) {
/**
* Returns the value for _attribute3.
- *
+ *
* @return the value for _attribute3
*/
public String getAttribute3() {
@@ -115,7 +115,7 @@ public String getAttribute3() {
/**
* Sets the value for _attribute3.
- *
+ *
* @param attribute3
* - the value for _attribute3
*/
@@ -124,7 +124,7 @@ public void setAttribute3(String attribute3) {
}
/**
- * Set the current page context. This method is invoked by the JSP page
+ * Set the current page context. This method is invoked by the Jakarta Pages page
* implementation object prior to doStartTag().
*
* This value is *not* reset by doEndTag() and must be explicitly reset by a
@@ -139,7 +139,7 @@ public void setPageContext(PageContext pc) {
/**
* Set the parent (closest enclosing tag handler) of this tag handler. Invoked
- * by the JSP page implementation object prior to doStartTag().
+ * by the Jakarta Pages page implementation object prior to doStartTag().
*
* This value is *not* reset by doEndTag() and must be explicitly reset by a
* page implementation.
@@ -153,7 +153,7 @@ public void setParent(Tag t) {
/**
* Get the parent (closest enclosing tag handler) for this tag handler.
- *
+ *
* @return the current parent, or null if none.
* @see jakarta.servlet.jsp.tagext.TagSupport#findAncestorWithClass
*/
@@ -163,7 +163,7 @@ public Tag getParent() {
/**
* Validates that the tag initialization occurs before calling doStartTag().
- *
+ *
* @return Tag.SKIP_BODY
* @throws JspException
* if an error occurred while processing this tag
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagsupport/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagsupport/URLClientIT.java
index b8fd2c6a..e38259dd 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagsupport/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagsupport/URLClientIT.java
@@ -93,9 +93,9 @@ public static WebArchive createDeployment() throws IOException {
* @testName: tagSupportTagInitializationTest
*
* @assertion_ids:
- * JSP:JAVADOC:342;JSP:JAVADOC:343;JSP:JAVADOC:344;JSP:JAVADOC:345;
- * JSP:JAVADOC:202;JSP:JAVADOC:203;JSP:JAVADOC:204;JSP:JAVADOC:205;
- * JSP:JAVADOC:206
+ * PAGES:JAVADOC:342;PAGES:JAVADOC:343;PAGES:JAVADOC:344;PAGES:JAVADOC:345;
+ * PAGES:JAVADOC:202;PAGES:JAVADOC:203;PAGES:JAVADOC:204;PAGES:JAVADOC:205;
+ * PAGES:JAVADOC:206
*
* @test_Strategy: Validates that the container performs the proper
* initialization steps for a new tag handler instance. The PageContext,
@@ -113,7 +113,7 @@ public void tagSupportTagInitializationTest() throws Exception {
/*
* @testName: tagSupportDoStartEvalBodyIncludeTest
*
- * @assertion_ids: JSP:JAVADOC:345
+ * @assertion_ids: PAGES:JAVADOC:345
*
* @test_Strategy: Validate the when doStartTag returns EVAL_BODY_INCLUDE will
* include the evaluation of the body in the current out. This will be
@@ -133,7 +133,7 @@ public void tagSupportDoStartEvalBodyIncludeTest() throws Exception {
/*
* @testName: tagSupportDoStartSkipBodyTest
*
- * @assertion_ids: JSP:JAVADOC:402
+ * @assertion_ids: PAGES:JAVADOC:402
*
* @test_Strategy: Validate the when doStartTag returns SKIP_BODY, the body of
* the tag is not included in the current out as the body related methods are
@@ -151,7 +151,7 @@ public void tagSupportDoStartSkipBodyTest() throws Exception {
/*
* @testName: tagSupportDoAfterBodySkipBodyTest
*
- * @assertion_ids: JSP:JAVADOC:368
+ * @assertion_ids: PAGES:JAVADOC:368
*
* @test_Strategy: Validate the doAfterBody() is called exactly once when
* doStartTag() returns EVAL_BODY_INCLUDE and doAfterBody() returns SKIP_BODY.
@@ -169,7 +169,7 @@ public void tagSupportDoAfterBodySkipBodyTest() throws Exception {
/*
* @testName: tagSupportDoAfterBodyEvalBodyAgainTest
*
- * @assertion_ids: JSP:JAVADOC:369
+ * @assertion_ids: PAGES:JAVADOC:369
*
* @test_Strategy: Validate the doAfterBody() is called subsequent of
* doAfterBody() being called and returning EVAL_BODY_AGAIN.
@@ -188,7 +188,7 @@ public void tagSupportDoAfterBodyEvalBodyAgainTest() throws Exception {
/*
* @testName: tagSupportDoEndTagSkipPageTest
*
- * @assertion_ids: JSP:JAVADOC:351;JSP:JAVADOC:347
+ * @assertion_ids: PAGES:JAVADOC:351;PAGES:JAVADOC:347
*
* @test_Strategy: Validate that page evaluation ceases when doEndTagReturns
* SKIP_PAGE. This also ensures that doEndTag will not be called in any parent
@@ -213,7 +213,7 @@ public void tagSupportDoEndTagSkipPageTest() throws Exception {
/*
* @testName: tagSupportDoEndTagEvalPageTest
*
- * @assertion_ids: JSP:JAVADOC:350
+ * @assertion_ids: PAGES:JAVADOC:350
*
* @test_Strategy: Validate that if doEndTag() returns EVAL_PAGE, the page
* continues to evaluate.
@@ -230,7 +230,7 @@ public void tagSupportDoEndTagEvalPageTest() throws Exception {
/*
* @testName: tagSupportFindAncestorWithClassTest
*
- * @assertion_ids: JSP:JAVADOC:194
+ * @assertion_ids: PAGES:JAVADOC:194
*
* @test_Strategy: Validate the behavior of findAncestorWithClass when test
* tag is nested with multiple tag instances of the same type.
@@ -246,7 +246,7 @@ public void tagSupportFindAncestorWithClassTest() throws Exception {
/*
* @testName: tagSupportDoStartTagDefaultValueTest
*
- * @assertion_ids: JSP:JAVADOC:195
+ * @assertion_ids: PAGES:JAVADOC:195
*
* @test_Strategy: Validate the default return value of
* TagSupport.doStartTag().
@@ -260,7 +260,7 @@ public void tagSupportDoStartTagDefaultValueTest() throws Exception {
/*
* @testName: tagSupportDoEndTagDefaultValueTest
*
- * @assertion_ids: JSP:JAVADOC:197
+ * @assertion_ids: PAGES:JAVADOC:197
*
* @test_Strategy: Validate the default return value of TagSupport.doEndTag().
*/
@@ -273,7 +273,7 @@ public void tagSupportDoEndTagDefaultValueTest() throws Exception {
/*
* @testName: tagSupportDoAfterBodyDefaultValueTest
*
- * @assertion_ids: JSP:JAVADOC:199
+ * @assertion_ids: PAGES:JAVADOC:199
*
* @test_Strategy: Validate the default return value of
* TagSupport.doAfterBody().
@@ -287,7 +287,7 @@ public void tagSupportDoAfterBodyDefaultValueTest() throws Exception {
/*
* @testName: tagSupportGetSetValueTest
*
- * @assertion_ids: JSP:JAVADOC:207;JSP:JAVADOC:208
+ * @assertion_ids: PAGES:JAVADOC:207;PAGES:JAVADOC:208
*
* @test_Strategy: Validate the behavior of TagSupport.setValue() and
* TagSupport.getValue().
@@ -301,7 +301,7 @@ public void tagSupportGetSetValueTest() throws Exception {
/*
* @testName: tagSupportGetValuesTest
*
- * @assertion_ids: JSP:JAVADOC:210
+ * @assertion_ids: PAGES:JAVADOC:210
*
* @test_Strategy: Validate the behavior of TagSupport.getValues().
*/
@@ -314,7 +314,7 @@ public void tagSupportGetValuesTest() throws Exception {
/*
* @testName: tagSupportRemoveValueTest
*
- * @assertion_ids: JSP:JAVADOC:209
+ * @assertion_ids: PAGES:JAVADOC:209
*
* @test_Strategy: Validate the behavior of TagSupport.removeValue().
*/
@@ -327,7 +327,7 @@ public void tagSupportRemoveValueTest() throws Exception {
/*
* @testName: tagSupportVariableSynchronizationTest
*
- * @assertion_ids: JSP:JAVADOC:348;JSP:JAVADOC:353;JSP:JAVADOC:371
+ * @assertion_ids: PAGES:JAVADOC:348;PAGES:JAVADOC:353;PAGES:JAVADOC:371
*
* @test_Strategy: Validate scripting variables are synchronized at the proper
* locations by the container.
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagvariableinfo/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagvariableinfo/URLClientIT.java
index 74b648ba..0563d1ff 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagvariableinfo/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/tagvariableinfo/URLClientIT.java
@@ -88,9 +88,9 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: tagVariableInfoGetClassNameTest
*
- * @assertion_ids: JSP:JAVADOC:189
+ * @assertion_ids: PAGES:JAVADOC:189
*
- * @test_Strategy: Validate the JSP container properly parses the specified
+ * @test_Strategy: Validate the Jakarta Pages container properly parses the specified
* TLD as refereneced by the taglib directive and that the TagVariableInfo
* objects created at translation time return the expected values when calling
* getClassName(). A translation error will occur if the test fails.
@@ -108,9 +108,9 @@ public void tagVariableInfoGetClassNameTest() throws Exception {
/*
* @testName: tagVariableInfoGetNameGivenTest
*
- * @assertion_ids: JSP:JAVADOC:187
+ * @assertion_ids: PAGES:JAVADOC:187
*
- * @test_Strategy: Validate the JSP container properly parses the specified
+ * @test_Strategy: Validate the Jakarta Pages container properly parses the specified
* TLD as refereneced by the taglib directive and that the TagVariableInfo
* objects created at translation time return the expected values when calling
* getNameGiven(). A translation error will occur if the test fails.
@@ -128,9 +128,9 @@ public void tagVariableInfoGetNameGivenTest() throws Exception {
/*
* @testName: tagVariableInfoGetNameFromAttributeTest
*
- * @assertion_ids: JSP:JAVADOC:188
+ * @assertion_ids: PAGES:JAVADOC:188
*
- * @test_Strategy: Validate the JSP container properly parses the specified
+ * @test_Strategy: Validate the Jakarta Pages container properly parses the specified
* TLD as refereneced by the taglib directive and that the TagVariableInfo
* objects created at translation time return the expected values when calling
* getNameFromAttribute(). A translation error will occur if the test fails.
@@ -148,9 +148,9 @@ public void tagVariableInfoGetNameFromAttributeTest() throws Exception {
/*
* @testName: tagVariableInfoGetDeclareTest
*
- * @assertion_ids: JSP:JAVADOC:190
+ * @assertion_ids: PAGES:JAVADOC:190
*
- * @test_Strategy: Validate the JSP container properly parses the specified
+ * @test_Strategy: Validate the Jakarta Pages container properly parses the specified
* TLD as refereneced by the taglib directive and that the TagVariableInfo
* objects created at translation time return the expected values when calling
* getDeclare(). A translation error will occur if the test fails.
@@ -168,9 +168,9 @@ public void tagVariableInfoGetDeclareTest() throws Exception {
/*
* @testName: tagVariableInfoGetScopeTest
*
- * @assertion_ids: JSP:JAVADOC:191
+ * @assertion_ids: PAGES:JAVADOC:191
*
- * @test_Strategy: Validate the JSP container properly parses the specified
+ * @test_Strategy: Validate the Jakarta Pages container properly parses the specified
* TLD as refereneced by the taglib directive and that the TagVariableInfo
* objects created at translation time return the expected values when calling
* getScope(). A translation error will occur if the test fails.
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/trycatchfinally/ResultVerifierBean.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/trycatchfinally/ResultVerifierBean.java
index 01237b16..db8d2e77 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/trycatchfinally/ResultVerifierBean.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/trycatchfinally/ResultVerifierBean.java
@@ -30,7 +30,7 @@
public class ResultVerifierBean {
/**
- * JSP PageContext.
+ * Jakarta Pages PageContext.
*/
private PageContext _context = null;
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/trycatchfinally/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/trycatchfinally/URLClientIT.java
index 8ab7aa2e..9647390c 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/trycatchfinally/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/trycatchfinally/URLClientIT.java
@@ -80,7 +80,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: tryCatchFinallyTest
*
- * @assertion_ids: JSP:JAVADOC:339;JSP:JAVADOC:341
+ * @assertion_ids: PAGES:JAVADOC:339;PAGES:JAVADOC:341
*
* @test_Strategy: Validate the behavior of the container when a tag
* implements the TryCatchFinally interface.
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/variableinfo/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/variableinfo/URLClientIT.java
index cacfa67b..4751b9cc 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/variableinfo/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/api/jakarta_servlet/jsp/tagext/variableinfo/URLClientIT.java
@@ -70,7 +70,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: variableInfoCtorTest
*
- * @assertion_ids: JSP:JAVADOC:177
+ * @assertion_ids: PAGES:JAVADOC:177
*
* @test_Strategy: Validate the construction of the VariableInfo object.
*/
@@ -83,7 +83,7 @@ public void variableInfoCtorTest() throws Exception {
/*
* @testName: variableInfoGetVarNameTest
*
- * @assertion_ids: JSP:JAVADOC:178
+ * @assertion_ids: PAGES:JAVADOC:178
*
* @test_Strategy: Validate the behavior of VariableInfo.getVarName().
*/
@@ -96,7 +96,7 @@ public void variableInfoGetVarNameTest() throws Exception {
/*
* @testName: variableInfoGetClassNameTest
*
- * @assertion_ids: JSP:JAVADOC:179
+ * @assertion_ids: PAGES:JAVADOC:179
*
* @test_Strategy: Validate the behavior of VariableInfo.getClassName().
*/
@@ -109,7 +109,7 @@ public void variableInfoGetClassNameTest() throws Exception {
/*
* @testName: variableInfoGetDeclareTest
*
- * @assertion_ids: JSP:JAVADOC:180
+ * @assertion_ids: PAGES:JAVADOC:180
*
* @test_Strategy: Validate the behavior of VariableInfo.getDeclare().
*/
@@ -122,7 +122,7 @@ public void variableInfoGetDeclareTest() throws Exception {
/*
* @testName: variableInfoGetScopeTest
*
- * @assertion_ids: JSP:JAVADOC:181
+ * @assertion_ids: PAGES:JAVADOC:181
*
* @test_Strategy: Validate the behavior of VariableInfo.getScopeTest();
*/
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/common/client/AbstractUrlClient.java b/tck/src/main/java/ee/jakarta/tck/pages/common/client/AbstractUrlClient.java
index 55ad2b78..18f6e65c 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/common/client/AbstractUrlClient.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/common/client/AbstractUrlClient.java
@@ -38,7 +38,7 @@
import java.lang.System.Logger;
/**
- * Base client for JSP tests.
+ * Base client for Jakarta Pages tests.
*/
public abstract class AbstractUrlClient extends BaseUrlClient {
@@ -80,7 +80,7 @@ void logFinishTest(TestInfo testInfo) {
private static final String FAILED = "Test FAILED";
/**
- * The test JSP.
+ * The test page.
*/
private String _jspName = null;
@@ -142,10 +142,10 @@ public void setup() throws Exception {
}
/**
- * Sets the name of the JSP when building the request.
+ * Sets the name of the page when building the request.
*
* @param jsp
- * - JSP name
+ * - page name
*/
public void setTestJsp(String jsp) {
_jspName = jsp;
@@ -217,7 +217,7 @@ private void setStandardProperties(String testValue, WebTestCase testCase) {
}
// A standard test sets consists of a testname
// a request, and a goldenfile. The URI is not used
- // in this case since the JSP's are assumed to be located
+ // in this case since the pages are assumed to be located
// at the top of the contextRoot
StringBuffer sb = new StringBuffer(50);
@@ -241,13 +241,13 @@ private void setStandardProperties(String testValue, WebTestCase testCase) {
}
/**
- * Returns full request based of provided context root, jsp name, and test
+ * Returns full request based of provided context root, page name, and test
* name.
*
* @param contextRoot
* - request context root
* @param jspName
- * - JSP name
+ * - page name
* @param testName
* - test name to execute.
* @return - Absolution URL to invoke the specified test.
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/common/client/ServletAbstractUrlClient.java b/tck/src/main/java/ee/jakarta/tck/pages/common/client/ServletAbstractUrlClient.java
index a9a89e9b..357c162b 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/common/client/ServletAbstractUrlClient.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/common/client/ServletAbstractUrlClient.java
@@ -164,7 +164,7 @@ private void setStandardProperties(String testValue, WebTestCase testCase) {
}
// A standard test sets consists of a testname
// a request, and a goldenfile. The URI is not used
- // in this case since the JSP's are assumed to be located
+ // in this case since the pages are assumed to be located
// at the top of the contextRoot
StringBuffer sb = new StringBuffer(50);
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/common/util/JspTestUtil.java b/tck/src/main/java/ee/jakarta/tck/pages/common/util/JspTestUtil.java
index 570c720d..38d91402 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/common/util/JspTestUtil.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/common/util/JspTestUtil.java
@@ -43,10 +43,10 @@
import jakarta.servlet.jsp.tagext.IterationTag;
import jakarta.servlet.jsp.tagext.Tag;
import jakarta.servlet.jsp.tagext.ValidationMessage;
-//replacing the removed jakarta.servlet.jsp.el.ELException class from JSP 4.0
+//replacing the removed jakarta.servlet.jsp.el.ELException class from Jakarta Pages 4.0
import jakarta.el.ELException;
/**
- * JSP TCK Utility class.
+ * Jakarta Pages TCK Utility class.
*/
public class JspTestUtil {
@@ -75,10 +75,10 @@ private JspTestUtil() {
}
/**
- * Utility method to invoke JSP API Tests.
- *
+ * Utility method to invoke Jakarta Pages API Tests.
+ *
* @param testObject
- * - the JSP test object
+ * - the test object
* @param req
* - the incoming client request
* @param res
@@ -106,7 +106,7 @@ public static void invokeTest(Object testObject, HttpServletRequest req,
/**
* Utility method to handle exceptions from tests in a generic fashion.
- *
+ *
* @param t
* - offending Throwable instance
* @param out
@@ -139,7 +139,7 @@ public static void handleThrowable(Throwable t, JspWriter out,
* If all values are found, true will be returned.
*
* The comparison is performed in a case sensitive manner.
- *
+ *
* @param e
* - Enumeration to validate
* @param values
@@ -184,7 +184,7 @@ public static boolean checkEnumeration(Enumeration e, String[] values) {
/**
* Returns the provided String array in the following format:
* [n1,n2,n...]
- *
+ *
* @param sArray
* - an array of String values
* @return - a String based off the values in the array
@@ -208,7 +208,7 @@ public static String getAsString(String[] sArray) {
/**
* Returns the provided Enumeration as a String in the following format:
* [n1,n2,n...]
- *
+ *
* @param e
* - an Enumeration
* @return - a printable version of the contents of the Enumeration
@@ -219,7 +219,7 @@ public static String getAsString(Enumeration e) {
/**
* Returnes the provides Enumeration as an Array of String Arguments.
- *
+ *
* @param e
* - an Enumeration
* @return - the elements of the Enumeration as an array of Strings
@@ -255,7 +255,7 @@ public static String[] getAsStringArray(String s) {
/**
* Writes the provided message to System.out when the debug is set.
- *
+ *
* @param message
* - the message to write to System.out
*/
@@ -267,7 +267,7 @@ public static void debug(String message) {
/**
* Creates an array of ValidationMessages.
- *
+ *
* @param id
* - the jsp:id
* @param message
@@ -311,7 +311,7 @@ public static String getAsString(Map map) {
/**
* Utility class to get a String version of a Tag return value based on the
* int value, the type, and the method it was returned from.
- *
+ *
* @param method
* - the Tag method returning the int status
* @param type
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/common/xml/common.xml b/tck/src/main/java/ee/jakarta/tck/pages/common/xml/common.xml
deleted file mode 100644
index 129cdf43..00000000
--- a/tck/src/main/java/ee/jakarta/tck/pages/common/xml/common.xml
+++ /dev/null
@@ -1,43 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/signaturetest/JSPSigTestIT.java b/tck/src/main/java/ee/jakarta/tck/pages/signaturetest/JSPSigTestIT.java
index 51f981a5..cfa293b7 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/signaturetest/JSPSigTestIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/signaturetest/JSPSigTestIT.java
@@ -96,8 +96,8 @@ protected String[] getPackages() {
/*
* @testName: signatureTest
*
- * @assertion: A JSP container must implement the required classes and APIs
- * specified in the JSP Specification.
+ * @assertion: A Jakarta Pages container must implement the required classes and APIs
+ * specified in the Jakarta Pages Specification.
*
* @test_Strategy: Using reflection, gather the implementation specific
* classes and APIs. Compare these results with the expected (required)
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/charsequence/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/charsequence/URLClientIT.java
index 7eda64a2..02f96dc4 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/charsequence/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/charsequence/URLClientIT.java
@@ -78,7 +78,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: deferredSyntaxAllowedAsLiteralTrueTemplateTextTest
*
- * @assertion_ids: JSP:SPEC:296
+ * @assertion_ids: PAGES:SPEC:296
*
* @test_Strategy: Invoke a jsp that is a member of a jsp-property-group in
* which the deferred-syntax-allowed-as-literal element is set to true. Verify
@@ -99,7 +99,7 @@ public void deferredSyntaxAllowedAsLiteralTrueTemplateTextTest()
/*
* @testName: deferredSyntaxAllowedAsLiteralFalseTemplateTextTest
*
- * @assertion_ids: JSP:SPEC:295
+ * @assertion_ids: PAGES:SPEC:295
*
* @test_Strategy: Invoke a jsp that is a member of a jsp-property-group in
* which the deferred-syntax-allowed-as-literal element is set to false.
@@ -118,7 +118,7 @@ public void deferredSyntaxAllowedAsLiteralFalseTemplateTextTest()
/*
* @testName: deferredSyntaxAllowedAsLiteralTrueActionTest
*
- * @assertion_ids: JSP:SPEC:296
+ * @assertion_ids: PAGES:SPEC:296
*
* @test_Strategy: Invoke a jsp that is a member of a jsp-property-group in
* which the deferred-syntax-allowed-as-literal element is set to true. Verify
@@ -138,7 +138,7 @@ public void deferredSyntaxAllowedAsLiteralTrueActionTest() throws Exception {
/*
* @testName: deferredSyntaxAllowedAsLiteralFalseActionTest
*
- * @assertion_ids: JSP:SPEC:295
+ * @assertion_ids: PAGES:SPEC:295
*
* @test_Strategy: Invoke a jsp that is a member of a jsp-property-group in
* which the deferred-syntax-allowed-as-literal element is set to false.
@@ -159,7 +159,7 @@ public void deferredSyntaxAllowedAsLiteralFalseActionTest() throws Exception {
/*
* @testName: noDeferredSyntaxAllowedAsLiteralTemplateTextTest
*
- * @assertion_ids: JSP:SPEC:295
+ * @assertion_ids: PAGES:SPEC:295
*
* @test_Strategy: Invoke a jsp that is a member of a jsp-property-group in
* which there is no deferred-syntax-allowed-as-literal element. Verify that
@@ -177,7 +177,7 @@ public void noDeferredSyntaxAllowedAsLiteralTemplateTextTest() throws Exception
/*
* @testName: noDeferredSyntaxAllowedAsLiteralActionTest
*
- * @assertion_ids: JSP:SPEC:295
+ * @assertion_ids: PAGES:SPEC:295
*
* @test_Strategy: Invoke a jsp that is a member of a jsp-property-group in
* which there is no deferred-syntax-allowed-as-literal element. Verify that
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/elevaluation/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/elevaluation/URLClientIT.java
index a6353d70..e6442b9c 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/elevaluation/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/elevaluation/URLClientIT.java
@@ -70,13 +70,13 @@ public static WebArchive createDeployment() {
/*
* @testName: elEvaluationUnspecifiedTest
*
- * @assertion_ids: JSP:SPEC:254
+ * @assertion_ids: PAGES:SPEC:254
*
* @test_Strategy: Validate that if the web application uses a 2.4 deployment
- * descriptor and the jsp-property-group element nor the JSP identified by the
+ * descriptor and the jsp-property-group element nor the page identified by the
* jsp-property-group specifies no EL evaluation information, EL will be
- * evaluated by the container. This validates both JSPs in standard syntax and
- * JSP documents.
+ * evaluated by the container. This validates both pages in standard syntax and
+ * document syntax.
*/
@Test
public void elEvaluationUnspecifiedTest() throws Exception {
@@ -93,13 +93,13 @@ public void elEvaluationUnspecifiedTest() throws Exception {
/*
* @testName: elEvaluationConfigurationFalseTest
*
- * @assertion_ids: JSP:SPEC:142
+ * @assertion_ids: PAGES:SPEC:142
*
* @test_Strategy: Validate that if the web application uses a 2.4 deployment
* descriptor and the jsp-property-group element sets the el-ignored element
- * to false, and the JSP page specifies no special EL handling, that EL
- * expressions will be evaluated. This validates both JSPs in standard syntax
- * and JSP documents.
+ * to false, and the page specifies no special EL handling, that EL
+ * expressions will be evaluated. This validates both pages in standard syntax
+ * and document syntax.
*/
@Test
public void elEvaluationConfigurationFalseTest() throws Exception {
@@ -116,13 +116,13 @@ public void elEvaluationConfigurationFalseTest() throws Exception {
/*
* @testName: elEvaluationConfigurationTrueTest
*
- * @assertion_ids: JSP:SPEC:141
+ * @assertion_ids: PAGES:SPEC:141
*
* @test_Strategy: Validate that if the web application uses a 2.4 deployment
* descriptor and the jsp-property-group element sets the el-ignored element
- * to true, and the JSP page specifies no special EL handling, that EL
- * expressions will not be evaluated. This validates both JSPs in standard
- * syntax and JSP documents.
+ * to true, and the page specifies no special EL handling, that EL
+ * expressions will not be evaluated. This validates both pages in standard
+ * syntax and document syntax.
*/
@Test
public void elEvaluationConfigurationTrueTest() throws Exception {
@@ -139,11 +139,11 @@ public void elEvaluationConfigurationTrueTest() throws Exception {
/*
* @testName: elEvaluationPageDirectiveOverrideTest
*
- * @assertion_ids: JSP:SPEC:255
+ * @assertion_ids: PAGES:SPEC:255
*
* @test_Strategy: Validate that if the web application uses a 2.4 deployment
* descriptor, that the page directive attribute isELIgnored takes precedence
- * over the configuration of the JSP property group.
+ * over the configuration of the Jakarta Pages property group.
*/
@Test
public void elEvaluationPageDirectiveOverrideTest() throws Exception {
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/elevaluation/jsp_config_eleval23_web.xml b/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/elevaluation/jsp_config_eleval23_web.xml
deleted file mode 100644
index 87d6d5b4..00000000
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/elevaluation/jsp_config_eleval23_web.xml
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
-
-
- JspConfigurationElEval23
-
- 5
-
-
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/elevaluation/jsp_config_eleval_web.xml b/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/elevaluation/jsp_config_eleval_web.xml
deleted file mode 100644
index 9c489a3d..00000000
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/elevaluation/jsp_config_eleval_web.xml
+++ /dev/null
@@ -1,82 +0,0 @@
-
-
-
-
- JspConfigurationElEval
-
- 5
-
-
-
-
- Unspecified in configuration and by JSP
- /elunspec/*
-
-
- Set to false in configuration not specified in JSP
- /elconffalse/*
- false
-
-
- Set to true in config not specified in JSP
- /elconftrue/*
- true
-
-
- Set to false in page...overrides config
- /elpagefalse/*
- true
-
-
- Set to true in page...overrides config
- /elpagetrue/*
- false
-
-
-
- Unspecified in configuration and by JSP
- /elunspecx/*
- true
-
-
- Set to false in configuration not specified in JSP
- /elconffalsex/*
- false
- true
-
-
- Set to true in config not specified in JSP
- /elconftruex/*
- true
- true
-
-
- Set to false in page...overrides config
- /elpagefalsex/*
- true
- true
-
-
- Set to true in page...overrides config
- /elpagetruex/*
- false
- true
-
-
-
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/encoding/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/encoding/URLClientIT.java
index 906ce971..63eae083 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/encoding/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/encoding/URLClientIT.java
@@ -73,9 +73,9 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: jspConfigurationEncodingTest
*
- * @assertion_ids: JSP:SPEC:253
+ * @assertion_ids: PAGES:SPEC:253
*
- * @test_Strategy: Validate that if a JSP configuration element specifies an
+ * @test_Strategy: Validate that if a Jakarta Pages configuration element specifies an
* encoding for a group of pages, the encoding is properly set for those pages
* when no encoding is set by the page(s) themselves.
*/
@@ -91,9 +91,9 @@ public void jspConfigurationEncodingTest() throws Exception {
/*
* @testName: jspConfigurationSameEncodingTest
*
- * @assertion_ids: JSP:SPEC:146
+ * @assertion_ids: PAGES:SPEC:146
*
- * @test_Strategy: Validate that if a JSP configuration element specifies an
+ * @test_Strategy: Validate that if a Jakarta Pages configuration element specifies an
* encoding for a group of pages, and the target page specifies the same
* encoding as that of the property group, no translation error occurs and the
* encoding is properly set.
@@ -110,9 +110,9 @@ public void jspConfigurationSameEncodingTest() throws Exception {
/*
* @testName: jspConfigurationDifferentEncodingTest
*
- * @assertion_ids: JSP:SPEC:145
+ * @assertion_ids: PAGES:SPEC:145
*
- * @test_Strategy: Validate that if a JSP configuration element specifies an
+ * @test_Strategy: Validate that if a Jakarta Pages configuration element specifies an
* encoding for a group of pages, and the target page specifies a different
* encoding as that of the property group, a translation error occurs.
*/
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/includes/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/includes/URLClientIT.java
index fc15302d..adfa76e2 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/includes/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/includes/URLClientIT.java
@@ -50,16 +50,16 @@ public URLClientIT() throws Exception {
@Deployment(testable = false)
public static WebArchive createDeployment() throws IOException {
-
+
String packagePath = URLClientIT.class.getPackageName().replace(".", "/");
WebArchive archive = ShrinkWrap.create(WebArchive.class, "jsp_config_includes_web.war");
archive.setWebXML(URLClientIT.class.getClassLoader().getResource(packagePath+"/jsp_config_includes_web.xml"));
- archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/jspf/prelude3.jspf", "jspf/prelude3.jspf");
- archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/jspf/prelude2.jspf", "jspf/prelude2.jspf");
- archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/jspf/prelude1.jspf", "jspf/prelude1.jspf");
- archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/jspf/coda3.jspf", "jspf/coda3.jspf");
- archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/jspf/coda2.jspf", "jspf/coda2.jspf");
- archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/jspf/coda1.jspf", "jspf/coda1.jspf");
+ archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/jspf/prelude3.jspf", "jspf/prelude3.jspf");
+ archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/jspf/prelude2.jspf", "jspf/prelude2.jspf");
+ archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/jspf/prelude1.jspf", "jspf/prelude1.jspf");
+ archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/jspf/coda3.jspf", "jspf/coda3.jspf");
+ archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/jspf/coda2.jspf", "jspf/coda2.jspf");
+ archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/jspf/coda1.jspf", "jspf/coda1.jspf");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/IncludesTest.jsp")), "IncludesTest.jsp");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/two/Includes2Test.jsp")), "two/Includes2Test.jsp");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/three/Includes3Test.jspx")), "three/Includes3Test.jspx");
@@ -77,16 +77,16 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: jspConfigurationIncludesTest
- *
- * @assertion_ids: JSP:SPEC:147;JSP:SPEC:148;JSP:SPEC:149
- *
+ *
+ * @assertion_ids: PAGES:SPEC:147;PAGES:SPEC:148;PAGES:SPEC:149
+ *
* @test_Strategy: Validate the following: - The container properly recognizes
* prelude and coda configuration elements. - Prelude includes are includes at
- * the beginning of the target JSP(s) identified by the url-pattern, and are
+ * the beginning of the target page(s) identified by the url-pattern, and are
* included in the order they appear in the deployment descriptor. - Coda
- * includes are inserted at the end of the target JSP(s) identified by the
+ * includes are inserted at the end of the target page(s) identified by the
* url-pattern, and are included in the order they appear in the deployment
- * descriptor. - Validate with both standard syntax JSPs and JSP documents.
+ * descriptor. - Validate with both standard and document syntax pages.
*/
@Test
public void jspConfigurationIncludesTest() throws Exception {
@@ -98,9 +98,9 @@ public void jspConfigurationIncludesTest() throws Exception {
/*
* @testName: jspConfigurationIncludes2Test
- *
- * @assertion_ids: JSP:SPEC:147;JSP:SPEC:148;JSP:SPEC:149
- *
+ *
+ * @assertion_ids: PAGES:SPEC:147;PAGES:SPEC:148;PAGES:SPEC:149
+ *
* @test_Strategy: Validate the same as above test.
*/
@Test
@@ -114,10 +114,10 @@ public void jspConfigurationIncludes2Test() throws Exception {
/*
* @testName: jspConfigurationIncludes3Test
- *
- * @assertion_ids: JSP:SPEC:147;JSP:SPEC:148;JSP:SPEC:149
- *
- * @test_Strategy: Validate the same as above test. JSP.1.10.4 states that
+ *
+ * @assertion_ids: PAGES:SPEC:147;PAGES:SPEC:148;PAGES:SPEC:149
+ *
+ * @test_Strategy: Validate the same as above test. Pages.1.10.4 states that
* implicit includes can use either the same syntax as the including page, or
* a different syntax.
*/
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/scripting/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/scripting/URLClientIT.java
index 3ef2e9f4..2d8895ef 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/scripting/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/scripting/URLClientIT.java
@@ -29,10 +29,8 @@
import ee.jakarta.tck.pages.common.client.AbstractUrlClient;
import ee.jakarta.tck.pages.common.tags.tck.SimpleTag;
-import org.apache.maven.artifact.versioning.ArtifactVersion;
import org.jboss.arquillian.container.test.api.Deployment;
import org.jboss.arquillian.junit5.ArquillianExtension;
-import org.jboss.shrinkwrap.api.Filters;
import org.jboss.shrinkwrap.api.ShrinkWrap;
import org.jboss.shrinkwrap.api.spec.WebArchive;
import org.junit.jupiter.api.Test;
@@ -51,26 +49,26 @@ public URLClientIT() throws Exception {
@Deployment(testable = false)
public static WebArchive createDeployment() throws IOException {
-
+
String packagePath = URLClientIT.class.getPackageName().replace(".", "/");
WebArchive archive = ShrinkWrap.create(WebArchive.class, "jsp_config_scr_web.war");
archive.addClasses(SimpleTag.class);
archive.setWebXML(URLClientIT.class.getClassLoader().getResource(packagePath+"/jsp_config_scr_web.xml"));
- archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tag.tld", "tag.tld");
-
+ archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tag.tld", "tag.tld");
+
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/scrunspecx/ScriptletTest.jspx")), "scrunspecx/ScriptletTest.jspx");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/scrunspecx/ExpressionTest.jspx")), "scrunspecx/ExpressionTest.jspx");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/scrunspecx/DeclarationTest.jspx")), "scrunspecx/DeclarationTest.jspx");
-
+
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/scrunspec/ScriptletTest.jsp")), "scrunspec/ScriptletTest.jsp");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/scrunspec/ExpressionTest.jsp")), "scrunspec/ExpressionTest.jsp");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/scrunspec/DeclarationTest.jsp")), "scrunspec/DeclarationTest.jsp");
-
+
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/scrtruex/ScriptletTest.jspx")), "scrtruex/ScriptletTest.jspx");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/scrtruex/ExpressionTest.jspx")), "scrtruex/ExpressionTest.jspx");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/scrtruex/AttributeExpressionTest.jspx")), "scrtruex/AttributeExpressionTest.jspx");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/scrtruex/DeclarationTest.jspx")), "scrtruex/DeclarationTest.jspx");
-
+
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/scrunspecx/ScriptletTest.jspx")), "scrunspecx/ScriptletTest.jspx");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/scrunspecx/DeclarationTest.jspx")), "scrunspecx/DeclarationTest.jspx");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/scrunspecx/ExpressionTest.jspx")), "scrunspecx/ExpressionTest.jspx");
@@ -100,13 +98,13 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: jspConfigurationScriptingUnspecifiedTest
- *
- * @assertion_ids: JSP:SPEC:256
- *
+ *
+ * @assertion_ids: PAGES:SPEC:256
+ *
* @test_Strategy: Validate that if scripting-invalid is not specified in the
* target property-group, that a translation error is not generated and the
* scripting elements are evaluated. This test is performed against standard
- * syntax JSP pages as well as JSP documents.
+ * syntax pages as well as documents.
*/
@Test
public void jspConfigurationScriptingUnspecifiedTest() throws Exception {
@@ -138,13 +136,13 @@ public void jspConfigurationScriptingUnspecifiedTest() throws Exception {
/*
* @testName: jspConfigurationScriptingFalseTest
- *
- * @assertion_ids: JSP:SPEC:144
- *
+ *
+ * @assertion_ids: PAGES:SPEC:144
+ *
* @test_Strategy: Validate that if scripting-invalid is set to false in the
* target property-group, that a translation error is not generated and the
* scripting elements are evaluated. This test is performed against standard
- * syntax JSP pages as well as JSP documents.
+ * syntax pages as well as documents.
*/
@Test
public void jspConfigurationScriptingFalseTest() throws Exception {
@@ -180,13 +178,13 @@ public void jspConfigurationScriptingFalseTest() throws Exception {
/*
* @testName: jspConfigurationScriptingTrueTest
- *
- * @assertion_ids: JSP:SPEC:143
- *
+ *
+ * @assertion_ids: PAGES:SPEC:143
+ *
* @test_Strategy: Validate that if scripting-invalid is set to false in the
* target property-group, that a translation error is generated (except in the
- * case of RT expressions). This test is performed against standard syntax JSP
- * pages as well as JSP documents.
+ * case of RT expressions). This test is performed against standard syntax
+ * pages as well as documents.
*/
@Test
public void jspConfigurationScriptingTrueTest() throws Exception {
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/xml/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/xml/URLClientIT.java
index 98fc37fd..b07c258f 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/xml/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/configuration/xml/URLClientIT.java
@@ -50,7 +50,7 @@ public URLClientIT() throws Exception {
@Deployment(testable = false)
public static WebArchive createDeployment() throws IOException {
-
+
String packagePath = URLClientIT.class.getPackageName().replace(".", "/");
WebArchive archive = ShrinkWrap.create(WebArchive.class, "jsp_config_xml_web.war");
archive.setWebXML(URLClientIT.class.getClassLoader().getResource(packagePath+"/jsp_config_xml_web.xml"));
@@ -71,13 +71,13 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: jspConfigurationIsXmlUnspecTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: Validate that if is-xml is not specified for a property
- * group, that the files matched by the url-pattern will not be considered JSP
+ * group, that the files matched by the url-pattern will not be considered
* documents.
- *
+ *
*/
@Test
public void jspConfigurationIsXmlUnspecTest() throws Exception {
@@ -89,11 +89,11 @@ public void jspConfigurationIsXmlUnspecTest() throws Exception {
/*
* @testName: jspConfigurationIsXmlFalseTest
- *
- * @assertion_ids: JSP:SPEC:150.2
- *
+ *
+ * @assertion_ids: PAGES:SPEC:150.2
+ *
* @test_Strategy: Validate that if is-xml is set to false for a property
- * group, that the files matched by the url-pattern will not be considered JSP
+ * group, that the files matched by the url-pattern will not be considered
* documents.
*/
@Test
@@ -106,11 +106,11 @@ public void jspConfigurationIsXmlFalseTest() throws Exception {
/*
* @testName: jspConfigurationIsXmlTrueTest
- *
- * @assertion_ids: JSP:SPEC:150.1
- *
+ *
+ * @assertion_ids: PAGES:SPEC:150.1
+ *
* @test_Strategy: Validate that if is-xml is set to true for a property
- * group, that the files matched by the url-pattern will be considered JSP
+ * group, that the files matched by the url-pattern will be considered
* documents.
*/
@Test
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/attribute/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/attribute/URLClientIT.java
index aa004dbe..d5721522 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/attribute/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/attribute/URLClientIT.java
@@ -99,7 +99,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: jspAttributeFragmentTest
*
- * @assertion_ids: JSP:SPEC:168.3;JSP:SPEC:168.4
+ * @assertion_ids: PAGES:SPEC:168.3;PAGES:SPEC:168.4
*
* @test_Strategy: Validate that container passes an instance of JspFragment
* when the target attribute is being set by jsp:attribute. This test will
@@ -117,7 +117,7 @@ public void jspAttributeFragmentTest() throws Exception {
/*
* @testName: jspAttributeUsageContextTest
*
- * @assertion_ids: JSP:SPEC:168.2;JSP:SPEC:168.11
+ * @assertion_ids: PAGES:SPEC:168.2;PAGES:SPEC:168.11
*
* @test_Strategy: Validate a translation-time error occurs for the following
* use cases: - jsp:attribute is not a child of a standard or custom action. -
@@ -144,7 +144,7 @@ public void jspAttributeUsageContextTest() throws Exception {
/*
* @testName: jspAttributeFragmentNonScriptingBodyTest
*
- * @assertion_ids: JSP:SPEC:168.5
+ * @assertion_ids: PAGES:SPEC:168.5
*
* @test_Strategy: Validate a translation error occurs if providing an
* attribute value using jsp:attribute to an attribute accepting JspFragment
@@ -182,7 +182,7 @@ public void jspAttributeFragmentNonScriptingBodyTest() throws Exception {
/*
* @testName: jspAttributeDynamicAttributesTest
*
- * @assertion_ids: JSP:SPEC:168.6
+ * @assertion_ids: PAGES:SPEC:168.6
*
* @test_Strategy: Validate that dynamic attribute values provided via
* jsp:attribute are provided to the tag handler as java.lang.String objects.
@@ -204,7 +204,7 @@ public void jspAttributeDynamicAttributesTest() throws Exception {
/*
* @testName: jspAttributeRtExprTest
*
- * @assertion_ids: JSP:SPEC:168.7
+ * @assertion_ids: PAGES:SPEC:168.7
*
* @test_Strategy: Validate that if a tag handler (either Classic or Simple)
* accepts RT expressions and the attribute values are provided via
@@ -224,10 +224,10 @@ public void jspAttributeRtExprTest() throws Exception {
/*
* @testName: jspAttributeElementInteractionTest
*
- * @assertion_ids: JSP:SPEC:168.9
+ * @assertion_ids: PAGES:SPEC:168.9
*
* @test_Strategy: Validate that when a jsp:attribute element is nexted within
- * a jsp:element element within a JSP document, that the element is
+ * a jsp:element element within a Jakarta Pages document, that the element is
* constructed with element name being the value of the name attribute of
* jsp:attribute and the body of the element being the body of the
* jsp:attribute element.
@@ -245,7 +245,7 @@ public void jspAttributeElementInteractionTest() throws Exception {
/*
* @testName: jspAttributeTrimTest
*
- * @assertion_ids: JSP:SPEC:168.13;JSP:SPEC:168.14;JSP:SPEC:168.15
+ * @assertion_ids: PAGES:SPEC:168.13;PAGES:SPEC:168.14;PAGES:SPEC:168.15
*
* @test_Strategy: Validate the behavior of the trim attribute when set to
* true or false, or when not specified when handling static values at
@@ -263,7 +263,7 @@ public void jspAttributeTrimTest() throws Exception {
/*
* @testName: jspAttributeDuplicatedAttributeTest
*
- * @assertion_ids: JSP:SPEC:168.1.2
+ * @assertion_ids: PAGES:SPEC:168.1.2
*
* @test_Strategy: Validate that if an attribute is already specified for an
* action (using the xml style) and a jsp:attribute action is used to define
@@ -280,7 +280,7 @@ public void jspAttributeDuplicatedAttributeTest() throws Exception {
/*
* @testName: jspAttributeQNameTest
*
- * @assertion_ids: JSP:SPEC:168.1.4;JSP:SPEC:168.12
+ * @assertion_ids: PAGES:SPEC:168.1.4;PAGES:SPEC:168.12
*
* @test_Strategy: Validate the following: - qname attribute names can be
* provided to the name attribute of jsp:attribute an work the same as a
@@ -312,7 +312,7 @@ public void jspAttributeQNameTest() throws Exception {
/*
* @testName: jspAttributeEmptyBodyTest
*
- * @assertion_ids: JSP:SPEC:168.10
+ * @assertion_ids: PAGES:SPEC:168.10
*
* @test_Strategy: Validate that if the body of jsp:attribute is empty, it
* sets the value of the attribute to "".
@@ -328,7 +328,7 @@ public void jspAttributeEmptyBodyTest() throws Exception {
/*
* @testName: jspAttributeNoAttributeFoundTest
*
- * @assertion_ids: JSP:SPEC:168.1.1
+ * @assertion_ids: PAGES:SPEC:168.1.1
*
* @test_Strategy: Validate that if jsp:attribute specifies an attribute of an
* action that does not exist, and that action does not accept dynamic
@@ -345,7 +345,7 @@ public void jspAttributeNoAttributeFoundTest() throws Exception {
/*
* @testName: jspAttributeNameRequiredAttributeTest
*
- * @assertion_ids: JSP:SPEC:168.1.3
+ * @assertion_ids: PAGES:SPEC:168.1.3
*
* @test_Strategy: Validate the name attribute is indeed a required attribute
* of the jsp:attribute standard action by omitting it and checking for a
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/body/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/body/URLClientIT.java
index ca31f4ac..e1471d20 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/body/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/body/URLClientIT.java
@@ -82,7 +82,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: jspBodyTest
*
- * @assertion_ids: JSP:SPEC:248
+ * @assertion_ids: PAGES:SPEC:248
*
* @test_Strategy: Validate that the body of an action is properly delivered
* to a custom action when provided through jsp:body.
@@ -99,7 +99,7 @@ public void jspBodyTest() throws Exception {
/*
* @testName: jspBodyUsageContextTest
*
- * @assertion_ids: JSP:SPEC:248.2;JSP:SPEC:248.3
+ * @assertion_ids: PAGES:SPEC:248.2;PAGES:SPEC:248.3
*
* @test_Strategy: Validate that translation-time errors will occur when
* jsp:body is used in an incorrected context. - Not nested within a standard
@@ -121,7 +121,7 @@ public void jspBodyUsageContextTest() throws Exception {
/*
* @testName: jspBodyEmptyBodyTest
*
- * @assertion_ids: JSP:SPEC:248.1
+ * @assertion_ids: PAGES:SPEC:248.1
*
* @test_Strategy: Verify that following empty body semantics involving
* jsp:body: - If an action has one or more jsp:attribute elements and no
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/declaration/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/declaration/URLClientIT.java
index b3027f69..5bbafe92 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/declaration/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/declaration/URLClientIT.java
@@ -30,7 +30,6 @@
import org.jboss.arquillian.container.test.api.Deployment;
import org.jboss.arquillian.junit5.ArquillianExtension;
-import org.jboss.shrinkwrap.api.Filters;
import org.jboss.shrinkwrap.api.ShrinkWrap;
import org.jboss.shrinkwrap.api.spec.WebArchive;
import org.junit.jupiter.api.Test;
@@ -51,14 +50,14 @@ public URLClientIT() throws Exception {
@Deployment(testable = false)
public static WebArchive createDeployment() throws IOException {
-
+
String packagePath = URLClientIT.class.getPackageName().replace(".", "/");
WebArchive archive = ShrinkWrap.create(WebArchive.class, "jsp_core_act_decl_web.war");
// archive.addPackages(true, Filters.exclude(URLClient.class),
// URLClient.class.getPackageName());
archive.setWebXML(URLClientIT.class.getClassLoader().getResource(packagePath+"/jsp_core_act_decl_web.xml"));
- archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/JspDeclarationTag2.tagx", "tags/JspDeclarationTag2.tagx");
- archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/JspDeclarationTag1.tag", "tags/JspDeclarationTag1.tag");
+ archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/JspDeclarationTag2.tagx", "tags/JspDeclarationTag2.tagx");
+ archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/JspDeclarationTag1.tag", "tags/JspDeclarationTag1.tag");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/JspDeclarationUsageContextTest1.jsp")), "JspDeclarationUsageContextTest1.jsp");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/JspDeclarationUsageContextTest2.jspx")), "JspDeclarationUsageContextTest2.jspx");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/JspDeclarationUsageContextTest3.jsp")), "JspDeclarationUsageContextTest3.jsp");
@@ -77,11 +76,11 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: jspDeclarationUsageContextTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: Validate the container's acceptance of the use of
- * jsp:declaration in standard JSP pages, JSP documents and Tag files in both
+ * jsp:declaration in standard pages, documents and Tag files in both
* standard and XML syntax.
*/
@Test
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/expression/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/expression/URLClientIT.java
index 7013b36b..bffd6ebd 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/expression/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/expression/URLClientIT.java
@@ -30,7 +30,6 @@
import org.jboss.arquillian.container.test.api.Deployment;
import org.jboss.arquillian.junit5.ArquillianExtension;
-import org.jboss.shrinkwrap.api.Filters;
import org.jboss.shrinkwrap.api.ShrinkWrap;
import org.jboss.shrinkwrap.api.spec.WebArchive;
import org.junit.jupiter.api.Test;
@@ -51,12 +50,12 @@ public URLClientIT() throws Exception {
@Deployment(testable = false)
public static WebArchive createDeployment() throws IOException {
-
+
String packagePath = URLClientIT.class.getPackageName().replace(".", "/");
WebArchive archive = ShrinkWrap.create(WebArchive.class, "jsp_core_act_expr_web.war");
archive.setWebXML(URLClientIT.class.getClassLoader().getResource(packagePath+"/jsp_core_act_expr_web.xml"));
- archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/JspExpressionTag1.tag", "tags/JspExpressionTag1.tag");
- archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/JspExpressionTag2.tagx", "tags/JspExpressionTag2.tagx");
+ archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/JspExpressionTag1.tag", "tags/JspExpressionTag1.tag");
+ archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/JspExpressionTag2.tagx", "tags/JspExpressionTag2.tagx");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/JspExpressionUsageContextTest1.jsp")), "JspExpressionUsageContextTest1.jsp");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/JspExpressionUsageContextTest2.jspx")), "JspExpressionUsageContextTest2.jspx");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/JspExpressionUsageContextTest3.jsp")), "JspExpressionUsageContextTest3.jsp");
@@ -75,11 +74,11 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: jspExpressionUsageContextTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: Validate the container's acceptance of the use of
- * jsp:expression in standard JSP pages, JSP documents and Tag files in both
+ * jsp:expression in standard pages, documents and Tag files in both
* standard and XML syntax.
*/
@Test
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/forward/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/forward/URLClientIT.java
index ee8bec2c..e53d0bdd 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/forward/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/forward/URLClientIT.java
@@ -22,8 +22,6 @@
-import java.io.File;
-import java.io.FileInputStream;
import java.io.IOException;
import java.io.InputStream;
@@ -31,7 +29,6 @@
import org.jboss.arquillian.container.test.api.Deployment;
import org.jboss.arquillian.junit5.ArquillianExtension;
-import org.jboss.shrinkwrap.api.Filters;
import org.jboss.shrinkwrap.api.ShrinkWrap;
import org.jboss.shrinkwrap.api.spec.WebArchive;
import org.junit.jupiter.api.Test;
@@ -56,7 +53,7 @@ public URLClientIT() throws Exception {
@Deployment(testable = false)
public static WebArchive createDeployment() throws IOException {
-
+
WebArchive archive = ShrinkWrap.create(WebArchive.class, "jsp_coresyntx_act_forward_web.war");
archive.setWebXML(URLClientIT.class.getClassLoader().getResource(packagePath+"/jsp_coresyntx_act_forward_web.xml"));
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/unbufferedWriteForwardTest.jsp")), "unbufferedWriteForwardTest.jsp");
@@ -72,7 +69,7 @@ public static WebArchive createDeployment() throws IOException {
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/flushedBufferForwardTest1.jsp")), "flushedBufferForwardTest1.jsp");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/flushedBufferForwardTest.jsp")), "flushedBufferForwardTest.jsp");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/flushedBufferForwardTest_error.jsp")), "flushedBufferForwardTest_error.jsp");
-
+
return archive;
}
@@ -86,10 +83,10 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: positiveForwardCtxRelativeTest
- *
- * @assertion_ids: JSP:SPEC:165.1
- *
- * @test_Strategy: Validate that jsp:forward can forward a request to a JSP
+ *
+ * @assertion_ids: PAGES:SPEC:165.1
+ *
+ * @test_Strategy: Validate that jsp:forward can forward a request to a
* page within the same context using a page relative-path. PENDING Merege
* existing forward tests
*/
@@ -104,9 +101,9 @@ public void positiveForwardCtxRelativeTest() throws Exception {
/*
* @testName: positiveForwardCtxRelativeHtmlTest
- *
- * @assertion_ids: JSP:SPEC:165.1
- *
+ *
+ * @assertion_ids: PAGES:SPEC:165.1
+ *
* @test_Strategy: Validate that jsp:forward can forward a request to a static
* resource within the same context using a page-relative path.
*/
@@ -121,10 +118,10 @@ public void positiveForwardCtxRelativeHtmlTest() throws Exception {
/*
* @testName: positiveForwardPageRelativeTest
- *
- * @assertion_ids: JSP:SPEC:165.1
- *
- * @test_Strategy: Validate that jsp:forward can forward a request to a JSP
+ *
+ * @assertion_ids: PAGES:SPEC:165.1
+ *
+ * @test_Strategy: Validate that jsp:forward can forward a request to a
* page within the same context using a page-relative path.
*/
@@ -138,9 +135,9 @@ public void positiveForwardPageRelativeTest() throws Exception {
/*
* @testName: positiveForwardPageRelativeHtmlTest
- *
- * @assertion_ids: JSP:SPEC:165.1
- *
+ *
+ * @assertion_ids: PAGES:SPEC:165.1
+ *
* @test_Strategy: Validate that jsp:forward can forward a request to a static
* resource within the same context using a page-relative path.
*/
@@ -155,9 +152,9 @@ public void positiveForwardPageRelativeHtmlTest() throws Exception {
/*
* @testName: positiveRequestAttrCtxRelativeTest
- *
- * @assertion_ids: JSP:SPEC:165.8
- *
+ *
+ * @assertion_ids: PAGES:SPEC:165.8
+ *
* @test_Strategy: Validate that jsp:forward can properly accept a
* request-time attribute containing a context-relative path value.
*/
@@ -172,9 +169,9 @@ public void positiveRequestAttrCtxRelativeTest() throws Exception {
/*
* @testName: positiveRequestAttrPageRelativeTest
- *
- * @assertion_ids: JSP:SPEC:165.8
- *
+ *
+ * @assertion_ids: PAGES:SPEC:165.8
+ *
* @test_Strategy: Validate that jsp:forward can properly accept a
* request-time attribute containing a page-relative path value.
*/
@@ -189,9 +186,9 @@ public void positiveRequestAttrPageRelativeTest() throws Exception {
/*
* @testName: unbufferedWriteForwardTest
- *
- * @assertion_ids: JSP:SPEC:165.5
- *
+ *
+ * @assertion_ids: PAGES:SPEC:165.5
+ *
* @test_Strategy:If the page output was unbuffered and anything has been
* written to it, an attempt to forward the request will result in an
* IllegalStateException.
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/getproperty/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/getproperty/URLClientIT.java
index 18bcc437..a58a56d1 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/getproperty/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/getproperty/URLClientIT.java
@@ -76,7 +76,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: positiveGetPropsTest
*
- * @assertion_ids: JSP:SPEC:163.1;JSP:SPEC:163.2;JSP:SPEC:163.4
+ * @assertion_ids: PAGES:SPEC:163.1;PAGES:SPEC:163.2;PAGES:SPEC:163.4
*
* @test_Strategy: Create a bean using jsp:useBean tag, use jsp:getProperty to
* access and validate the property.
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/include/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/include/URLClientIT.java
index 33fa62e6..9b567468 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/include/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/include/URLClientIT.java
@@ -28,7 +28,6 @@
import org.jboss.arquillian.container.test.api.Deployment;
import org.jboss.arquillian.junit5.ArquillianExtension;
-import org.jboss.shrinkwrap.api.Filters;
import org.jboss.shrinkwrap.api.ShrinkWrap;
import org.jboss.shrinkwrap.api.spec.WebArchive;
import org.junit.jupiter.api.Test;
@@ -54,7 +53,7 @@ public URLClientIT() throws Exception {
@Deployment(testable = false)
public static WebArchive createDeployment() throws IOException {
-
+
WebArchive archive = ShrinkWrap.create(WebArchive.class, "jsp_coresyntx_act_include_web.war");
archive.setWebXML(URLClientIT.class.getClassLoader().getResource(packagePath+"/jsp_coresyntx_act_include_web.xml"));
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/staticStatic_A.jsp")), "staticStatic_A.jsp");
@@ -95,12 +94,12 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: positiveIncludeCtxRelativeTest
- *
+ *
* @assertion_ids: PENDING
- *
- * @test_Strategy: Include content, using a context-relative path, from JSP
- * page into the current JSP page.
- *
+ *
+ * @test_Strategy: Include content, using a context-relative path, from a
+ * Jakarta Pages page into the current page.
+ *
* jsp:include provides for the inclusion of dynamic resources, within the
* same context, using a context-relative path. JavaServer Pages Specification
* v1.2, Sec. 4.4
@@ -116,11 +115,11 @@ public void positiveIncludeCtxRelativeTest() throws Exception {
/*
* @testName: positiveIncludeCtxRelativeHtmlTest
- *
- * @assertion_ids: JSP:SPEC:164.1
- *
+ *
+ * @assertion_ids: PAGES:SPEC:164.1
+ *
* @test_Strategy: Include content, using a context-relative path, from a
- * static HTML page into the current JSP page. PENDING Merge existing tests
+ * static HTML page into the current page. PENDING Merge existing tests
* into one test.
*/
@@ -134,11 +133,11 @@ public void positiveIncludeCtxRelativeHtmlTest() throws Exception {
/*
* @testName: positiveIncludePageRelativeTest
- *
- * @assertion_ids: JSP:SPEC:164.1
- *
- * @test_Strategy: Include content, using a page-relative path, from a JSP
- * page into the current JSP page.
+ *
+ * @assertion_ids: PAGES:SPEC:164.1
+ *
+ * @test_Strategy: Include content, using a page-relative path, from a Jakarta Pages
+ * page into the current page.
*/
@Test
public void positiveIncludePageRelativeTest() throws Exception {
@@ -150,9 +149,9 @@ public void positiveIncludePageRelativeTest() throws Exception {
/*
* @testName: positiveRequestAttrCtxRelativeTest
- *
- * @assertion_ids: JSP:SPEC:164.1;JSP:SPEC:164.9
- *
+ *
+ * @assertion_ids: PAGES:SPEC:164.1;PAGES:SPEC:164.9
+ *
* @test_Strategy: Validate the page attribute of jsp:include can correctly
* accept request-time attribute values which contain context-relative paths.
*/
@@ -167,9 +166,9 @@ public void positiveRequestAttrCtxRelativeTest() throws Exception {
/*
* @testName: positiveRequestAttrPageRelativeTest
- *
- * @assertion_ids: JSP:SPEC:164.1
- *
+ *
+ * @assertion_ids: PAGES:SPEC:164.1
+ *
* @test_Strategy: Validate the page attribute of jsp:include can correctly
* accept request-time attribute values which contain page-relative paths.
*/
@@ -184,11 +183,11 @@ public void positiveRequestAttrPageRelativeTest() throws Exception {
/*
* @testName: positiveIncludePageRelative2Test
- *
- * @assertion_ids: JSP:SPEC:164.1
- *
- * @test_Strategy: Include content, using a page-relative path, from a JSP
- * page in a different dir into the current JSP page, with a jsp-config
+ *
+ * @assertion_ids: PAGES:SPEC:164.1
+ *
+ * @test_Strategy: Include content, using a page-relative path, from a Jakarta Pages
+ * page in a different dir into the current Jakarta Pages page, with a jsp-config
* url-pattern in web.xml
*/
@Test
@@ -201,14 +200,14 @@ public void positiveIncludePageRelative2Test() throws Exception {
/*
* @testName: positiveIncludeForwardTest
- *
- * @assertion_ids: JSP:SPEC:164.1
- *
+ *
+ * @assertion_ids: PAGES:SPEC:164.1
+ *
* @test_Strategy: Include a jsp, which forwards to a html file Only the
* output from the forwarded target should be sent to client, because the test
- * jsp and included jsp shared the same out (JSP 5.4), and a forwarding clears
+ * jsp and included jsp shared the same out (Pages 5.4), and a forwarding clears
* the response buffer (SVR 8.4).
- *
+ *
*/
@Test
public void positiveIncludeForwardTest() throws Exception {
@@ -220,9 +219,9 @@ public void positiveIncludeForwardTest() throws Exception {
/*
* @testName: includeMappedServletTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: set page attribute to a mapped servlet.
*/
@@ -238,10 +237,10 @@ public void includeMappedServletTest() throws Exception {
/*
* @testName: staticStaticTest
- *
+ *
* @assertion_ids: PENDING
- *
- * @test_Strategy:complex set of inclusions in JSP.5.4
+ *
+ * @test_Strategy:complex set of inclusions in Pages.5.4
*/
@Test
@@ -254,10 +253,10 @@ public void staticStaticTest() throws Exception {
/*
* @testName: dynamicDynamicTest
- *
+ *
* @assertion_ids: PENDING
- *
- * @test_Strategy: complex set of inclusions in JSP.5.4
+ *
+ * @test_Strategy: complex set of inclusions in Pages.5.4
*/
@Test
@@ -270,10 +269,10 @@ public void dynamicDynamicTest() throws Exception {
/*
* @testName: dynamicStaticTest
- *
+ *
* @assertion_ids: PENDING
- *
- * @test_Strategy: complex set of inclusions in JSP.5.4
+ *
+ * @test_Strategy: complex set of inclusions in Pages.5.4
*/
@Test
@@ -286,10 +285,10 @@ public void dynamicStaticTest() throws Exception {
/*
* @testName: staticDynamicTest
- *
+ *
* @assertion_ids: PENDING
- *
- * @test_Strategy: complex set of inclusions in JSP.5.4
+ *
+ * @test_Strategy: complex set of inclusions in Pages.5.4
*/
@Test
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/invoke/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/invoke/URLClientIT.java
index 98beb06e..b5df1fad 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/invoke/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/invoke/URLClientIT.java
@@ -31,7 +31,6 @@
import org.jboss.arquillian.container.test.api.Deployment;
import org.jboss.arquillian.junit5.ArquillianExtension;
-import org.jboss.shrinkwrap.api.Filters;
import org.jboss.shrinkwrap.api.ShrinkWrap;
import org.jboss.shrinkwrap.api.spec.WebArchive;
import org.junit.jupiter.api.Test;
@@ -52,7 +51,7 @@ public URLClientIT() throws Exception {
@Deployment(testable = false)
public static WebArchive createDeployment() throws IOException {
-
+
String packagePath = URLClientIT.class.getPackageName().replace(".", "/");
WebArchive archive = ShrinkWrap.create(WebArchive.class, "jsp_core_act_invoke_web.war");
archive.addClasses(JspTestUtil.class);
@@ -107,11 +106,11 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: jspInvokeUsageContextTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: Validate the following usage contexts of jsp:invoke: -
- * jsp:invoke present in a JSP or JSP document is a translation error. -
+ * jsp:invoke present in a page or a document is a translation error. -
* jsp:invoke is valid within a tag file.
*/
@Test
@@ -132,9 +131,9 @@ public void jspInvokeUsageContextTest() throws Exception {
/*
* @testName: jspInvokeVarTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: Validate the behavior of jsp:invoke when the var attribute
* is specified. The tag file should export the result of the invocation to a
* request-scoped variable. The type and value of the exported variable will
@@ -151,9 +150,9 @@ public void jspInvokeVarTest() throws Exception {
/*
* @testName: jspInvokeVarReaderTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: Validate the behavior of jsp:invoke when the varReader
* attribute is specified. The tag file should export the result of the
* invocation to a request-scoped variable. The type and value of the exported
@@ -171,9 +170,9 @@ public void jspInvokeVarReaderTest() throws Exception {
/*
* @testName: jspInvokeScopeTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: Validate the behavior of jsp:invoke when the scope
* attribute is and is not specified. If not specified, the result of the
* invocation should be in the page scope of the tag file. If the scope is
@@ -194,9 +193,9 @@ public void jspInvokeScopeTest() throws Exception {
/*
* @testName: jspInvokeVarVarReaderTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: Validate that if both var and varReader are specified
* within one particular jsp:invoke action, a translation- time error is
* raised.
@@ -211,9 +210,9 @@ public void jspInvokeVarVarReaderTest() throws Exception {
/*
* @testName: jspInvokeNoVarVarReaderTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: Validate that if the scope attribute of jsp:invoke is
* specified but neither the var nor varReader are specified, a
* translation-time error is raised.
@@ -228,9 +227,9 @@ public void jspInvokeNoVarVarReaderTest() throws Exception {
/*
* @testName: jspInvokeNotInSessionTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: Validate that jsp:invoke will cause an
* IllegalStateException to be raised if the jsp:invoke action tries to export
* a result into the session scope where the calling page does not participate
@@ -247,9 +246,9 @@ public void jspInvokeNotInSessionTest() throws Exception {
/*
* @testName: jspInvokeJspAttributeTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: Validate the attributes of jspInvoke can all be specified
* using the jsp:attribute action.
*/
@@ -264,9 +263,9 @@ public void jspInvokeJspAttributeTest() throws Exception {
/*
* @testName: jspInvokeInvalidScopeTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: Validate that a translation-time error is generated if the
* scope attribute of jsp:invoke is provided an invalid value (i.e. not
* 'page', 'request', 'session', or 'application').
@@ -297,9 +296,9 @@ public void jspInvokeInvalidScopeTest() throws Exception {
/*
* @testName: jspInvokeFragmentReqAttributeTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: Validate that the 'fragment' attribute of jsp:invoke is
* indeed required by the container. Validate by calling jsp:invoke without
* the attribute and look for a translation- time error.
@@ -314,9 +313,9 @@ public void jspInvokeFragmentReqAttributeTest() throws Exception {
/*
* @testName: jspInvokeNonEmptyBodyTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: Validate a translation-time error is raised if the
* jsp:invoke action has a non-empty body.
*/
@@ -330,9 +329,9 @@ public void jspInvokeNonEmptyBodyTest() throws Exception {
/*
* @testName: jspFragmentNullTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: If the fragment identified by the given name is null, will
* behave as though a fragment was passed in that produces no output.
*/
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/output/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/output/URLClientIT.java
index 5b4ec1c6..a66cf34a 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/output/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/output/URLClientIT.java
@@ -31,7 +31,6 @@
import org.jboss.arquillian.container.test.api.Deployment;
import org.jboss.arquillian.junit5.ArquillianExtension;
-import org.jboss.shrinkwrap.api.Filters;
import org.jboss.shrinkwrap.api.ShrinkWrap;
import org.jboss.shrinkwrap.api.spec.WebArchive;
import org.junit.jupiter.api.Test;
@@ -54,7 +53,7 @@ public URLClientIT() throws Exception {
@Deployment(testable = false)
public static WebArchive createDeployment() throws IOException {
-
+
String packagePath = URLClientIT.class.getPackageName().replace(".", "/");
WebArchive archive = ShrinkWrap.create(WebArchive.class, "jsp_core_act_output_web.war");
archive.addClasses(JspTestUtil.class);
@@ -85,15 +84,15 @@ public static WebArchive createDeployment() throws IOException {
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/doctypeSystemTest.jspx")), "doctypeSystemTest.jspx");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/doctypeSystemPublicTest.jspx")), "doctypeSystemPublicTest.jspx");
- archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/JspOutputUsageXMLTag.tagx", "tags/JspOutputUsageXMLTag.tagx");
- archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/JspOutputUsageTag.tag", "tags/JspOutputUsageTag.tag");
- archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/JspOutputOmitDeclYesTag.tagx", "tags/JspOutputOmitDeclYesTag.tagx");
- archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/JspOutputOmitDeclTrueTag.tagx", "tags/JspOutputOmitDeclTrueTag.tagx");
- archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/JspOutputOmitDeclNoTag.tagx", "tags/JspOutputOmitDeclNoTag.tagx");
- archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/JspOutputOmitDeclFalseTag.tagx", "tags/JspOutputOmitDeclFalseTag.tagx");
- archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/JspOutputDefaultTag.tagx", "tags/JspOutputDefaultTag.tagx");
- archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/JspOutputBodyTag.tagx", "tags/JspOutputBodyTag.tagx");
-
+ archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/JspOutputUsageXMLTag.tagx", "tags/JspOutputUsageXMLTag.tagx");
+ archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/JspOutputUsageTag.tag", "tags/JspOutputUsageTag.tag");
+ archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/JspOutputOmitDeclYesTag.tagx", "tags/JspOutputOmitDeclYesTag.tagx");
+ archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/JspOutputOmitDeclTrueTag.tagx", "tags/JspOutputOmitDeclTrueTag.tagx");
+ archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/JspOutputOmitDeclNoTag.tagx", "tags/JspOutputOmitDeclNoTag.tagx");
+ archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/JspOutputOmitDeclFalseTag.tagx", "tags/JspOutputOmitDeclFalseTag.tagx");
+ archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/JspOutputDefaultTag.tagx", "tags/JspOutputDefaultTag.tagx");
+ archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/JspOutputBodyTag.tagx", "tags/JspOutputBodyTag.tagx");
+
return archive;
}
@@ -107,12 +106,12 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: jspOutputUsageContextTest
- *
+ *
* @assertion_ids: PENDING
- *
- * @test_Strategy: Validate that jsp:output can be used within JSP documents
+ *
+ * @test_Strategy: Validate that jsp:output can be used within Jakarta Pages documents
* and Tag files in XML syntax and that a translation-time error is raised if
- * used within the context of a standard syntax JSP or Tag file.
+ * used within the context of a standard syntax page or Tag file.
*/
@Test
public void jspOutputUsageContextTest() throws Exception {
@@ -138,9 +137,9 @@ public void jspOutputUsageContextTest() throws Exception {
/*
* @testName: jspOutputOmitDeclValidValuesTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: Validate the valid values for the omit-xml-declaration are
* 'true', 'false', 'yes', and 'no'. If the attribute values are 'false' or
* 'no', then the xml declaration will be generated. If 'true' or 'yes' no
@@ -188,10 +187,10 @@ public void jspOutputOmitDeclValidValuesTest() throws Exception {
/*
* @testName: jspOutputJspRootOmitDeclDefaultTest
- *
+ *
* @assertion_ids: PENDING
- *
- * @test_Strategy: Validate that if a JSP document contains jsp:root, and a
+ *
+ * @test_Strategy: Validate that if a Jakarta Pages document contains jsp:root, and a
* jsp:output action is present without the omit-xml-declaration attribute,
* the xml declaration will not be generated.
*/
@@ -205,10 +204,10 @@ public void jspOutputJspRootOmitDeclDefaultTest() throws Exception {
/*
* @testName: jspOutputOmitDeclDefaultTest
- *
+ *
* @assertion_ids: PENDING
- *
- * @test_Strategy: Validate that if jsp:output is present in a JSP document
+ *
+ * @test_Strategy: Validate that if jsp:output is present in a Jakarta Pages document
* without a jsp:root element, and the omit-xml-declaration attribute is not
* present, the default behavior is that an xml declaration is generated.
*/
@@ -223,9 +222,9 @@ public void jspOutputOmitDeclDefaultTest() throws Exception {
/*
* @testName: jspOutputOmitDeclDefaultTagTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: Validate that if jsp:output is present in a Tag file in XML
* syntax, and the omit-xml-declaration attribute is not present, the default
* behavior will be the generation of an XML declaration.
@@ -241,9 +240,9 @@ public void jspOutputOmitDeclDefaultTagTest() throws Exception {
/*
* @testName: jspOutputBodyTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: Validate that a translation error occurs if the body of
* jsp:output is not empty.
*/
@@ -261,9 +260,9 @@ public void jspOutputBodyTest() throws Exception {
/*
* @testName: simpleDefaultTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: use a jsp document without jsp:output. response encoding is
* not set so use default for jsp document
*/
@@ -280,9 +279,9 @@ public void simpleDefaultTest() throws Exception {
/*
* @testName: doctypeSystemTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: A DOCTYPE must be automatically output if and only if the
* doctype-system element appears in the translation unit as part of a
* action. The format of the DOCTYPE: action. The format of the DOCTYPE: byte char
@@ -295,7 +295,7 @@ public void positiveSetIndexedPropTest() throws Exception {
/*
* @testName: positiveSetIntObjTest
*
- * @assertion_ids: JSP:SPEC:91;JSP:SPEC:162.10
+ * @assertion_ids: PAGES:SPEC:91;PAGES:SPEC:162.10
*
* @test_Strategy: Using jsp:useBean, create a new bean instance and set an
* Integer property of the bean using a String constant. PENDING Merge with
@@ -313,7 +313,7 @@ public void positiveSetIntObjTest() throws Exception {
/*
* @testName: positiveSetIntPrimTest
*
- * @assertion_ids: JSP:SPEC:91
+ * @assertion_ids: PAGES:SPEC:91
*
* @test_Strategy: Using jsp:useBean, create a new bean instance and set an
* int property of the bean using a String constant.
@@ -330,7 +330,7 @@ public void positiveSetIntPrimTest() throws Exception {
/*
* @testName: positiveSetLongObjTest
*
- * @assertion_ids: JSP:SPEC:93;JSP:SPEC:162.10
+ * @assertion_ids: PAGES:SPEC:93;PAGES:SPEC:162.10
*
* @test_Strategy: Using jsp:useBean, create a new bean instance and set an
* Long property of the bean using a String constant.
@@ -347,7 +347,7 @@ public void positiveSetLongObjTest() throws Exception {
/*
* @testName: positiveSetLongPrimTest
*
- * @assertion_ids: JSP:SPEC:93
+ * @assertion_ids: PAGES:SPEC:93
*
* @test_Strategy: Using jsp:useBean, create a new bean instance and set a
* long property of the bean using a String constant. PENDING Merge with prim
@@ -364,7 +364,7 @@ public void positiveSetLongPrimTest() throws Exception {
/*
* @testName: positiveSetPropAllTest
*
- * @assertion_ids: JSP:SPEC:162.2.1
+ * @assertion_ids: PAGES:SPEC:162.2.1
*
* @test_Strategy: Using jsp:useBean, create a new bean instance and set the
* property attribute to '*'. The following properties should be set by the
@@ -387,7 +387,7 @@ public void positiveSetPropAllTest() throws Exception {
/*
* @testName: positiveSetPropNoParamTest
*
- * @assertion_ids: JSP:SPEC:162.4
+ * @assertion_ids: PAGES:SPEC:162.4
*
* @test_Strategy: Using jsp:useBean, create a new bean instance.
* jsp:setProperty only specifies the name and property properties. The
@@ -412,7 +412,7 @@ public void positiveSetPropNoParamTest() throws Exception {
/*
* @testName: positiveSetPropParamTest
*
- * @assertion_ids: JSP:SPEC:162.3
+ * @assertion_ids: PAGES:SPEC:162.3
*
* @test_Strategy: Using jsp:useBean, create a new bean instance.
* jsp:setProperty only specifies the param property. The container should set
@@ -436,7 +436,7 @@ public void positiveSetPropParamTest() throws Exception {
/*
* @testName: positiveSetPropReqTimeSingleQuotesTest
*
- * @assertion_ids: JSP:SPEC:162.7.1
+ * @assertion_ids: PAGES:SPEC:162.7.1
*
* @test_Strategy: Using jsp:useBean, create a new bean instance. Set the
* value of a bean property using a request-time attribute expression
@@ -455,7 +455,7 @@ public void positiveSetPropReqTimeSingleQuotesTest() throws Exception {
/*
* @testName: positiveSetPropReqTimeDoubleQuotesTest
*
- * @assertion_ids: JSP:SPEC:162.7.1
+ * @assertion_ids: PAGES:SPEC:162.7.1
*
* @test_Strategy: Using jsp:useBean, create a new bean instance. Set the
* value of a bean property using a request-time attribute expression
@@ -474,7 +474,7 @@ public void positiveSetPropReqTimeDoubleQuotesTest() throws Exception {
/*
* @testName: positiveSetPropValueTest
*
- * @assertion_ids: JSP:SPEC:162.1; JSP:SPEC:162.2; JSP:SPEC:162.7
+ * @assertion_ids: PAGES:SPEC:162.1; PAGES:SPEC:162.2; PAGES:SPEC:162.7
*
* @test_Strategy: Using jsp:useBean, create a new bean instance. Set the
* value of a bean property using the value attribute.
@@ -491,7 +491,7 @@ public void positiveSetPropValueTest() throws Exception {
/*
* @testName: positiveBeanPropertyEditorTest
*
- * @assertion_ids: JSP:SPEC:86
+ * @assertion_ids: PAGES:SPEC:86
*
* @test_Strategy: Create a bean using useBean tag, use setProperty and and
* verfiy results using getProperty.
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/usebean/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/usebean/URLClientIT.java
index 1e5ffcab..fb58141a 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/usebean/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/actions/usebean/URLClientIT.java
@@ -28,7 +28,6 @@
import org.jboss.arquillian.container.test.api.Deployment;
import org.jboss.arquillian.junit5.ArquillianExtension;
-import org.jboss.shrinkwrap.api.Filters;
import org.jboss.shrinkwrap.api.ShrinkWrap;
import org.jboss.shrinkwrap.api.spec.WebArchive;
import org.junit.jupiter.api.Test;
@@ -52,10 +51,10 @@ public URLClientIT() throws Exception {
@Deployment(testable = false)
public static WebArchive createDeployment() throws IOException {
-
+
WebArchive archive = ShrinkWrap.create(WebArchive.class, "jsp_coresyntx_act_usebean_web.war");
archive.addClasses(Counter.class, NewCounter.class, String_IntBean.class);
-
+
archive.setWebXML(URLClientIT.class.getClassLoader().getResource(packagePath+"/jsp_coresyntx_act_usebean_web.xml"));
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/date.ser")), "WEB-INF/classes/date.ser");
@@ -80,7 +79,7 @@ public static WebArchive createDeployment() throws IOException {
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/negativeClassCastException.jsp")), "negativeClassCastException.jsp");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/errorPage.jsp")), "errorPage.jsp");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/defaultScope.jsp")), "defaultScope.jsp");
-
+
return archive;
}
@@ -93,9 +92,9 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: positiveBeanNameTypeTest
- *
- * @assertion_ids: JSP:SPEC:155.1;JSP:SPEC:156;JSP:SPEC:162.2;JSP:SPEC:168.8
- *
+ *
+ * @assertion_ids: PAGES:SPEC:155.1;PAGES:SPEC:156;PAGES:SPEC:162.2;PAGES:SPEC:168.8
+ *
* @test_Strategy: Use jsp:useBean to create a bean where the beanName and
* type attributes have the same values. Verify that the bean can be used by
* invoking a method on the bean inside a scriplet.
@@ -111,9 +110,9 @@ public void positiveBeanNameTypeTest() throws Exception {
/*
* @testName: positiveBeanNameTypeCastTest
- *
- * @assertion_ids: JSP:SPEC:162.1
- *
+ *
+ * @assertion_ids: PAGES:SPEC:162.1
+ *
* @test_Strategy: Use jsp:useBean to create a bean where the beanName
* specifies one particular type, and type specifies a superclass of the value
* specified by beanName. Verify that the bean can be used by invoking a
@@ -130,9 +129,9 @@ public void positiveBeanNameTypeCastTest() throws Exception {
/*
* @testName: positiveBodyNewTest
- *
- * @assertion_ids: JSP:SPEC:161.7.1
- *
+ *
+ * @assertion_ids: PAGES:SPEC:161.7.1
+ *
* @test_Strategy: Using jsp:useBean, create a new instance. Within the body
* of the jsp:useBean action, use jsp:setProperty to initialize a Bean
* property. After closing the jsp:useBean action, use jsp:getProperty to
@@ -149,13 +148,13 @@ public void positiveBodyNewTest() throws Exception {
/*
* @testName: positivePageScopedObjectTest
- *
- * @assertion_ids: JSP:SPEC:158; JSP:SPEC:158.2;JSP:SPEC:8
- *
- * @test_Strategy: In one JSP page, create a new bean object using jsp:useBean
+ *
+ * @assertion_ids: PAGES:SPEC:158; PAGES:SPEC:158.2;PAGES:SPEC:8
+ *
+ * @test_Strategy: In one page, create a new bean object using jsp:useBean
* with the scope set to "page". After the object has been created, forward
- * the request to a second JSP page to validate that an object associated with
- * the same ID used in the first JSP page is not available in the current
+ * the request to a second page to validate that an object associated with
+ * the same ID used in the first page is not available in the current
* PageContext.
*/
@@ -171,13 +170,13 @@ public void positivePageScopedObjectTest() throws Exception {
/*
* @testName: positiveRequestScopedObjectTest
- *
- * @assertion_ids: JSP:SPEC:158; JSP:SPEC:158.3;JSP:SPEC:9
- *
- * @test_Strategy: In one JSP page, create a new bean object using jsp:useBean
+ *
+ * @assertion_ids: PAGES:SPEC:158; PAGES:SPEC:158.3;PAGES:SPEC:9
+ *
+ * @test_Strategy: In one page, create a new bean object using jsp:useBean
* with the scope set to "request". After the object has been created, forward
- * the request to a second JSP page to validate that an object associated with
- * the same ID used in the first JSP page is available in the current
+ * the request to a second page to validate that an object associated with
+ * the same ID used in the first page is available in the current
* HttpServletRequest.
*/
@@ -193,13 +192,13 @@ public void positiveRequestScopedObjectTest() throws Exception {
/*
* @testName: positiveSessionScopedObjectTest
- *
- * @assertion_ids: JSP:SPEC:158; JSP:SPEC:158.4;JSP:SPEC:10
- *
- * @test_Strategy: In one JSP page, create a new bean object using jsp:useBean
+ *
+ * @assertion_ids: PAGES:SPEC:158; PAGES:SPEC:158.4;PAGES:SPEC:10
+ *
+ * @test_Strategy: In one page, create a new bean object using jsp:useBean
* with the scope set to "session". After the object has been created, forward
- * the request to a second JSP page to validate that an object associated with
- * the same ID used in the first JSP page is available in the current
+ * the request to a second page to validate that an object associated with
+ * the same ID used in the first page is available in the current
* HttpSession.
*/
@@ -215,13 +214,13 @@ public void positiveSessionScopedObjectTest() throws Exception {
/*
* @testName: positiveApplicationScopedObjectTest
- *
- * @assertion_ids: JSP:SPEC:158; JSP:SPEC:158.5;JSP:SPEC:11
- *
- * @test_Strategy: In one JSP page, create a new bean object using jsp:useBean
+ *
+ * @assertion_ids: PAGES:SPEC:158; PAGES:SPEC:158.5;PAGES:SPEC:11
+ *
+ * @test_Strategy: In one page, create a new bean object using jsp:useBean
* with the scope set to "application". After the object has been created,
- * forward the request to a second JSP page to validate that an object
- * associated with the same ID used in the first JSP page is available in the
+ * forward the request to a second page to validate that an object
+ * associated with the same ID used in the first page is available in the
* current ServletContext.
*/
@@ -237,9 +236,9 @@ public void positiveApplicationScopedObjectTest() throws Exception {
/*
* @testName: positiveNoBodyTest
- *
- * @assertion_ids: JSP:SPEC:161.5
- *
+ *
+ * @assertion_ids: PAGES:SPEC:161.5
+ *
* @test_Strategy: Explicit test to ensure that the jsp:useBean action can be
* used without a body.
*/
@@ -254,9 +253,9 @@ public void positiveNoBodyTest() throws Exception {
/*
* @testName: positiveClassTypeCastTest
- *
- * @assertion_ids: JSP:SPEC:161.8
- *
+ *
+ * @assertion_ids: PAGES:SPEC:161.8
+ *
* @test_Strategy: Create a new bean instance with a particular class set for
* the class attribute, and a parent class for the type attribute. Validate
* That the instance is cast without an Exception.
@@ -272,9 +271,9 @@ public void positiveClassTypeCastTest() throws Exception {
/*
* @testName: negativeDuplicateIDFatalTranslationErrorTest
- *
- * @assertion_ids: JSP:SPEC:157
- *
+ *
+ * @assertion_ids: PAGES:SPEC:157
+ *
* @test_Strategy: Create two beans with the same id attribute. Validate that
* a Fatal Translation error occurs.
*/
@@ -291,9 +290,9 @@ public void negativeDuplicateIDFatalTranslationErrorTest() throws Exception {
/*
* @testName: negativeSessionScopeFatalTranslationErrorTest
- *
- * @assertion_ids: JSP:SPEC:10;JSP:SPEC:159
- *
+ *
+ * @assertion_ids: PAGES:SPEC:10;PAGES:SPEC:159
+ *
* @test_Strategy: Use the page directive to set the session attribute to
* false and then declare a bean with session scope. Validate that a Fatal
* Translation error occurs.
@@ -311,11 +310,11 @@ public void negativeSessionScopeFatalTranslationErrorTest() throws Exception {
/*
* @testName: negativeClassCastExceptionTest
- *
- * @assertion_ids: JSP:SPEC:161.4
- *
- * @test_Strategy: In one JSP page, declare a bean of a particular type with
- * session scope. Once declared, this page will forward to a second JSP page
+ *
+ * @assertion_ids: PAGES:SPEC:161.4
+ *
+ * @test_Strategy: In one page, declare a bean of a particular type with
+ * session scope. Once declared, this page will forward to a second page
* which will try to reference the previously declared bean in the session
* scope, but will define the type attribute with an incompatible type.
*/
@@ -334,9 +333,9 @@ public void negativeClassCastExceptionTest() throws Exception {
/*
* @testName: negativeTypeAssignableTest
- *
- * @assertion_ids: JSP:SPEC:152
- *
+ *
+ * @assertion_ids: PAGES:SPEC:152
+ *
* @test_Strategy: both type and class attributes are present and class is not
* assignable to type
*/
@@ -353,9 +352,9 @@ public void negativeTypeAssignableTest() throws Exception {
/*
* @testName: negativeInvalidScopeTest
- *
- * @assertion_ids: JSP:SPEC:158.6
- *
+ *
+ * @assertion_ids: PAGES:SPEC:158.6
+ *
* @test_Strategy: both type and class attributes are present and class is not
* assignable to type
*/
@@ -372,9 +371,9 @@ public void negativeInvalidScopeTest() throws Exception {
/*
* @testName: defaultScopeTest
- *
- * @assertion_ids: JSP:SPEC:158.1
- *
+ *
+ * @assertion_ids: PAGES:SPEC:158.1
+ *
* @test_Strategy: check if the default scope is page
*/
@@ -389,9 +388,9 @@ public void defaultScopeTest() throws Exception {
/*
* @testName: requestTimeBeanNameTest
- *
- * @assertion_ids: JSP:SPEC:154; JSP:SPEC:155
- *
+ *
+ * @assertion_ids: PAGES:SPEC:154; PAGES:SPEC:155
+ *
* @test_Strategy: use a request-time attribute expression for beanName
*/
@@ -407,9 +406,9 @@ public void requestTimeBeanNameTest() throws Exception {
/*
* @testName: serBeanNameTest
- *
- * @assertion_ids: JSP:SPEC:155; JSP:SPEC:152
- *
+ *
+ * @assertion_ids: PAGES:SPEC:155; PAGES:SPEC:152
+ *
* @test_Strategy: use beanName of the form a.b.c.ser
*/
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/directives/include/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/directives/include/URLClientIT.java
index 84042f30..0d4cafa5 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/directives/include/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/directives/include/URLClientIT.java
@@ -72,7 +72,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: positiveIncludeCtxRelativeDirectiveTest
*
- * @assertion_ids: JSP:SPEC:69
+ * @assertion_ids: PAGES:SPEC:69
*
* @test_Strategy: Using an include directive, include content referenced by a
* context-relative path. PENDING Merge with test below
@@ -89,7 +89,7 @@ public void positiveIncludeCtxRelativeDirectiveTest() throws Exception {
/*
* @testName: positiveIncludePageRelativeDirectiveTest
*
- * @assertion_ids: JSP:SPEC:69
+ * @assertion_ids: PAGES:SPEC:69
*
* @test_Strategy: Using an include directive, include content referenced by a
* page-relative path.
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/directives/page/SuperPage.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/directives/page/SuperPage.java
index be4c2903..7ba62b2e 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/directives/page/SuperPage.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/directives/page/SuperPage.java
@@ -104,7 +104,7 @@ public void jspInit() {
public void jspDestroy() {
}
- // to be provided by JSP processor
+ // to be provided by Jakarta Pages processor
abstract public void _jspService(HttpServletRequest request,
HttpServletResponse response) throws ServletException, IOException;
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/directives/page/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/directives/page/URLClientIT.java
index 7624afe9..3103e283 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/directives/page/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/directives/page/URLClientIT.java
@@ -147,7 +147,7 @@ public static WebArchive createDeployment() {
/*
* @testName: positiveBuffAutoflushTest
*
- * @assertion_ids: JSP:SPEC:44; JSP:SPEC:42
+ * @assertion_ids: PAGES:SPEC:44; PAGES:SPEC:42
*
* @test_Strategy: Leaving the defaults for autoFlush and buffer, validate
* that the buffer is automatically flushed once the buffer is full.
@@ -167,7 +167,7 @@ public void positiveBuffAutoflushTest() throws Exception {
/*
* @testName: negativeBuffAutoflushTest
*
- * @assertion_ids: JSP:SPEC:45
+ * @assertion_ids: PAGES:SPEC:45
*
* @test_Strategy: set autoFlash to false when buffer=none, resulting in a
* translation error.
@@ -185,7 +185,7 @@ public void negativeBuffAutoflushTest() throws Exception {
/*
* @testName: positiveBuffCreateTest
*
- * @assertion_ids: JSP:SPEC:41
+ * @assertion_ids: PAGES:SPEC:41
*
* @test_Strategy: Validate that the page can configure a buffer and set the
* autoFlush attribute to false. Write data to the output stream and manually
@@ -206,7 +206,7 @@ public void positiveBuffCreateTest() throws Exception {
/*
* @testName: negativeDuplicateBufferFatalTranslationErrorTest
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @test_Strategy: Declare a page directive with two buffer attributes of
* different values. Validate that a fatal translation error occurs.
@@ -225,7 +225,7 @@ public void negativeDuplicateBufferFatalTranslationErrorTest() throws Exception
/*
* @testName: negativeDuplicateBufferFatalTranslationError2Test
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @test_Strategy: Declare two page directives with buffer attributes of
* different values. Validate that a fatal translation error occurs.
@@ -244,7 +244,7 @@ public void negativeDuplicateBufferFatalTranslationError2Test() throws Exception
/*
* @testName: negativeDuplicateAutoFlushFatalTranslationErrorTest
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @test_Strategy: Declare a page directive with two autoFlush attributes of
* different values. Validate that a fatal translation error occurs.
@@ -263,7 +263,7 @@ public void negativeDuplicateAutoFlushFatalTranslationErrorTest()
/*
* @testName: negativeDuplicateAutoFlushFatalTranslationError2Test
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @test_Strategy: Declare two page directives with autoflush attributes of
* different values. Validate that a fatal translation error occurs.
@@ -283,7 +283,7 @@ public void negativeDuplicateAutoFlushFatalTranslationError2Test()
/*
* @testName: negativeDuplicateIsErrorPageFatalTranslationErrorTest
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @test_Strategy: Declare a page directive with two isErrorPage attributes of
* different values Validate that a fatal translation error occurs.
@@ -302,7 +302,7 @@ public void negativeDuplicateIsErrorPageFatalTranslationErrorTest()
/*
* @testName: negativeDuplicateIsErrorPageFatalTranslationError2Test
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @test_Strategy: Declare two page directives with isErrorPage attributes of
* different values. Validate that a fatal translation error occurs.
@@ -322,7 +322,7 @@ public void negativeDuplicateIsErrorPageFatalTranslationError2Test()
/*
* @testName: negativeDuplicateIsELIgnoredFatalTranslationErrorTest
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @test_Strategy: Declare a page directive with two isELIgnored attributes of
* different values. Validate that a fatal translation error occurs.
@@ -341,7 +341,7 @@ public void negativeDuplicateIsELIgnoredFatalTranslationErrorTest()
/*
* @testName: negativeDuplicateIsELIgnoredFatalTranslationError2Test
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @test_Strategy: Declare two page directives with isELIgnored attributes of
* different values. Validate that a fatal translation error occurs.
@@ -361,7 +361,7 @@ public void negativeDuplicateIsELIgnoredFatalTranslationError2Test()
/*
* @testName: negativeBufferOverflowExceptionTest
*
- * @assertion_ids: JSP:SPEC:44
+ * @assertion_ids: PAGES:SPEC:44
*
* @test_Strategy: Declare a page directive with autoFlush set to false.
* Overflow the buffer and verify the Exception is caught.
@@ -379,7 +379,7 @@ public void negativeBufferOverflowExceptionTest() throws Exception {
/*
* @testName: positiveContentTypeTest
*
- * @assertion_ids: JSP:SPEC:52
+ * @assertion_ids: PAGES:SPEC:52
*
* @test_Strategy: Using the page directive, set the contentType attribute to
* "text/plain;charset=ISO-8859-1". Verify on the client side that the
@@ -400,7 +400,7 @@ public void positiveContentTypeTest() throws Exception {
/*
* @testName: negativeDuplicateContentFatalTranslationErrorTest
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @test_Strategy: Declare a page directive with contentType attributes
* specified of different values. Validate that a fatal translation error
@@ -421,7 +421,7 @@ public void negativeDuplicateContentFatalTranslationErrorTest() throws Exception
/*
* @testName: negativeDuplicateContentFatalTranslationError2Test
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @test_Strategy: Declare two page directives with contentType attributes of
* different values. Validate that a fatal translation error occurs.
@@ -441,7 +441,7 @@ public void negativeDuplicateContentFatalTranslationError2Test()
/*
* @testName: positiveDefaultIsErrorPageTest
*
- * @assertion_ids: JSP:SPEC:49
+ * @assertion_ids: PAGES:SPEC:49
*
* @test_Strategy: Verify that the 'isErrorPage' attribute is false by
* generating an exception in the called page and then have the error page
@@ -462,9 +462,9 @@ public void positiveDefaultIsErrorPageTest() throws Exception {
/*
* @testName: positiveErrorPageTest
*
- * @assertion_ids: JSP:SPEC:48
+ * @assertion_ids: PAGES:SPEC:48
*
- * @test_Strategy: In the initial JSP page, generate a java.lang.Arithmetic
+ * @test_Strategy: In the initial page, generate a java.lang.Arithmetic
* Exception by dividing an int value by 0. Validate the following: The
* errorPage attributes value must be used instead of the error-page defined
* in web.xml
@@ -488,7 +488,7 @@ public void positiveErrorPageTest() throws Exception {
* errorPage attribute set. The Error page has isErrorPage set to false and
* will attempt to access the exception object.
*
- * A fatal translation error shall result if a JSP error page has the
+ * A fatal translation error shall result if a Jakarta Pages error page has the
* isErrorPage attribute set to false and an attempt is made to access the
* implicit exception object. JavaServer Pages Specification v1.2, Sec 2.10.1
*/
@@ -530,7 +530,7 @@ public void negativeDuplicateErrorPageFatalTranslationErrorTest()
/*
* @testName: negativeDuplicateErrorPageFatalTranslationError2Test
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @test_Strategy: Declare two page directives with errorPage attributes of
* different values. Validate that a fatal translation error occurs.
@@ -550,10 +550,10 @@ public void negativeDuplicateErrorPageFatalTranslationError2Test()
/*
* @testName: positiveExtendsTest
*
- * @assertion_ids: JSP:SPEC:33
+ * @assertion_ids: PAGES:SPEC:33
*
* @test_Strategy: Provide the extends attribute with a fully qualified class.
- * The resulting JSP implementation class will use instanceof to validate that
+ * The resulting Jakarta Pages implementation class will use instanceof to validate that
* this page instance is an instance of the class that it extends.
*/
@@ -568,7 +568,7 @@ public void positiveExtendsTest() throws Exception {
/*
* @testName: negativeDuplicateExtendsFatalTranslationErrorTest
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @assertion: Duplicate extends attributes with distinct values within a
* given translation unit shall result in a fatal translation error.
@@ -591,7 +591,7 @@ public void negativeDuplicateExtendsFatalTranslationErrorTest() throws Exception
/*
* @testName: negativeDuplicateExtendsFatalTranslationError2Test
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @assertion: Duplicate extends attributes with distinct values within a
* given translation unit
@@ -614,7 +614,7 @@ public void negativeDuplicateExtendsFatalTranslationError2Test()
/*
* @testName: positiveImportTest
*
- * @assertion_ids: JSP:SPEC:34
+ * @assertion_ids: PAGES:SPEC:34
*
* @test_Strategy: Use the import attribute to import 'java.util.Properties'.
* Validated that a Properties object can be created and used.
@@ -631,7 +631,7 @@ public void positiveImportTest() throws Exception {
/*
* @testName: implicitImportLangTest
*
- * @assertion_ids: JSP:SPEC:35
+ * @assertion_ids: PAGES:SPEC:35
*
* @test_Strategy: Validate that classes from the java.lang package are
* implicitly imported by creating and using a java.lang.Integer object.
@@ -649,7 +649,7 @@ public void implicitImportLangTest() throws Exception {
/*
* @testName: implicitImportJspTest
*
- * @assertion_ids: JSP:SPEC:35
+ * @assertion_ids: PAGES:SPEC:35
*
* @test_Strategy: Validate that classes from the jakarta.servlet.jsp package
* are implicitly imported by calling JspFactory.getDefaultFactory() method.
@@ -666,7 +666,7 @@ public void implicitImportJspTest() throws Exception {
/*
* @testName: implicitImportServletTest
*
- * @assertion_ids: JSP:SPEC:35
+ * @assertion_ids: PAGES:SPEC:35
*
* @test_Strategy: Validate that classes from the jakarta.servlet package are
* implicitly imported by creating and using an instance of RequestDispatcher.
@@ -683,7 +683,7 @@ public void implicitImportServletTest() throws Exception {
/*
* @testName: implicitImportHttpTest
*
- * @assertion_ids: JSP:SPEC:35
+ * @assertion_ids: PAGES:SPEC:35
*
* @test_Strategy: Validate that classes from the jakarta.servlet.http package
* are implicitly imported by creating and using an instance of Cookie.
@@ -700,7 +700,7 @@ public void implicitImportHttpTest() throws Exception {
/*
* @testName: positiveMultipleImportTest
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @test_Strategy: Declare a page directive with two import attributes.
*
@@ -719,7 +719,7 @@ public void positiveMultipleImportTest() throws Exception {
/*
* @testName: negativeMultiplePageEncodingTest
*
- * @assertion_ids: JSP:SPEC:229.21
+ * @assertion_ids: PAGES:SPEC:229.21
*
* @test_Strategy: Declare a page directive with two pageEncoding attributes.
*
@@ -737,7 +737,7 @@ public void negativeMultiplePageEncodingTest() throws Exception {
/*
* @testName: positiveInfoTest
*
- * @assertion_ids: JSP:SPEC:47
+ * @assertion_ids: PAGES:SPEC:47
*
* @test_Strategy: Set the info attribute of the page directive. Call
* getServletInfo().
@@ -754,7 +754,7 @@ public void positiveInfoTest() throws Exception {
/*
* @testName: negativeDuplicateInfoFatalTranslationErrorTest
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @test_Strategy: Declare a page directive with two info attributes of
* different values and Validate that a fatal translation error occurs.
@@ -774,7 +774,7 @@ public void negativeDuplicateInfoFatalTranslationErrorTest() throws Exception {
/*
* @testName: negativeDuplicateInfoFatalTranslationError2Test
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @test_Strategy: Declare two page directives with info attributes of
* different values and Validate that a fatal translation error occurs.
@@ -793,7 +793,7 @@ public void negativeDuplicateInfoFatalTranslationError2Test() throws Exception {
/*
* @testName: positiveLangTest
*
- * @assertion_ids: JSP:SPEC:32
+ * @assertion_ids: PAGES:SPEC:32
*
* @test_Strategy: Validate that the language attribute can be set to "java"
* without an error.
@@ -810,7 +810,7 @@ public void positiveLangTest() throws Exception {
/*
* @testName: negativeDuplicateLanguageFatalTranslationErrorTest
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @test_Strategy: Declare a page directive with two language attributes of
* different values. Validate that a fatal translation error occurs.
@@ -830,7 +830,7 @@ public void negativeDuplicateLanguageFatalTranslationErrorTest()
/*
* @testName: negativeDuplicateLanguageFatalTranslationError2Test
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @test_Strategy: Declare two page directives with language attributes of
* different values. Validate that a fatal translation error occurs.
@@ -850,7 +850,7 @@ public void negativeDuplicateLanguageFatalTranslationError2Test()
/*
* @testName: positiveSessionTest
*
- * @assertion_ids: JSP:SPEC:36
+ * @assertion_ids: PAGES:SPEC:36
*
* @test_Strategy: Set the session attribute to 'true' and validate that the
* implicit session variable can be accessed and used.
@@ -870,7 +870,7 @@ public void positiveSessionTest() throws Exception {
/*
* @testName: positiveSessionDefaultTest
*
- * @assertion_ids: JSP:SPEC:38
+ * @assertion_ids: PAGES:SPEC:38
*
* @test_Strategy: Do not set the session attribute in the page. Validate that
* the implicit session variable can be accessed and used.
@@ -890,7 +890,7 @@ public void positiveSessionDefaultTest() throws Exception {
/*
* @testName: negativeSessionFatalTranslationErrorTest
*
- * @assertion_ids: JSP:SPEC:37
+ * @assertion_ids: PAGES:SPEC:37
*
* @test_Strategy: Validate that setting the session attribute to false will
* result in a fatal translation error if the implicit session variable is
@@ -910,7 +910,7 @@ public void negativeSessionFatalTranslationErrorTest() throws Exception {
/*
* @testName: negativeDuplicateSessionFatalTranslationErrorTest
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @test_Strategy: Declare a page directive with two session attributes of
* different values. Validate that a fatal translation error occurs.
@@ -929,7 +929,7 @@ public void negativeDuplicateSessionFatalTranslationErrorTest() throws Exception
/*
* @testName: negativeDuplicateSessionFatalTranslationError2Test
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @test_Strategy: Declare two page directives with session attributes of
* different values. Validate that a fatal translation error occurs.
@@ -949,7 +949,7 @@ public void negativeDuplicateSessionFatalTranslationError2Test()
/*
* @testName: positiveDuplicateBufferTest
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @test_Strategy: Declare a page directive with two identical buffer
* attributes.
@@ -967,7 +967,7 @@ public void positiveDuplicateBufferTest() throws Exception {
/*
* @testName: positiveDuplicateAutoFlushTest
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @test_Strategy: Declare a page directive with two identical autoFlush
* attributes.
@@ -985,7 +985,7 @@ public void positiveDuplicateAutoFlushTest() throws Exception {
/*
* @testName: positiveDuplicateIsErrorPageTest
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @test_Strategy: Declare a page directive with two identical isErrorPage
* attributes.
@@ -1003,7 +1003,7 @@ public void positiveDuplicateIsErrorPageTest() throws Exception {
/*
* @testName: positiveDuplicateIsELIgnoredTest
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @test_Strategy: Declare a page directive with two identical isELIgnored
* attributes.
@@ -1021,7 +1021,7 @@ public void positiveDuplicateIsELIgnoredTest() throws Exception {
/*
* @testName: positiveDuplicateContentTest
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @test_Strategy: Declare a page directive with two identical contentType
* attributes specified.
@@ -1041,7 +1041,7 @@ public void positiveDuplicateContentTest() throws Exception {
/*
* @testName: positiveDuplicateErrorPageTest
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @test_Strategy: Declare a page directive with two identical errorPage
* attributes.
@@ -1060,7 +1060,7 @@ public void positiveDuplicateErrorPageTest() throws Exception {
/*
* @testName: positiveDuplicateExtendsTest
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @test_Strategy: Declare a page directive with two identical extends
* attributes.
@@ -1079,7 +1079,7 @@ public void positiveDuplicateExtendsTest() throws Exception {
/*
* @testName: positiveDuplicateInfoTest
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @test_Strategy: Declare a page directive with two identical info
* attributes.
@@ -1099,7 +1099,7 @@ public void positiveDuplicateInfoTest() throws Exception {
/*
* @testName: positiveDuplicateLanguageTest
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @test_Strategy: Declare a page directive with two identical language
* attributes.
@@ -1118,7 +1118,7 @@ public void positiveDuplicateLanguageTest() throws Exception {
/*
* @testName: positiveDuplicateSessionTest
*
- * @assertion_ids: JSP:SPEC:21
+ * @assertion_ids: PAGES:SPEC:21
*
* @test_Strategy: Declare a page directive with two identical session
* attributes.
@@ -1137,7 +1137,7 @@ public void positiveDuplicateSessionTest() throws Exception {
/*
* @testName: negativeBufferSuffixTest
*
- * @assertion_ids: JSP:SPEC:40
+ * @assertion_ids: PAGES:SPEC:40
*
* @test_Strategy: The suffix kb is mandatory or a translation error must
* occur.
@@ -1159,7 +1159,7 @@ public void negativeBufferSuffixTest() throws Exception {
/*
* @testName: errorPageExceptionAttributeTest
*
- * @assertion_ids: JSP:SPEC:50
+ * @assertion_ids: PAGES:SPEC:50
*
* @test_Strategy: Throwable object is transferred by the throwing page
* implementation to the error page implementation by saving the object
@@ -1183,7 +1183,7 @@ public void errorPageExceptionAttributeTest() throws Exception {
/*
* @testName: negativeImportUtilTest
*
- * @assertion_ids: JSP:SPEC:267
+ * @assertion_ids: PAGES:SPEC:267
*
* @test_Strategy: Verify that a jsp page does not import java.util.* by
* default.
@@ -1200,7 +1200,7 @@ public void negativeImportUtilTest() throws Exception {
/*
* @testName: negativeImportIoTest
*
- * @assertion_ids: JSP:SPEC:267
+ * @assertion_ids: PAGES:SPEC:267
*
* @test_Strategy: Verify that a jsp page does not import java.io.* by
* default.
@@ -1217,7 +1217,7 @@ public void negativeImportIoTest() throws Exception {
/*
* @testName: isELIgnoredTrueTemplateTextTest
*
- * @assertion_ids: JSP:SPEC:268
+ * @assertion_ids: PAGES:SPEC:268
*
* @test_Strategy: [IsELIgnored] Verify that EL expressions are ignored by the
* container in template text when the IsELIgnored page directive attribute is
@@ -1234,7 +1234,7 @@ public void isELIgnoredTrueTemplateTextTest() throws Exception {
/*
* @testName: isELIgnoredFalseTemplateTextDollarTest
*
- * @assertion_ids: JSP:SPEC:268
+ * @assertion_ids: PAGES:SPEC:268
*
* @test_Strategy: [IsELIgnored] Verify that EL expressions are recognized by
* the container in template text when the IsELIgnored page directive
@@ -1251,7 +1251,7 @@ public void isELIgnoredFalseTemplateTextDollarTest() throws Exception {
/*
* @testName: isELIgnoredFalseTemplateTextPoundTest
*
- * @assertion_ids: JSP:SPEC:268
+ * @assertion_ids: PAGES:SPEC:268
*
* @test_Strategy: [IsELIgnored] Verify that EL expressions are recognized by
* the container in template text when the IsELIgnored page directive
@@ -1271,7 +1271,7 @@ public void isELIgnoredFalseTemplateTextPoundTest() throws Exception {
/*
* @testName: isELIgnoredFalseActionTest
*
- * @assertion_ids: JSP:SPEC:268
+ * @assertion_ids: PAGES:SPEC:268
*
* @test_Strategy: [IsELIgnored] Verify that EL expressions are recognized by
* the container in actions when the IsELIgnored page directive attribute is
@@ -1288,7 +1288,7 @@ public void isELIgnoredFalseActionTest() throws Exception {
/*
* @testName: isELIgnoredTrueActionTest
*
- * @assertion_ids: JSP:SPEC:268
+ * @assertion_ids: PAGES:SPEC:268
*
* @test_Strategy: [IsELIgnored] Verify that EL expressions are ignored by the
* container in actions when the IsELIgnored page directive attribute is set
@@ -1305,7 +1305,7 @@ public void isELIgnoredTrueActionTest() throws Exception {
/*
* @testName: deferredSyntaxAllowedAsLiteralFalseTemplateTextTest
*
- * @assertion_ids: JSP:SPEC:269
+ * @assertion_ids: PAGES:SPEC:269
*
* @test_Strategy: [DeferredSyntaxAllowedAsLiteralPageDirective] Verify that
* when the DeferredSyntaxAllowedAsLiteral page directive attribute is set to
@@ -1325,7 +1325,7 @@ public void deferredSyntaxAllowedAsLiteralFalseTemplateTextTest()
/*
* @testName: deferredSyntaxAllowedAsLiteralTrueTemplateTextTest
*
- * @assertion_ids: JSP:SPEC:269
+ * @assertion_ids: PAGES:SPEC:269
*
* @test_Strategy: [DeferredSyntaxAllowedAsLiteralPageDirective] Verify that
* when the DeferredSyntaxAllowedAsLiteral page directive attribute is set to
@@ -1344,7 +1344,7 @@ public void deferredSyntaxAllowedAsLiteralTrueTemplateTextTest()
/*
* @testName: deferredSyntaxAllowedAsLiteralFalseActionTest
*
- * @assertion_ids: JSP:SPEC:269
+ * @assertion_ids: PAGES:SPEC:269
*
* @test_Strategy: [DeferredSyntaxAllowedAsLiteralPageDirective] Verify that
* when the DeferredSyntaxAllowedAsLiteral page directive attribute is set to
@@ -1363,7 +1363,7 @@ public void deferredSyntaxAllowedAsLiteralFalseActionTest() throws Exception {
/*
* @testName: deferredSyntaxAllowedAsLiteralTrueActionTest
*
- * @assertion_ids: JSP:SPEC:269
+ * @assertion_ids: PAGES:SPEC:269
*
* @test_Strategy: [DeferredSyntaxAllowedAsLiteralPageDirective] Verify that
* when the DeferredSyntaxAllowedAsLiteral page directive attribute is set to
@@ -1381,7 +1381,7 @@ public void deferredSyntaxAllowedAsLiteralTrueActionTest() throws Exception {
/*
* @testName: errorOnELNotFoundFalseTest
*
- * @assertion_ids: JSP:SPEC:319
+ * @assertion_ids: PAGES:SPEC:319
*
* @test_Strategy: [ErrorOnELNotFoundPageDirective] Verify that when the
* ErrorOnELNotFound page directive attribute is set to false, a reference
@@ -1400,7 +1400,7 @@ public void errorOnELNotFoundFalseTest()
/*
* @testName: errorOnELNotFoundDefaultTest
*
- * @assertion_ids: JSP:SPEC:319
+ * @assertion_ids: PAGES:SPEC:319
*
* @test_Strategy: [ErrorOnELNotFoundPageDirective] Verify that when the
* ErrorOnELNotFound page directive attribute is not specified, a reference
@@ -1419,7 +1419,7 @@ public void errorOnELNotFoundDefaultTest()
/*
* @testName: errorOnELNotFoundTrueTest
*
- * @assertion_ids: JSP:SPEC:319
+ * @assertion_ids: PAGES:SPEC:319
*
* @test_Strategy: [ErrorOnELNotFoundPageDirective] Verify that when the
* ErrorOnELNotFound page directive attribute is set to false, a reference
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/directives/taglib/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/directives/taglib/URLClientIT.java
index ad0f4ef2..a555f82a 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/directives/taglib/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/directives/taglib/URLClientIT.java
@@ -71,7 +71,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: positiveTagLibTest
*
- * @assertion_ids: JSP:SPEC:59; JSP:SPEC:64
+ * @assertion_ids: PAGES:SPEC:59; PAGES:SPEC:64
*
* @test_Strategy: Validate that the taglib directive is recognized by the
* container by declaring a new tag and calling an action against that tag.
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/implicitobjects/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/implicitobjects/URLClientIT.java
index 7f318c28..518698ac 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/implicitobjects/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/implicitobjects/URLClientIT.java
@@ -79,7 +79,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: checkSessionTest
*
- * @assertion_ids: JSP:SPEC:15
+ * @assertion_ids: PAGES:SPEC:15
*
* @test_Strategy: Validate that the object associated with the session
* scripting variable is of type jakarta.servlet.http.HttpSession and that a
@@ -119,7 +119,7 @@ public void checkConfigTest() throws Exception {
/*
* @testName: checkExceptionTest
*
- * @assertion_ids: JSP:SPEC:17
+ * @assertion_ids: PAGES:SPEC:17
*
* @test_Strategy: Validate that the object associated with the exception
* scripting variable is of an instance of the exception type thrown (a
@@ -172,7 +172,7 @@ public void checkPageTest() throws Exception {
/*
* @testName: checkPageContextTest
*
- * @assertion_ids: JSP:SPEC:14
+ * @assertion_ids: PAGES:SPEC:14
*
* @test_Strategy: Validate that the object associated with the pageContext
* scripting variable is of type jakarta.servlet.jsp.PageContext and that a
@@ -190,7 +190,7 @@ public void checkPageContextTest() throws Exception {
/*
* @testName: checkRequestTest
*
- * @assertion_ids: JSP:SPEC:12
+ * @assertion_ids: PAGES:SPEC:12
*
* @test_Strategy: Validate that the object associated with the request
* scripting variable is of type jakarta.servlet.Request (parent class of
@@ -212,7 +212,7 @@ public void checkRequestTest() throws Exception {
/*
* @testName: checkResponseTest
*
- * @assertion_ids: JSP:SPEC:13
+ * @assertion_ids: PAGES:SPEC:13
*
* @test_Strategy: Validate that the object associated with the response
* scripting variable is of type jakarta.servlet.Response (parent class of
@@ -231,7 +231,7 @@ public void checkResponseTest() throws Exception {
/*
* @testName: checkApplicationTest
*
- * @assertion_ids: JSP:SPEC:16
+ * @assertion_ids: PAGES:SPEC:16
*
* @test_Strategy: Validate that the object associated with the application
* scripting variable is of type jakarta.servlet.ServletContext that a method
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/scripting/declaration/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/scripting/declaration/URLClientIT.java
index 76721e37..90355f70 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/scripting/declaration/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/scripting/declaration/URLClientIT.java
@@ -72,7 +72,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: positiveDeclarationTest
*
- * @assertion_ids: JSP:SPEC:74;PENDING
+ * @assertion_ids: PAGES:SPEC:74;PENDING
*
* @test_Strategy: Validate the scripting declarations are properly
* recognized, by declaring and assigning a value to an int variable, and
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/scripting/el/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/scripting/el/URLClientIT.java
index 294e7805..4e45c788 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/scripting/el/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/scripting/el/URLClientIT.java
@@ -116,7 +116,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: elInvocationAndUsageTest
*
- * @assertion_ids: JSP:SPEC:97;JSP:SPEC:99;JSP:SPEC:100
+ * @assertion_ids: PAGES:SPEC:97;PAGES:SPEC:99;PAGES:SPEC:100
*
* @test_Strategy: Validate EL expression will be evaluated by the container
* when provided as attribute values for actions that accept dynamic values,
@@ -140,7 +140,7 @@ public void elInvocationAndUsageTest() throws Exception {
/*
* @testName: elStaticAttributeTest
*
- * @assertion_ids: JSP:SPEC:98
+ * @assertion_ids: PAGES:SPEC:98
*
* @test_Strategy: Validate EL expressions provided to an action that does not
* accept dynamic attributes will result in a translation error.
@@ -156,7 +156,7 @@ public void elStaticAttributeTest() throws Exception {
/*
* @testName: elAttributeSearchTest
*
- * @assertion_ids: JSP:SPEC:118
+ * @assertion_ids: PAGES:SPEC:118
*
* @test_Strategy: Validate that if no scope qualifier is provided, attributes
* are located in the PageContext using the semantics of
@@ -175,7 +175,7 @@ public void elAttributeSearchTest() throws Exception {
/*
* @testName: elBooleanLiteralTest
*
- * @assertion_ids: JSP:SPEC:101
+ * @assertion_ids: PAGES:SPEC:101
*
* @test_Strategy: Validate that the EL Boolean literal evaluated as expected.
*/
@@ -191,7 +191,7 @@ public void elBooleanLiteralTest() throws Exception {
/*
* @testName: elNullLiteralTest
*
- * @assertion_ids: JSP:SPEC:105
+ * @assertion_ids: PAGES:SPEC:105
*
* @test_Strategy: Validate that EL Null literal evaluated as expected.
*/
@@ -207,7 +207,7 @@ public void elNullLiteralTest() throws Exception {
/*
* @testName: elIntegerLiteralTest
*
- * @assertion_ids: JSP:SPEC:102
+ * @assertion_ids: PAGES:SPEC:102
*
* @test_Strategy: Validate that EL Integer literal evaluated as expected.
*/
@@ -223,7 +223,7 @@ public void elIntegerLiteralTest() throws Exception {
/*
* @testName: elFloatingPointLiteralTest
*
- * @assertion_ids: JSP:SPEC:103
+ * @assertion_ids: PAGES:SPEC:103
*
* @test_Strategy: Validate that EL Floating Point literal evaluated as
* expected.
@@ -240,7 +240,7 @@ public void elFloatingPointLiteralTest() throws Exception {
/*
* @testName: elStringLiteralTest
*
- * @assertion_ids: JSP:SPEC:104
+ * @assertion_ids: PAGES:SPEC:104
*
* @test_Strategy: Validate that EL String literal evaluated as expected.
*/
@@ -256,7 +256,7 @@ public void elStringLiteralTest() throws Exception {
/*
* @testName: elBinaryOperators1Test
*
- * @assertion_ids: JSP:SPEC:107.1;JSP:SPEC:107.2;JSP:SPEC:107.3;JSP:SPEC:107.4
+ * @assertion_ids: PAGES:SPEC:107.1;PAGES:SPEC:107.2;PAGES:SPEC:107.3;PAGES:SPEC:107.4
*
* @test_Strategy: Validate the binary operators, '+', '-', and '*' when using
* Doubles, Floats, and Strings.
@@ -273,7 +273,7 @@ public void elBinaryOperators1Test() throws Exception {
/*
* @testName: elBinaryOperators2Test
*
- * @assertion_ids: JSP:SPEC:108.1;JSP:SPEC:108.2;JSP:SPEC:108.3
+ * @assertion_ids: PAGES:SPEC:108.1;PAGES:SPEC:108.2;PAGES:SPEC:108.3
*
* @test_Strategy: Validate the binary operators, '/' and 'div' when using
* different types.
@@ -290,7 +290,7 @@ public void elBinaryOperators2Test() throws Exception {
/*
* @testName: elBinaryOperators3Test
*
- * @assertion_ids: JSP:SPEC:109.1;JSP:SPEC:109.2;JSP:SPEC:109.3;JSP:SPEC:109.4
+ * @assertion_ids: PAGES:SPEC:109.1;PAGES:SPEC:109.2;PAGES:SPEC:109.3;PAGES:SPEC:109.4
*
* @test_Strategy: Validate the binary operator '%' and 'mod' when using
* different types.
@@ -307,7 +307,7 @@ public void elBinaryOperators3Test() throws Exception {
/*
* @testName: elBinaryOperators4Test
*
- * @assertion_ids: JSP:SPEC:113.1
+ * @assertion_ids: PAGES:SPEC:113.1
*
* @test_Strategy: Validate the binary operator '&&', 'and', '||', and "or'
* when using different types.
@@ -324,8 +324,8 @@ public void elBinaryOperators4Test() throws Exception {
/*
* @testName: elUnaryOperators1Test
*
- * @assertion_ids: JSP:SPEC:110.1;JSP:SPEC:110.2.1;JSP:SPEC:110.2.2;
- * JSP:SPEC:110.2.3;JSP:SPEC:110.3
+ * @assertion_ids: PAGES:SPEC:110.1;PAGES:SPEC:110.2.1;PAGES:SPEC:110.2.2;
+ * PAGES:SPEC:110.2.3;PAGES:SPEC:110.3
*
* @test_Strategy: Validate the unary minus ('-') operator with variaous types
* and validate the evaluation of the expression returns the expected value.
@@ -342,7 +342,7 @@ public void elUnaryOperators1Test() throws Exception {
/*
* @testName: elUnaryOperators2Test
*
- * @assertion_ids: JSP:SPEC:114.1
+ * @assertion_ids: PAGES:SPEC:114.1
*
* @test_Strategy: Validate the unary minus ('!' and 'not') returns the
* expected value.
@@ -359,8 +359,8 @@ public void elUnaryOperators2Test() throws Exception {
/*
* @testName: elRelationalOperators1Test
*
- * @assertion_ids: JSP:SPEC:111.1;JSP:SPEC:111.2;JSP:SPEC:111.3;
- * JSP:SPEC:111.4;JSP:SPEC:111.8;JSP:SPEC:111.5; JSP:SPEC:111.6
+ * @assertion_ids: PAGES:SPEC:111.1;PAGES:SPEC:111.2;PAGES:SPEC:111.3;
+ * PAGES:SPEC:111.4;PAGES:SPEC:111.8;PAGES:SPEC:111.5; PAGES:SPEC:111.6
*
* @test_Strategy: Validate the relational operators '<', '>', '<=', '>=',
* 'lt', 'gt', 'le', 'ge' when one value is null, as well as the various types
@@ -379,8 +379,8 @@ public void elRelationalOperators1Test() throws Exception {
/*
* @testName: elRelationalOperators2Test
*
- * @assertion_ids: JSP:SPEC:112.1;JSP:SPEC:112.2;JSP:SPEC:112.3;
- * JSP:SPEC:112.4;JSP:SPEC:112.5;JSP:SPEC:112.6; JSP:SPEC:112.6.2
+ * @assertion_ids: PAGES:SPEC:112.1;PAGES:SPEC:112.2;PAGES:SPEC:112.3;
+ * PAGES:SPEC:112.4;PAGES:SPEC:112.5;PAGES:SPEC:112.6; PAGES:SPEC:112.6.2
*
* @test_Strategy: Validate the relational operators '==', '!=', 'ne', 'eq',
* when one value is null or both values are null, as well as the various
@@ -399,8 +399,8 @@ public void elRelationalOperators2Test() throws Exception {
/*
* @testName: elEmptyOperatorTest
*
- * @assertion_ids: JSP:SPEC:115.1;JSP:SPEC:115.2;JSP:SPEC:115.3;
- * JSP:SPEC:115.4;JSP:SPEC:115.5;JSP:SPEC:115.6
+ * @assertion_ids: PAGES:SPEC:115.1;PAGES:SPEC:115.2;PAGES:SPEC:115.3;
+ * PAGES:SPEC:115.4;PAGES:SPEC:115.5;PAGES:SPEC:115.6
*
* @test_Strategy: Validate the behavior of the EL 'empty' operator when used
* to evaluate null, String, array, Map, and Collection values (on the case of
@@ -418,8 +418,8 @@ public void elEmptyOperatorTest() throws Exception {
/*
* @testName: elStringCoercionTest
*
- * @assertion_ids: JSP:SPEC:135.1;JSP:SPEC:135.2;JSP:SPEC:135.4;
- * JSP:SPEC:134.5
+ * @assertion_ids: PAGES:SPEC:135.1;PAGES:SPEC:135.2;PAGES:SPEC:135.4;
+ * PAGES:SPEC:134.5
*
* @testStrategy: Validate that various can be successfully corerced to a
* String using the EL string coercion rules. Also validate any error
@@ -437,8 +437,8 @@ public void elStringCoercionTest() throws Exception {
/*
* @testName: elNumberCoercionTest
*
- * @assertion_ids: JSP:SPEC:136.1;JSP:SPEC:136.2;JSP:SPEC:136.3;
- * JSP:SPEC:136.4;JSP:SPEC:136.5;JSP:SPEC:136.6; JSP:SPEC:136.7;JSP:SPEC:136.8
+ * @assertion_ids: PAGES:SPEC:136.1;PAGES:SPEC:136.2;PAGES:SPEC:136.3;
+ * PAGES:SPEC:136.4;PAGES:SPEC:136.5;PAGES:SPEC:136.6; PAGES:SPEC:136.7;PAGES:SPEC:136.8
*
* @testStrategy: Validate the EL is able to convert between the various
* number types successfully based on varying input and target values. Also
@@ -456,8 +456,8 @@ public void elNumberCoercionTest() throws Exception {
/*
* @testName: elCharacterCoercionTest
*
- * @assertion_ids: JSP:SPEC:137.1;JSP:SPEC:137.2;JSP:SPEC:137.3;
- * JSP:SPEC:137.4;JSP:SPEC:137.5;JSP:SPEC:137.6
+ * @assertion_ids: PAGES:SPEC:137.1;PAGES:SPEC:137.2;PAGES:SPEC:137.3;
+ * PAGES:SPEC:137.4;PAGES:SPEC:137.5;PAGES:SPEC:137.6
*
* @testStrategy: Validate that the EL is able to convert various types to a
* Character. Also validate any error conditions that can occur during the
@@ -475,8 +475,8 @@ public void elCharacterCoercionTest() throws Exception {
/*
* @testName: elBooleanCoercionTest
*
- * @assertion_ids: JSP:SPEC:138.1;JSP:SPEC:138.2;JSP:SPEC:138.3;
- * JSP:SPEC:138.4;JSP:SPEC:138.5
+ * @assertion_ids: PAGES:SPEC:138.1;PAGES:SPEC:138.2;PAGES:SPEC:138.3;
+ * PAGES:SPEC:138.4;PAGES:SPEC:138.5
*
* @testStrategy: Validate that the EL is able to convert various types to a
* Boolean. Also validate any error conditions that can occur during the
@@ -494,8 +494,8 @@ public void elBooleanCoercionTest() throws Exception {
/*
* @testName: elOtherTypeCoercionTest
*
- * @assertion_ids: JSP:SPEC:139.1;JSP:SPEC:139.2;JSP:SPEC:139.3;
- * JSP:SPEC:139.6
+ * @assertion_ids: PAGES:SPEC:139.1;PAGES:SPEC:139.2;PAGES:SPEC:139.3;
+ * PAGES:SPEC:139.6
*
* @testStrategy: Validate that the EL is able to convert various types
* including invoking propery editors if target type has PropertyEditory.
@@ -513,7 +513,7 @@ public void elOtherTypeCoercionTest() throws Exception {
/*
* @testName: elPrimitiveBoxedTypeConversionTest
*
- * @assertion_ids: JSP:SPEC:134.1;JSP:SPEC:134.2;JSP:SPEC:134.4
+ * @assertion_ids: PAGES:SPEC:134.1;PAGES:SPEC:134.2;PAGES:SPEC:134.4
*
* @testStrategy: Validate that if the target type is primitive and the
* resulting EL evaluation is a boxed type, the result is 'unboxed' and passed
@@ -531,7 +531,7 @@ public void elPrimitiveBoxedTypeConversionTest() throws Exception {
/*
* @testName: elFunctionInvocationTest
*
- * @assertion_ids: JSP:SPEC:122.5;JSP:SPEC:122.6
+ * @assertion_ids: PAGES:SPEC:122.5;PAGES:SPEC:122.6
*
* @test_Strategy: Validation an EL Function can be successfully invoked.
*/
@@ -546,7 +546,7 @@ public void elFunctionInvocationTest() throws Exception {
/*
* @testName: elNonExistingFunctionNameTest
*
- * @assertion_ids: JSP:SPEC:122.3
+ * @assertion_ids: PAGES:SPEC:122.3
*
* @test_Strategy: Validate a translation error occurs if the specified
* function name doesn't exist in the imported taglibrary.
@@ -562,7 +562,7 @@ public void elNonExistingFunctionNameTest() throws Exception {
/*
* @testName: elNonMatchingFunctionSignatureTest
*
- * @assertion_ids: JSP:SPEC:122.4
+ * @assertion_ids: PAGES:SPEC:122.4
*
* @test_Strategy: Validate a translation error occurs if the specified
* function find a matching name, but the signature doesn't match.
@@ -578,7 +578,7 @@ public void elNonMatchingFunctionSignatureTest() throws Exception {
/*
* @testName: elNonStaticPublicFunctionTest
*
- * @assertion_ids: JSP:SPEC:120
+ * @assertion_ids: PAGES:SPEC:120
*
* @test_Strategy: Validate a translation error occurs if the specified
* function is not defined a public static.
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/scripting/escaping/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/scripting/escaping/URLClientIT.java
index b7f84946..e91f4f4d 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/scripting/escaping/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/scripting/escaping/URLClientIT.java
@@ -70,7 +70,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: positiveEscapingTest
*
- * @assertion_ids: JSP:SPEC:7
+ * @assertion_ids: PAGES:SPEC:7
*
* @testStrategy: Validate handling of escaped entities.
*/
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/scripting/expressions/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/scripting/expressions/URLClientIT.java
index 8c533163..f175d7af 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/scripting/expressions/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/scripting/expressions/URLClientIT.java
@@ -73,7 +73,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: positiveExprTest
*
- * @assertion_ids: JSP:SPEC:77
+ * @assertion_ids: PAGES:SPEC:77
*
* @test_Strategy: Validate that the container can correctly support a basic
* expression by validating the output returned.
@@ -90,7 +90,7 @@ public void positiveExprTest() throws Exception {
/*
* @testName: positiveExprCommentTest
*
- * @assertion_ids: JSP:SPEC:5
+ * @assertion_ids: PAGES:SPEC:5
*
* @test_Strategy: Validate that an HTML stye comment with an embedded
* expression returns the value of the expression within the comment and that
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/scripting/scriptlet/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/scripting/scriptlet/URLClientIT.java
index ebe797a5..26f97b0a 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/scripting/scriptlet/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/core_syntax/scripting/scriptlet/URLClientIT.java
@@ -73,7 +73,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: positiveScriptletTest
*
- * @assertion_ids: JSP:SPEC:76
+ * @assertion_ids: PAGES:SPEC:76
*
* @test_Strategy: Correct syntax is used in the scriptlet
*
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/el/jsp/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/el/jsp/URLClientIT.java
index dc1c6b5b..0b94fbb4 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/el/jsp/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/el/jsp/URLClientIT.java
@@ -91,7 +91,7 @@ public static WebArchive createDeployment() {
/*
* @testName: positiveELDeferredValueValueTest
*
- * @assertion_ids: JSP:SPEC:282
+ * @assertion_ids: PAGES:SPEC:282
*
* @test_Strategy: [ELDeferredValueValue] In a jsp page, pass a String literal
* expression and an expression using the #{} syntax to a tag handler via a
@@ -110,7 +110,7 @@ public void positiveELDeferredValueValueTest() throws Exception {
/*
* @testName: negativeELDeferredValueValueTest
*
- * @assertion_ids: JSP:SPEC:282
+ * @assertion_ids: PAGES:SPEC:282
*
* @test_Strategy: [ELDeferredValueValue] In a jsp page, pass an expression
* using the ${} syntax to a tag handler via a deferred-value element in the
@@ -127,7 +127,7 @@ public void negativeELDeferredValueValueTest() throws Exception {
/*
* @testName: eLDeferredValueCoercionTest
*
- * @assertion_ids: JSP:SPEC:284
+ * @assertion_ids: PAGES:SPEC:284
*
* @test_Strategy: [ELDeferredValueCoercion] In a jsp page, pass a String
* literal expression and an expression using the #{} syntax to a tag handler
@@ -146,7 +146,7 @@ public void eLDeferredValueCoercionTest() throws Exception {
/*
* @testName: positiveELDeferredMethodValueTest
*
- * @assertion_ids: JSP:SPEC:287
+ * @assertion_ids: PAGES:SPEC:287
*
* @test_Strategy: [ELDeferredMethodValue] In a jsp page, pass a String
* literal expression and an expression using the #{} syntax to a tag handler
@@ -165,7 +165,7 @@ public void positiveELDeferredMethodValueTest() throws Exception {
/*
* @testName: negativeELDeferredMethodValueTest
*
- * @assertion_ids: JSP:SPEC:287
+ * @assertion_ids: PAGES:SPEC:287
*
* @test_Strategy: [ELDeferredMethodValue] In a jsp page, pass an expression
* using the ${} syntax to a tag handler via a deferred-method element in the
@@ -182,7 +182,7 @@ public void negativeELDeferredMethodValueTest() throws Exception {
/*
* @testName: eLDeferredMethodStringLiteralTest
*
- * @assertion_ids: JSP:SPEC:288
+ * @assertion_ids: PAGES:SPEC:288
*
* @test_Strategy: [ELDeferredMethodStringLiteral] In a jsp page, pass a
* literal expression representing a String and a literal expression
@@ -201,7 +201,7 @@ public void eLDeferredMethodStringLiteralTest() throws Exception {
/*
* @testName: eLDeferredMethodStringLiteralErrorTest1
*
- * @assertion_ids: JSP:SPEC:289
+ * @assertion_ids: PAGES:SPEC:289
*
* @test_Strategy: [ELDeferredMethodStringLiteralError] In a jsp page, pass a
* string literal to a tag handler via a deferred-method element in the tld
@@ -219,7 +219,7 @@ public void eLDeferredMethodStringLiteralErrorTest1() throws Exception {
/*
* @testName: eLDeferredMethodStringLiteralErrorTest2
*
- * @assertion_ids: JSP:SPEC:289
+ * @assertion_ids: PAGES:SPEC:289
*
* @test_Strategy: [ELDeferredMethodStringLiteralError] In a jsp page, pass a
* string literal to a tag handler via a deferred-method element in the tld
@@ -237,7 +237,7 @@ public void eLDeferredMethodStringLiteralErrorTest2() throws Exception {
/*
* @testName: templateTextPoundTranslationErrorTest
*
- * @assertion_ids: JSP:SPEC:272
+ * @assertion_ids: PAGES:SPEC:272
*
* @test_Strategy: [TemplateTextPoundTranslationError] Verify that the #{
* character sequence, when embedded in template text, triggers a translation
@@ -254,7 +254,7 @@ public void templateTextPoundTranslationErrorTest() throws Exception {
/*
* @testName: tagLibraryPoundTranslationErrorTest
*
- * @assertion_ids: JSP:SPEC:273
+ * @assertion_ids: PAGES:SPEC:273
*
* @test_Strategy: [TagLibraryPoundTranslationError] Verify that the #{
* character sequence triggers a translation error if used for a tag attribute
@@ -272,7 +272,7 @@ public void tagLibraryPoundTranslationErrorTest() throws Exception {
/*
* @testName: allowedDynamicAttributeValueTypesTest
*
- * @assertion_ids: JSP:SPEC:290
+ * @assertion_ids: PAGES:SPEC:290
*
* @test_Strategy: [AllowedDynamicAttributeValueTypes] In a jsp page, pass a
* literal expression, a scriptlet expression, an expression using the ${}
@@ -291,7 +291,7 @@ public void allowedDynamicAttributeValueTypesTest() throws Exception {
/*
* @testName: dynamicAttributeSetterMethodTest
*
- * @assertion_ids: JSP:SPEC:291
+ * @assertion_ids: PAGES:SPEC:291
*
* @test_Strategy: [DynamicAttributeSetterMethod] Verify that an argument to
* the setter method of a dynamic attribute must be of type java.lang.Object.
@@ -310,7 +310,7 @@ public void dynamicAttributeSetterMethodTest() throws Exception {
/*
* @testName: implicitImportTest
*
- * @assertion_ids: JSP:SPEC:35
+ * @assertion_ids: PAGES:SPEC:35
*
* @test_Strategy: [ImplicitELImport] Verify that each of the implicit package
* is available to the EL environment.
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/i18n/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/i18n/URLClientIT.java
index f3677960..409ce6d8 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/i18n/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/i18n/URLClientIT.java
@@ -30,7 +30,6 @@
import org.jboss.arquillian.container.test.api.Deployment;
import org.jboss.arquillian.junit5.ArquillianExtension;
-import org.jboss.shrinkwrap.api.Filters;
import org.jboss.shrinkwrap.api.ShrinkWrap;
import org.jboss.shrinkwrap.api.spec.WebArchive;
import org.junit.jupiter.api.Test;
@@ -51,11 +50,11 @@ public URLClientIT() throws Exception {
@Deployment(testable = false)
public static WebArchive createDeployment() throws IOException {
-
+
String packagePath = URLClientIT.class.getPackageName().replace(".", "/");
WebArchive archive = ShrinkWrap.create(WebArchive.class, "jsp_i18n_web.war");
archive.setWebXML(URLClientIT.class.getClassLoader().getResource(packagePath+"/jsp_i18n_web.xml"));
- archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/BadTagPageEncoding.tag", "tags/BadTagPageEncoding.tag");
+ archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tags/BadTagPageEncoding.tag", "tags/BadTagPageEncoding.tag");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/inclusion_utf-16LE.jspx")), "inclusion_utf-16LE.jspx");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/inclusion_iso.txt")), "inclusion_iso.txt");
@@ -98,11 +97,11 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: i18nStandardPageResponseEncodingTest
- *
- * @assertion_ids: JSP:SPEC:249.4;JSP:SPEC:250.3;JSP:SPEC:250.6.2;
- * JSP:SPEC:250.2;JSP:SPEC:249.2;JSP:SPEC:250.6.1;
- * JSP:SPEC:249.3;JSP:SPEC:250.1;JSP:SPEC:250.4
- *
+ *
+ * @assertion_ids: PAGES:SPEC:249.4;PAGES:SPEC:250.3;PAGES:SPEC:250.6.2;
+ * PAGES:SPEC:250.2;PAGES:SPEC:249.2;PAGES:SPEC:250.6.1;
+ * PAGES:SPEC:249.3;PAGES:SPEC:250.1;PAGES:SPEC:250.4
+ *
* @test_Strategy: Request 1: Using a page encoded in ISO-8859-1, with no page
* directive including verify the page is is properly loaded and the resulting
* output content type is the default of text/html with the charset parameter
@@ -133,7 +132,7 @@ public static WebArchive createDeployment() throws IOException {
* consideration. If there's no such specification, no initial response
* character encoding is passed to ServletResponse.setContentType() - the
* ServletResponse object's default, ISO-8859-1, is used."
- *
+ *
* However, this section omits the fact that if the default encoding is used,
* it will be added to the response content type as soon as
* ServletResponse.getWriter() is called. See the javadoc for
@@ -176,11 +175,11 @@ public void i18nStandardPageResponseEncodingTest() throws Exception {
/*
* @testName: i18nXmlPageResponseEncodingTest
- *
- * @assertion_ids: JSP:SPEC:249.5;JSP:SPEC:249.6;JSP:SPEC:250.5;
- * JSP:SPEC:250.3;JSP:SPEC:250.1;JSP:SPEC:250.4
- *
- * @test_Strategy: This test will exercise JSP documents with and without a
+ *
+ * @assertion_ids: PAGES:SPEC:249.5;PAGES:SPEC:249.6;PAGES:SPEC:250.5;
+ * PAGES:SPEC:250.3;PAGES:SPEC:250.1;PAGES:SPEC:250.4
+ *
+ * @test_Strategy: This test will exercise documents with and without a
* prolog with an encoding attribute. This will be performed over several
* requests. This test will also validate that items such as charset
* parameters present in a contentType attribute don't cause problems with the
@@ -199,29 +198,29 @@ public void i18nStandardPageResponseEncodingTest() throws Exception {
* pageEncoding attribute of the page directive. Since the contentType
* attribute is also present the resulting output should have a content type
* of text/plain with a charset of ISO-8859-1. Request 5: Validate that if the
- * JSP document (encoding in UTF-16) has a prolog with no encoding attribute,
+ * document (encoding in UTF-16) has a prolog with no encoding attribute,
* that the container is able to properly load the document using the encoding
* detection semantics specified by the XML 1.0 specification. In this case
- * the JSP document has no pageEncoding or contentType attributes and is
+ * the document has no pageEncoding or contentType attributes and is
* encoded in UTF-16. The container should be able to load and parse the page
* without issue. The response content type should be text/xml with a charset
- * of UTF-8. Request 6: Validate that a JSP document (encoding in UTF-16BE)
+ * of UTF-8. Request 6: Validate that a document (encoding in UTF-16BE)
* has a prolog with no encoding attribute, that the container is able to
* properly load the document using the encoding detection semantics specified
- * by the XML 1.0 specification. In this case the JSP document has only a
+ * by the XML 1.0 specification. In this case the document has only a
* pageEncoding attribute defined. The container should be able to load and
* parse the page without issue. The response content type should be text/xml
- * with a charset of UTF-8. Request 7: Validate that a JSP document (encoded
+ * with a charset of UTF-8. Request 7: Validate that a document (encoded
* in UTF-16LE) has a prolog with no encoding attribute, that the container is
* able to properly load the document using the encoding detection semantics
- * specified by the XML 1.0 specification. In this case the JSP document has
+ * specified by the XML 1.0 specification. In this case the document has
* only a contentType attribute defined. The container should be able to load
* and parse the page without issue. The response content type should be based
* off the contentType attribute: text/plain with a charset of ISO-8859-1.
- * Request 8: Validate that a JSP document (encoded in UTF-16) has a prolog
+ * Request 8: Validate that a document (encoded in UTF-16) has a prolog
* with no encoding attribute, that the container is able to properly load the
* document using the encoding detection semantics specified by the XML 1.0
- * specification. In this case the JSP document has both contentType and
+ * specification. In this case the document has both contentType and
* pageEncoding attributes defined. The container should be able to load and
* parse the page without issue. The response content type should be based off
* the contentType attribute: text/plain with a charset of ISO-8859-1.
@@ -287,11 +286,11 @@ public void i18nXmlPageResponseEncodingTest() throws Exception {
/*
* @testName: i18nEncodingMismatchTest
- *
- * @assertion_ids: JSP:SPEC:249.7
- *
- * @test_Strategy: Validate that if a JSP Document specifies an encoding in
- * the XML prolog and a JSP page directive specifies a different encoding, a
+ *
+ * @assertion_ids: PAGES:SPEC:249.7
+ *
+ * @test_Strategy: Validate that if a Jakarta Pages Document specifies an encoding in
+ * the XML prolog and a Jakarta Pages page directive specifies a different encoding, a
* translation error occurs. NOTE: The similiar translation-time
* error with a mismatched encoding between property groups and pages in
* standard syntax are covered in the spec/configuration test area.
@@ -311,11 +310,11 @@ public void i18nEncodingMismatchTest() throws Exception {
/*
* @testName: i18nUnsupportedEncodingTest
- *
- * @assertion_ids: JSP:SPEC:249.8
- *
- * @test_Strategy: Validate a translation error occurs if a standard JSP
- * specifies an invalid encoding in the page directive, or if a JSP document
+ *
+ * @assertion_ids: PAGES:SPEC:249.8
+ *
+ * @test_Strategy: Validate a translation error occurs if a standard page
+ * specifies an invalid encoding in the page directive, or if a document
* has an invalid encoding in the prolog.
*/
@Test
@@ -332,13 +331,13 @@ public void i18nUnsupportedEncodingTest() throws Exception {
/*
* @testName: i18nIncludedContentTest
- *
- * @assertion_ids: JSP:SPEC:249.5
- *
+ *
+ * @assertion_ids: PAGES:SPEC:249.5
+ *
* @test_Strategy: Validate that units that make up a single translation unit
- * all have their file encoding detected individually. In this case a JSP
+ * all have their file encoding detected individually. In this case a Jakarta Pages
* Document encoded in UTF-16BE using the include directive includes another
- * JSP Document encoded in UTF-16LE.
+ * Jakarta Pages Document encoded in UTF-16LE.
*/
@Test
public void i18nIncludedContentTest() throws Exception {
@@ -354,9 +353,9 @@ public void i18nIncludedContentTest() throws Exception {
/*
* @testName: i18nBomByteSequencesUTF8Test
- *
- * @assertion_ids: JSP:SPEC:299
- *
+ *
+ * @assertion_ids: PAGES:SPEC:299
+ *
* @test_Strategy: [BOMCharacterEncodingDescription] Verify that the character
* encoding of pages in standard syntax is determined by a BOM, and that the
* byte sequences reserved to identify a BOM at the beginning of a page do not
@@ -375,9 +374,9 @@ public void i18nBomByteSequencesUTF8Test() throws Exception {
/*
* @testName: i18nBomByteSequencesUTF16BETest
- *
- * @assertion_ids: JSP:SPEC:299
- *
+ *
+ * @assertion_ids: PAGES:SPEC:299
+ *
* @test_Strategy: [BOMCharacterEncodingDescription] Verify that the character
* encoding of pages in standard syntax is determined by a BOM, and that the
* byte sequences reserved to identify a BOM at the beginning of a page do not
@@ -397,9 +396,9 @@ public void i18nBomByteSequencesUTF16BETest() throws Exception {
/*
* @testName: i18nBomByteSequencesUTF16LETest
- *
- * @assertion_ids: JSP:SPEC:299
- *
+ *
+ * @assertion_ids: PAGES:SPEC:299
+ *
* @test_Strategy: [BOMCharacterEncodingDescription] Verify that the character
* encoding of pages in standard syntax is determined by a BOM, and that the
* byte sequences reserved to identify a BOM at the beginning of a page do not
@@ -419,11 +418,11 @@ public void i18nBomByteSequencesUTF16LETest() throws Exception {
/*
* @testName: i18nBomLegalCharacterEncodingTest1
- *
- * @assertion_ids: JSP:SPEC:300
- *
+ *
+ * @assertion_ids: PAGES:SPEC:300
+ *
* @test_Strategy: [BOMLegalCharacterEncoding] Verify that when using a BOM,
- * it is legal to describe the character encoding in a JSP page-encoding
+ * it is legal to describe the character encoding in a Jakarta Pages page-encoding
* configuration element.
*/
@Test
@@ -440,9 +439,9 @@ public void i18nBomLegalCharacterEncodingTest1() throws Exception {
/*
* @testName: i18nBomLegalCharacterEncodingTest2
- *
- * @assertion_ids: JSP:SPEC:300
- *
+ *
+ * @assertion_ids: PAGES:SPEC:300
+ *
* @test_Strategy: [BOMLegalCharacterEncoding] Verify that when using a BOM,
* it is legal to describe the character encoding in the pageEncoding
* attribute of a page directive.
@@ -461,9 +460,9 @@ public void i18nBomLegalCharacterEncodingTest2() throws Exception {
/*
* @testName: i18nBomErrorReportingTest1
- *
- * @assertion_ids: JSP:SPEC:318
- *
+ *
+ * @assertion_ids: PAGES:SPEC:318
+ *
* @test_Strategy: [BOMErrorReporting] Verify that when using a BOM, an error
* results when the encoding specified by page-encoding configuration element
* whose URL matches the page does not match the encoding indicated by the
@@ -480,9 +479,9 @@ public void i18nBomErrorReportingTest1() throws Exception {
/*
* @testName: i18nBomErrorReportingTest2
- *
- * @assertion_ids: JSP:SPEC:318
- *
+ *
+ * @assertion_ids: PAGES:SPEC:318
+ *
* @test_Strategy: [BOMErrorReporting] Verify that when using a BOM, an error
* results when the encoding specified by the pageEncoding attribute of a page
* directive does not match the encoding indicated by the BOM.
@@ -498,9 +497,9 @@ public void i18nBomErrorReportingTest2() throws Exception {
/*
* @testName: i18nBomErrorReportingTest3
- *
- * @assertion_ids: JSP:SPEC:318
- *
+ *
+ * @assertion_ids: PAGES:SPEC:318
+ *
* @test_Strategy: [BOMErrorReporting] Verify that when using a BOM, an error
* results when the encoding specified by the pageEncoding attribute of a tag
* directive does not match the encoding indicated by the BOM.
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/jspdocument/elements/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/jspdocument/elements/URLClientIT.java
index 32dc7d47..3b9f91b5 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/jspdocument/elements/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/jspdocument/elements/URLClientIT.java
@@ -74,7 +74,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: negativeJspRootTest
*
- * @assertion_ids: JSP:SPEC:177; JSP:SPEC:173.1
+ * @assertion_ids: PAGES:SPEC:177; PAGES:SPEC:173.1
*
* @test_Strategy: use jsp:root not as the top element of a jsp document.
* jsp-property-group config overrides other determiniations.
@@ -96,7 +96,7 @@ public void negativeJspRootTest() throws Exception {
/*
* @testName: jspRootPrefixTest
*
- * @assertion_ids: JSP:SPEC:175
+ * @assertion_ids: PAGES:SPEC:175
*
* @test_Strategy: use a different prefix abc
*/
@@ -113,7 +113,7 @@ public void jspRootPrefixTest() throws Exception {
/*
* @testName: directiveIncludeLocationTest
*
- * @assertion_ids: JSP:SPEC:179.1; JSP:SPEC:179; JSP:SPEC:179.3
+ * @assertion_ids: PAGES:SPEC:179.1; PAGES:SPEC:179; PAGES:SPEC:179.3
*
* @test_Strategy: use jsp:directive.include anywhere within a jsp document.
*/
@@ -131,7 +131,7 @@ public void directiveIncludeLocationTest() throws Exception {
/*
* @testName: directiveIncludeInJspPageTest
*
- * @assertion_ids: JSP:SPEC:179.5
+ * @assertion_ids: PAGES:SPEC:179.5
*
* @test_Strategy: use jsp:directive.include in a jsp page
*/
@@ -149,7 +149,7 @@ public void directiveIncludeInJspPageTest() throws Exception {
/*
* @testName: directivePageInJspPageTest
*
- * @assertion_ids: JSP:SPEC:178.39
+ * @assertion_ids: PAGES:SPEC:178.39
*
* @test_Strategy: use jsp:directive.page in a jsp page
*/
@@ -167,7 +167,7 @@ public void directivePageInJspPageTest() throws Exception {
/*
* @testName: scriptingTest
*
- * @assertion_ids: JSP:SPEC:180; JSP:SPEC:181; JSP:SPEC:182
+ * @assertion_ids: PAGES:SPEC:180; PAGES:SPEC:181; PAGES:SPEC:182
*
* @test_Strategy: use jsp:declaration, jsp:scriptlet, and jsp:expression in a
* jsp document.
@@ -186,7 +186,7 @@ public void scriptingTest() throws Exception {
/*
* @testName: scriptingInJspPageTest
*
- * @assertion_ids: JSP:SPEC:180.4; JSP:SPEC:181.2; JSP:SPEC:182.5
+ * @assertion_ids: PAGES:SPEC:180.4; PAGES:SPEC:181.2; PAGES:SPEC:182.5
*
* @test_Strategy: use jsp:declaration, jsp:scriptlet, and jsp:expression in a
* jsp page.
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/jspdocument/general/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/jspdocument/general/URLClientIT.java
index 0f7b2fc4..206f7656 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/jspdocument/general/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/jspdocument/general/URLClientIT.java
@@ -72,7 +72,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: negativeWellFormednessTest
*
- * @assertion_ids: JSP:SPEC:173.4
+ * @assertion_ids: PAGES:SPEC:173.4
*
* @test_Strategy: access a jsp document that is not well-formed.
*/
@@ -89,7 +89,7 @@ public void negativeWellFormednessTest() throws Exception {
/*
* @testName: identifyByJspRootTest
*
- * @assertion_ids: JSP:SPEC:173; JSP:SPEC:173.3
+ * @assertion_ids: PAGES:SPEC:173; PAGES:SPEC:173.3
*
* @test_Strategy: access a jsp page that has a jsp:root as top element
*/
@@ -106,7 +106,7 @@ public void identifyByJspRootTest() throws Exception {
/*
* @testName: identifyByExtensionTest
*
- * @assertion_ids: JSP:SPEC:173; JSP:SPEC:173.2; JSP:SPEC:176
+ * @assertion_ids: PAGES:SPEC:173; PAGES:SPEC:173.2; PAGES:SPEC:176
*
* @test_Strategy: identify a jsp document by .jspx extension a jsp document
* does not need to have jsp:root
@@ -124,7 +124,7 @@ public void identifyByExtensionTest() throws Exception {
/*
* @testName: identifyByConfigTest
*
- * @assertion_ids: JSP:SPEC:173; JSP:SPEC:173.1; JSP:SPEC:176
+ * @assertion_ids: PAGES:SPEC:173; PAGES:SPEC:173.1; PAGES:SPEC:176
*
* @test_Strategy: identify a jsp document by jsp-property-group via is-xml a
* jsp document does not need to have jsp:root
@@ -142,7 +142,7 @@ public void identifyByConfigTest() throws Exception {
/*
* @testName: negativeDTDValidationTest
*
- * @assertion_ids: JSP:SPEC:260
+ * @assertion_ids: PAGES:SPEC:260
*
* @test_Strategy: access an invalid jsp document and expect translation
* error.
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/misc/precompilation/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/misc/precompilation/URLClientIT.java
index 5e843139..e1d286e2 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/misc/precompilation/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/misc/precompilation/URLClientIT.java
@@ -68,7 +68,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: precompileNoValueTest
*
- * @assertion_ids: JSP:SPEC:244.1.4
+ * @assertion_ids: PAGES:SPEC:244.1.4
*
* @test_Strategy: Validate that no response body is returned when
* jsp_precompile has no value.
@@ -87,7 +87,7 @@ public void precompileNoValueTest() throws Exception {
/*
* @testName: precompileFalseTest
*
- * @assertion_ids: JSP:SPEC:244.1.2
+ * @assertion_ids: PAGES:SPEC:244.1.2
*
* @test_Strategy: Validate that no response body is returned when
* jsp_precompile is set to false.
@@ -106,7 +106,7 @@ public void precompileFalseTest() throws Exception {
/*
* @testName: precompileTrueTest
*
- * @assertion_ids: JSP:SPEC:244.1.1
+ * @assertion_ids: PAGES:SPEC:244.1.1
*
* @test_Strategy: Validate that no response body is returned when
* jsp_precompile is set to true.
@@ -125,7 +125,7 @@ public void precompileTrueTest() throws Exception {
/*
* @testName: precompileNegativeTest
*
- * @assertion_ids: JSP:SPEC:244.1.5
+ * @assertion_ids: PAGES:SPEC:244.1.5
*
* @test_Strategy: Set the jsp_precompile request paramter to a non valid
* value and validate that a 500 error occurs.
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/tagfiles/directives/attribute20/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/tagfiles/directives/attribute20/URLClientIT.java
index f79821a7..0fe4e4a0 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/tagfiles/directives/attribute20/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/tagfiles/directives/attribute20/URLClientIT.java
@@ -105,7 +105,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: negativeName1Test
*
- * @assertion_ids: JSP:SPEC:230.2
+ * @assertion_ids: PAGES:SPEC:230.2
*
* @test_Strategy: A translation error must result if more than one attribute
* directive appears in the same translation unit with the same name
@@ -123,7 +123,7 @@ public void negativeName1Test() throws Exception {
/*
* @testName: negativeName1IncludeTest
*
- * @assertion_ids: JSP:SPEC:230.2
+ * @assertion_ids: PAGES:SPEC:230.2
*
* @test_Strategy: A translation error must result if more than one attribute
* directive appears in the same translation unit with the same name
@@ -141,7 +141,7 @@ public void negativeName1IncludeTest() throws Exception {
/*
* @testName: negativeName2Test
*
- * @assertion_ids: JSP:SPEC:230.1.2
+ * @assertion_ids: PAGES:SPEC:230.1.2
*
* @test_Strategy: A translation error must result if the attribute name
* equals to the name-given of a variable.
@@ -159,7 +159,7 @@ public void negativeName2Test() throws Exception {
/*
* @testName: negativeName2IncludeTest
*
- * @assertion_ids: JSP:SPEC:230.1.2
+ * @assertion_ids: PAGES:SPEC:230.1.2
*
* @test_Strategy: A translation error must result if the attribute name
* equals to the name-given of a variable.
@@ -177,7 +177,7 @@ public void negativeName2IncludeTest() throws Exception {
/*
* @testName: negativeName3Test
*
- * @assertion_ids: JSP:SPEC:230.1.2
+ * @assertion_ids: PAGES:SPEC:230.1.2
*
* @test_Strategy: A translation error must result if the attribute name
* equals to dynamic-attributes of a tag directive.
@@ -195,7 +195,7 @@ public void negativeName3Test() throws Exception {
/*
* @testName: negativeName3IncludeTest
*
- * @assertion_ids: JSP:SPEC:230.1.2
+ * @assertion_ids: PAGES:SPEC:230.1.2
*
* @test_Strategy: A translation error must result if the attribute name
* equals to dynamic-attributes of a tag directive.
@@ -213,7 +213,7 @@ public void negativeName3IncludeTest() throws Exception {
/*
* @testName: defaultRequiredTest
*
- * @assertion_ids: JSP:SPEC:230.3.3
+ * @assertion_ids: PAGES:SPEC:230.3.3
*
* @test_Strategy: required default is false
*/
@@ -230,7 +230,7 @@ public void defaultRequiredTest() throws Exception {
/*
* @testName: defaultTypeTest
*
- * @assertion_ids: JSP:SPEC:230.6.1
+ * @assertion_ids: PAGES:SPEC:230.6.1
*
* @test_Strategy: type defaults to java.lang.String, and also verify an Float
* type attribute.
@@ -248,7 +248,7 @@ public void defaultTypeTest() throws Exception {
/*
* @testName: negativeTypeTest
*
- * @assertion_ids: JSP:SPEC:230.6.2
+ * @assertion_ids: PAGES:SPEC:230.6.2
*
* @test_Strategy: A translation error must result if the type is a primitive
*/
@@ -265,7 +265,7 @@ public void negativeTypeTest() throws Exception {
/*
* @testName: negativeFragmentTypeTest
*
- * @assertion_ids: JSP:SPEC:230.4.5
+ * @assertion_ids: PAGES:SPEC:230.4.5
*
* @test_Strategy: A translation error must result if fragment is true and
* type is specified
@@ -283,7 +283,7 @@ public void negativeFragmentTypeTest() throws Exception {
/*
* @testName: negativeFragmentRtexprvalueTest
*
- * @assertion_ids: JSP:SPEC:230.4.2.1
+ * @assertion_ids: PAGES:SPEC:230.4.2.1
*
* @test_Strategy: A translation error must result if fragment is true and
* rtexprvalue is specified
@@ -301,7 +301,7 @@ public void negativeFragmentRtexprvalueTest() throws Exception {
/*
* @testName: defaultFragmentTest
*
- * @assertion_ids: JSP:SPEC:230
+ * @assertion_ids: PAGES:SPEC:230
*
* @test_Strategy: fragment defaults to false. Also verifies the default attr
* type is String.
@@ -319,7 +319,7 @@ public void defaultFragmentTest() throws Exception {
/*
* @testName: defaultRtexprvalueTest
*
- * @assertion_ids: JSP:SPEC:230
+ * @assertion_ids: PAGES:SPEC:230
*
* @test_Strategy: rtexprvalue defaults to true.
*/
@@ -336,10 +336,10 @@ public void defaultRtexprvalueTest() throws Exception {
/*
* @testName: deferredValueMinimumJspVersionTest
*
- * @assertion_ids: JSP:SPEC:230.8.3
+ * @assertion_ids: PAGES:SPEC:230.8.3
*
* @test_Strategy: [deferredValueMinimumJspVersion] The deferredValue
- * attribute causes a translation error if specified in a tag file with a JSP
+ * attribute causes a translation error if specified in a tag file with a Jakarta Pages
* version less than 2.1.
*/
@@ -355,10 +355,10 @@ public void deferredValueMinimumJspVersionTest() throws Exception {
/*
* @testName: deferredValueTypeMinimumJspVersionTest
*
- * @assertion_ids: JSP:SPEC:230.9.4
+ * @assertion_ids: PAGES:SPEC:230.9.4
*
* @test_Strategy: [deferredValueTypeMinimumJspVersion] The deferredValueType
- * attribute causes a translation error if specified in a tag file with a JSP
+ * attribute causes a translation error if specified in a tag file with a Jakarta Pages
* version less than 2.1.
*/
@@ -374,10 +374,10 @@ public void deferredValueTypeMinimumJspVersionTest() throws Exception {
/*
* @testName: deferredMethodMinimumJspVersionTest
*
- * @assertion_ids: JSP:SPEC:230.10.2
+ * @assertion_ids: PAGES:SPEC:230.10.2
*
* @test_Strategy: [deferredMethodMinimumJspVersion] The deferredMethod
- * attribute causes a translation error if specified in a tag file with a JSP
+ * attribute causes a translation error if specified in a tag file with a Jakarta Pages
* version less than 2.1.
*/
@@ -393,11 +393,11 @@ public void deferredMethodMinimumJspVersionTest() throws Exception {
/*
* @testName: deferredMethodSignatureMinimumJspVersionTest
*
- * @assertion_ids: JSP:SPEC:230.11.3
+ * @assertion_ids: PAGES:SPEC:230.11.3
*
* @test_Strategy: [deferredMethodSignatureMinimumJspVersion] The
* deferredMethodSignature attribute causes a translation error if specified
- * in a tag file with a JSP version less than 2.1.
+ * in a tag file with a Jakarta Pages version less than 2.1.
*/
@Test
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/tagfiles/directives/attribute21/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/tagfiles/directives/attribute21/URLClientIT.java
index 5a3123a2..b01079b1 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/tagfiles/directives/attribute21/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/tagfiles/directives/attribute21/URLClientIT.java
@@ -87,7 +87,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: onlyOneOfDeferredValueOrDeferredMethodTest
*
- * @assertion_ids: JSP:SPEC:230.8.1
+ * @assertion_ids: PAGES:SPEC:230.8.1
*
* @test_Strategy: [OnlyOneOfDeferredValueOrMethod] A translation error must
* result when both deferredValue and deferredMethod appear in the same tag.
@@ -105,7 +105,7 @@ public void onlyOneOfDeferredValueOrDeferredMethodTest() throws Exception {
/*
* @testName: defaultDeferredValue1Test
*
- * @assertion_ids: JSP:SPEC:230.8.2
+ * @assertion_ids: PAGES:SPEC:230.8.2
*
* @test_Strategy: [DefaultDeferredValue] Specify an attribute tag with no
* deferredValue attribute and a deferredValueType attribute. Verify that the
@@ -123,7 +123,7 @@ public void defaultDeferredValue1Test() throws Exception {
/*
* @testName: defaultDeferredValue2Test
*
- * @assertion_ids: JSP:SPEC:230.8.2
+ * @assertion_ids: PAGES:SPEC:230.8.2
*
* @test_Strategy: [DefaultDeferredValue] Specify an attribute tag with no
* deferredValue attribute and no deferredValueType attribute. Verify that the
@@ -142,7 +142,7 @@ public void defaultDeferredValue2Test() throws Exception {
/*
* @testName: deferredValueTypeNotSpecifiedTest
*
- * @assertion_ids: JSP:SPEC:230.9.1
+ * @assertion_ids: PAGES:SPEC:230.9.1
*
* @test_Strategy: [DeferredValueTypeNotSpecified] Specify an attribute tag
* with a deferredValue attribute and no deferredValueType attribute. Verify
@@ -161,7 +161,7 @@ public void deferredValueTypeNotSpecifiedTest() throws Exception {
/*
* @testName: bothDeferredValueTypeAndDeferredValueTest
*
- * @assertion_ids: JSP:SPEC:230.9.2
+ * @assertion_ids: PAGES:SPEC:230.9.2
*
* @test_Strategy: [BothDeferredValueTypeAndDeferredValue] A translation error
* must result when both deferredValueType and and deferredValue appear in the
@@ -179,7 +179,7 @@ public void bothDeferredValueTypeAndDeferredValueTest() throws Exception {
/*
* @testName: defaultDeferredMethod1Test
*
- * @assertion_ids: JSP:SPEC:230.10.1
+ * @assertion_ids: PAGES:SPEC:230.10.1
*
* @test_Strategy: [DefaultDeferredMethod] Specify an attribute tag with no
* deferredMethod attribute and a deferredMethodSignature attribute. Verify
@@ -197,7 +197,7 @@ public void defaultDeferredMethod1Test() throws Exception {
/*
* @testName: defaultDeferredMethod2Test
*
- * @assertion_ids: JSP:SPEC:230.10.1
+ * @assertion_ids: PAGES:SPEC:230.10.1
*
* @test_Strategy: [DefaultDeferredMethod] Specify an attribute tag with no
* deferredMethod attribute and no deferredMethodSignature attribute. Verify
@@ -216,7 +216,7 @@ public void defaultDeferredMethod2Test() throws Exception {
/*
* @testName: bothDeferredMethodAndSignatureTest
*
- * @assertion_ids: JSP:SPEC:230.11.1
+ * @assertion_ids: PAGES:SPEC:230.11.1
*
* @test_Strategy: [BothDeferredMethodAndSignature] A translation error must
* result when both deferredMethodSignature and and deferredMethod appear in
@@ -234,7 +234,7 @@ public void bothDeferredMethodAndSignatureTest() throws Exception {
/*
* @testName: defaultDeferredMethodSignatureTest
*
- * @assertion_ids: JSP:SPEC:230.11.2
+ * @assertion_ids: PAGES:SPEC:230.11.2
*
* @test_Strategy: [DefaultDeferredMethodSignature] Specify an attribute tag
* with a deferredMethod attribute set to true and no
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/tagfiles/directives/general/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/tagfiles/directives/general/URLClientIT.java
index 13ec0f08..2d89b6ee 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/tagfiles/directives/general/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/tagfiles/directives/general/URLClientIT.java
@@ -92,7 +92,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: negativePageDirectiveTest
*
- * @assertion_ids: JSP:SPEC:223
+ * @assertion_ids: PAGES:SPEC:223
*
* @test_Strategy: If a page directive is used in a tag file, a translation
* error must result.
@@ -110,7 +110,7 @@ public void negativePageDirectiveTest() throws Exception {
/*
* @testName: negativeTagDirectiveTest
*
- * @assertion_ids: JSP:SPEC:226
+ * @assertion_ids: PAGES:SPEC:226
*
* @test_Strategy: If a tag directive is used in a jsp page, a translation
* error must result.
@@ -128,7 +128,7 @@ public void negativeTagDirectiveTest() throws Exception {
/*
* @testName: negativeAttributeDirectiveTest
*
- * @assertion_ids: JSP:SPEC:227
+ * @assertion_ids: PAGES:SPEC:227
*
* @test_Strategy: If a attribute directive is used in a jsp page, a
* translation error must result.
@@ -146,7 +146,7 @@ public void negativeAttributeDirectiveTest() throws Exception {
/*
* @testName: negativeVariableDirectiveTest
*
- * @assertion_ids: JSP:SPEC:228
+ * @assertion_ids: PAGES:SPEC:228
*
* @test_Strategy: If a variable directive is used in a jsp page, a
* translation error must result.
@@ -232,7 +232,7 @@ public void positiveTaglibTest() throws Exception {
/*
* @testName: errorOnELNotFoundFalseTest
*
- * @assertion_ids: JSP:SPEC:320
+ * @assertion_ids: PAGES:SPEC:320
*
* @test_Strategy: [ErrorOnELNotFoundTagDirective] Verify that when the
* ErrorOnELNotFound tag directive attribute is set to false, a reference
@@ -250,7 +250,7 @@ public void errorOnELNotFoundFalseTest()
/*
* @testName: errorOnELNotFoundTrueTest
*
- * @assertion_ids: JSP:SPEC:320
+ * @assertion_ids: PAGES:SPEC:320
*
* @test_Strategy: [ErrorOnELNotFoundTagDirective] Verify that when the
* ErrorOnELNotFound tag directive attribute is set to false, a reference
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/tagfiles/directives/tag20/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/tagfiles/directives/tag20/URLClientIT.java
index f3b2ba6d..948aad46 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/tagfiles/directives/tag20/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/tagfiles/directives/tag20/URLClientIT.java
@@ -27,7 +27,6 @@
import org.jboss.arquillian.container.test.api.Deployment;
import org.jboss.arquillian.junit5.ArquillianExtension;
-import org.jboss.shrinkwrap.api.Filters;
import org.jboss.shrinkwrap.api.ShrinkWrap;
import org.jboss.shrinkwrap.api.spec.WebArchive;
import org.junit.jupiter.api.Test;
@@ -51,7 +50,7 @@ public URLClientIT() throws Exception {
@Deployment(testable = false)
public static WebArchive createDeployment() throws IOException {
-
+
String packagePath = URLClientIT.class.getPackageName().replace(".", "/");
WebArchive archive = ShrinkWrap.create(WebArchive.class, "jsp_tagfile_directives_tag20_web.war");
archive.setWebXML(URLClientIT.class.getClassLoader().getResource(packagePath+"/jsp_tagfile_directives_tag20_web.xml"));
@@ -118,9 +117,9 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: negativeDuplicateIsELIgnoredFatalTranslationErrorTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: Declare a tag directive with two isELIgnored attributes.
*/
@@ -136,9 +135,9 @@ public void negativeDuplicateIsELIgnoredFatalTranslationErrorTest()
/*
* @testName: positiveImportTest
- *
- * @assertion_ids: JSP:SPEC:229.19
- *
+ *
+ * @assertion_ids: PAGES:SPEC:229.19
+ *
* @test_Strategy: Use the import attribute to import 'java.util.ArrayList'.
* Validated that a ArrayList object can be created and used.
*/
@@ -154,9 +153,9 @@ public void positiveImportTest() throws Exception {
/*
* @testName: implicitImportLangTest
- *
- * @assertion_ids: JSP:SPEC:229.19.1
- *
+ *
+ * @assertion_ids: PAGES:SPEC:229.19.1
+ *
* @test_Strategy: Validate that classes from the java.lang package are
* implicitly imported by creating and using a java.lang.Integer object.
*/
@@ -172,9 +171,9 @@ public void implicitImportLangTest() throws Exception {
/*
* @testName: implicitImportJspTest
- *
- * @assertion_ids: JSP:SPEC:229.19.1
- *
+ *
+ * @assertion_ids: PAGES:SPEC:229.19.1
+ *
* @test_Strategy: Validate that classes from the jakarta.servlet.jsp package
* are implicitly imported by calling JspFactory.getDefaultFactory() method.
*/
@@ -190,9 +189,9 @@ public void implicitImportJspTest() throws Exception {
/*
* @testName: implicitImportServletTest
- *
- * @assertion_ids: JSP:SPEC:229.19.1
- *
+ *
+ * @assertion_ids: PAGES:SPEC:229.19.1
+ *
* @test_Strategy: Validate that classes from the jakarta.servlet package are
* implicitly imported by creating and using an instance of RequestDispatcher.
*/
@@ -208,9 +207,9 @@ public void implicitImportServletTest() throws Exception {
/*
* @testName: implicitImportHttpTest
- *
- * @assertion_ids: JSP:SPEC:229.19.1
- *
+ *
+ * @assertion_ids: PAGES:SPEC:229.19.1
+ *
* @test_Strategy: Validate that classes from the jakarta.servlet.http package
* are implicitly imported by creating and using an instance of Cookie.
*/
@@ -226,9 +225,9 @@ public void implicitImportHttpTest() throws Exception {
/*
* @testName: positiveMultipleImportTest
- *
- * @assertion_ids: JSP:SPEC:229.19.2
- *
+ *
+ * @assertion_ids: PAGES:SPEC:229.19.2
+ *
* @test_Strategy: Declare a tag directive with two import attributes.
*
*/
@@ -244,9 +243,9 @@ public void positiveMultipleImportTest() throws Exception {
/*
* @testName: negativeMultiplePageEncodingTest
- *
- * @assertion_ids: JSP:SPEC:232.1.21
- *
+ *
+ * @assertion_ids: PAGES:SPEC:232.1.21
+ *
* @test_Strategy: Declare a tag directive with two pageEncoding attributes.
*
*/
@@ -262,9 +261,9 @@ public void negativeMultiplePageEncodingTest() throws Exception {
/*
* @testName: positiveLangTest
- *
- * @assertion_ids: JSP:SPEC:229.17
- *
+ *
+ * @assertion_ids: PAGES:SPEC:229.17
+ *
* @test_Strategy: Validate that the language attribute can be set to "java"
* without an error.
*/
@@ -280,9 +279,9 @@ public void positiveLangTest() throws Exception {
/*
* @testName: negativeDuplicateLanguageFatalTranslationErrorTest
- *
- * @assertion_ids: JSP:SPEC:229.18
- *
+ *
+ * @assertion_ids: PAGES:SPEC:229.18
+ *
* @test_Strategy: Declare a tag directive with two language attributes. of
* different values. Validate that a fatal translation error occurs.
*/
@@ -299,10 +298,10 @@ public void negativeDuplicateLanguageFatalTranslationErrorTest()
/*
* @testName: negativeBodyContentTest
- *
- * @assertion_ids: JSP:SPEC:232.1.5.5
- *
- * @test_Strategy: A translation error will result if JSP is used as tag
+ *
+ * @assertion_ids: PAGES:SPEC:232.1.5.5
+ *
+ * @test_Strategy: A translation error will result if Jakarta Pages page is used as tag
* directive body-content
*/
@@ -317,9 +316,9 @@ public void negativeBodyContentTest() throws Exception {
/*
* @testName: positiveDuplicateAttributesTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: There shall be only one occurrence of any attribute /value
* defined in a given translation unit, unless the values for the duplicate
* attributes are identical for all occurences.
@@ -336,9 +335,9 @@ public void positiveDuplicateAttributesTest() throws Exception {
/*
* @testName: negativeUnrecognizedAttributeTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: Unrecognized attributes or values result in fatal
* translation error.
*/
@@ -354,9 +353,9 @@ public void negativeUnrecognizedAttributeTest() throws Exception {
/*
* @testName: negativeDuplicateDisplayNameTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: other such multiple attribute/value (re) definitions result
* in a fatal translation error if the value do not match.
*/
@@ -372,9 +371,9 @@ public void negativeDuplicateDisplayNameTest() throws Exception {
/*
* @testName: negativeDuplicateBodyContentTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: other such multiple attribute/value (re) definitions result
* in a fatal translation error if the value do not match.
*/
@@ -390,9 +389,9 @@ public void negativeDuplicateBodyContentTest() throws Exception {
/*
* @testName: negativeDuplicateDynamicAttributesTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: other such multiple attribute/value (re) definitions result
* in a fatal translation error if the value do not match.
*/
@@ -408,9 +407,9 @@ public void negativeDuplicateDynamicAttributesTest() throws Exception {
/*
* @testName: negativeDuplicateDescriptionTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: other such multiple attribute/value (re) definitions result
* in a fatal translation error if the value do not match.
*/
@@ -426,9 +425,9 @@ public void negativeDuplicateDescriptionTest() throws Exception {
/*
* @testName: negativeDuplicateExampleTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: other such multiple attribute/value (re) definitions result
* in a fatal translation error if the value do not match.
*/
@@ -444,9 +443,9 @@ public void negativeDuplicateExampleTest() throws Exception {
/*
* @testName: negativeDuplicateSmallIconTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: other such multiple attribute/value (re) definitions result
* in a fatal translation error if the value do not match.
*/
@@ -462,9 +461,9 @@ public void negativeDuplicateSmallIconTest() throws Exception {
/*
* @testName: negativeDuplicateLargeIconTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: other such multiple attribute/value (re) definitions result
* in a fatal translation error if the value do not match.
*/
@@ -480,9 +479,9 @@ public void negativeDuplicateLargeIconTest() throws Exception {
/*
* @testName: dynamicAttributesNoUriTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: Only dynamic attributes with no uri are to be present in
* the Map; all other are ignored.
*/
@@ -499,12 +498,12 @@ public void dynamicAttributesNoUriTest() throws Exception {
/*
* @testName: deferredValueMinimumJspVersionTest
- *
- * @assertion_ids: JSP:SPEC:230.8.3
- *
+ *
+ * @assertion_ids: PAGES:SPEC:230.8.3
+ *
* @test_Strategy: [deferredValueMinimumJspVersion] Show that the use of the
* deferredValue attribute for the tag directive causes a translation error if
- * specified in a tag file with a JSP version less than 2.1.
+ * specified in a tag file with a Jakarta Pages version less than 2.1.
*/
@Test
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/tagfiles/directives/tag21/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/tagfiles/directives/tag21/URLClientIT.java
index 7636d9d1..9d13734b 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/tagfiles/directives/tag21/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/tagfiles/directives/tag21/URLClientIT.java
@@ -82,7 +82,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: deferredSyntaxAllowedAsLiteralFalseTemplateTextTest
*
- * @assertion_ids: JSP:SPEC:229.26
+ * @assertion_ids: PAGES:SPEC:229.26
*
* @test_Strategy: [DeferredSyntaxAllowedAsLiteralTagDirectiveAttribute]
* Verify that when the DeferredSyntaxAllowedAsLiteral tag directive attribute
@@ -102,7 +102,7 @@ public void deferredSyntaxAllowedAsLiteralFalseTemplateTextTest()
/*
* @testName: deferredSyntaxAllowedAsLiteralTrueTemplateTextTest
*
- * @assertion_ids: JSP:SPEC:229.26
+ * @assertion_ids: PAGES:SPEC:229.26
*
* @test_Strategy: [DeferredSyntaxAllowedAsLiteralTagDirectiveAttribute]
* Verify that when the DeferredSyntaxAllowedAsLiteral tag directive attribute
@@ -122,7 +122,7 @@ public void deferredSyntaxAllowedAsLiteralTrueTemplateTextTest()
/*
* @testName: deferredSyntaxAllowedAsLiteralFalseActionTest
*
- * @assertion_ids: JSP:SPEC:229.26
+ * @assertion_ids: PAGES:SPEC:229.26
*
* @test_Strategy: [DeferredSyntaxAllowedAsLiteralTagDirectiveAttribute]
* Verify that when the DeferredSyntaxAllowedAsLiteral tag directive attribute
@@ -141,7 +141,7 @@ public void deferredSyntaxAllowedAsLiteralFalseActionTest() throws Exception {
/*
* @testName: deferredSyntaxAllowedAsLiteralTrueActionTest
*
- * @assertion_ids: JSP:SPEC:229.26
+ * @assertion_ids: PAGES:SPEC:229.26
*
* @test_Strategy: [DeferredSyntaxAllowedAsLiteralTagDirectiveAttribute]
* Verify that when the DeferredSyntaxAllowedAsLiteral tag directive attribute
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/tagfiles/packaging/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/tagfiles/packaging/URLClientIT.java
index f76ebf8c..92d19105 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/tagfiles/packaging/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/tagfiles/packaging/URLClientIT.java
@@ -109,7 +109,7 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: jspTagFilePackagedJarTest
*
- * @assertion_ids: JSP:SPEC:220.1
+ * @assertion_ids: PAGES:SPEC:220.1
*
* @test_Strategy: Validate that tag files packaged in a JAR file and
* referenced in a TLD, can be recognized by the container and invoked within
@@ -126,7 +126,7 @@ public void jspTagFilePackagedJarTest() throws Exception {
/*
* @testName: jspTagFilePackagedJarIgnoredTagTest
*
- * @assertion_ids: JSP:SPEC:220.2
+ * @assertion_ids: PAGES:SPEC:220.2
*
* @test_Strategy: Validate that if a Tag file is packaged in a JAR but not
* referenced by a TLD, the container ignores the tag file. Since the Page
@@ -143,7 +143,7 @@ public void jspTagFilePackagedJarIgnoredTagTest() throws Exception {
/*
* @testName: jspTagFilePackagedWarTest
*
- * @assertion_ids: JSP:SPEC:221
+ * @assertion_ids: PAGES:SPEC:221
*
* @test_Strategy: Validate that tag files can be properly detected by the
* container and that they can be used in a Page.
@@ -175,9 +175,9 @@ public void jspTagFilePackagedWarTldTest() throws Exception {
/*
* @testName: implicitTldMinimumJspVersionTest
*
- * @assertion_ids: JSP:SPEC:311
+ * @assertion_ids: PAGES:SPEC:311
*
- * @test_Strategy: [ImplicitTldMinimumJspVersion] Show that if the JSP version
+ * @test_Strategy: [ImplicitTldMinimumJspVersion] Show that if the Jakarta Pages version
* specified in an implicit.tld file is less than 2.0 a translation error will
* result.
*/
@@ -192,9 +192,9 @@ public void implicitTldMinimumJspVersionTest() throws Exception {
/*
* @testName: implicitTldAdditionalElementsTest
*
- * @assertion_ids: JSP:SPEC:310
+ * @assertion_ids: PAGES:SPEC:310
*
- * @test_Strategy: [ImplicitTldAdditionalElements] Show that if the JSP
+ * @test_Strategy: [ImplicitTldAdditionalElements] Show that if the Jakarta Pages
* version specified in an implicit.tld file is less than 2.0 a translation
* error will result.
*/
@@ -209,10 +209,10 @@ public void implicitTldAdditionalElementsTest() throws Exception {
/*
* @testName: tldImplicitTldJspVersionNotMatchTest
*
- * @assertion_ids: JSP:SPEC:313
+ * @assertion_ids: PAGES:SPEC:313
*
* @test_Strategy: [TldImplicitTldJspVersionNotMatch] Show that if a tag file
- * is referenced by both a TLD and an implicit TLD, the JSP versions of the
+ * is referenced by both a TLD and an implicit TLD, the Jakarta Pages versions of the
* TLD and implicit TLD do not need to match.
*/
@Test
@@ -226,9 +226,9 @@ public void tldImplicitTldJspVersionNotMatchTest() throws Exception {
/*
* @testName: implicitTldReservedName20Test
*
- * @assertion_ids: JSP:SPEC:308
+ * @assertion_ids: PAGES:SPEC:308
*
- * @test_Strategy: [ImplicitTldReservedName] The JSP version of an implicit
+ * @test_Strategy: [ImplicitTldReservedName] The Jakarta Pages 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. Verify this for version 2.0 by embedding '{#' in an
@@ -245,9 +245,9 @@ public void implicitTldReservedName20Test() throws Exception {
/*
* @testName: implicitTldReservedName21Test
*
- * @assertion_ids: JSP:SPEC:308
+ * @assertion_ids: PAGES:SPEC:308
*
- * @test_Strategy: [ImplicitTldReservedName] The JSP version of an implicit
+ * @test_Strategy: [ImplicitTldReservedName] The Jakarta Pages 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. Verify this for version 2.1 by embedding '{#' in an
@@ -264,7 +264,7 @@ public void implicitTldReservedName21Test() throws Exception {
/*
* @testName: implicitTldDefaultJspVersionTest
*
- * @assertion_ids: JSP:SPEC:307
+ * @assertion_ids: PAGES:SPEC:307
*
* @test_Strategy: [ImplicitTldDefaultJspVersion] Show that the jsp version of
* an implicit tag library defaults to 2.0 by embedding an unescaped '#{"
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/tagfiles/semantics/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/tagfiles/semantics/URLClientIT.java
index 8393e3de..ffdc369e 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/tagfiles/semantics/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/tagfiles/semantics/URLClientIT.java
@@ -91,7 +91,7 @@ public static WebArchive createDeployment() throws IOException {
*
* @assertion_ids: PENDING
*
- * @test_Strategy: Validate that the container properly creates a JSP Context
+ * @test_Strategy: Validate that the container properly creates a Jakarta Pages Context
* wrapper, an instance of PageContext, for the tag file. Validate that this
* wrapper is not the same JspContext as that of the invoking page (this
* includes validate of the jspContext scripting variable).
diff --git a/tck/src/main/java/ee/jakarta/tck/pages/spec/tldres/URLClientIT.java b/tck/src/main/java/ee/jakarta/tck/pages/spec/tldres/URLClientIT.java
index 57932231..61ae7091 100644
--- a/tck/src/main/java/ee/jakarta/tck/pages/spec/tldres/URLClientIT.java
+++ b/tck/src/main/java/ee/jakarta/tck/pages/spec/tldres/URLClientIT.java
@@ -30,7 +30,6 @@
import org.jboss.arquillian.container.test.api.Deployment;
import org.jboss.arquillian.junit5.ArquillianExtension;
-import org.jboss.shrinkwrap.api.Filters;
import org.jboss.shrinkwrap.api.ShrinkWrap;
import org.jboss.shrinkwrap.api.spec.JavaArchive;
import org.jboss.shrinkwrap.api.spec.WebArchive;
@@ -52,18 +51,18 @@ public URLClientIT() throws Exception {
@Deployment(testable = false)
public static WebArchive createDeployment() throws IOException {
-
+
String packagePath = URLClientIT.class.getPackageName().replace(".", "/");
WebArchive archive = ShrinkWrap.create(WebArchive.class, "jsp_tldres_web.war");
archive.addClasses(HSListenerWebInf.class, HSListenerWebInfSub.class,
UriTag.class, WebXmlTag.class);
archive.setWebXML(URLClientIT.class.getClassLoader().getResource(packagePath+"/jsp_tldres_web.xml"));
- archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/sub/webinfsub.tld", "sub/webinfsub.tld");
- archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tlds/uri.tld", "tlds/uri.tld");
- archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/webinfpres.tld", "webinfpres.tld");
- archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/webxml.tld", "webxml.tld");
- archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/a12.tld", "a12.tld");
+ archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/sub/webinfsub.tld", "sub/webinfsub.tld");
+ archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/tlds/uri.tld", "tlds/uri.tld");
+ archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/webinfpres.tld", "webinfpres.tld");
+ archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/webxml.tld", "webxml.tld");
+ archive.addAsWebInfResource(URLClientIT.class.getPackage(), "WEB-INF/a12.tld", "a12.tld");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/listenerTldTest.jsp")), "listenerTldTest.jsp");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/negativeJSPPrefix.jsp")), "negativeJSPPrefix.jsp");
@@ -77,7 +76,7 @@ public static WebArchive createDeployment() throws IOException {
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/TldResPathExplicitWebXmlTest.jsp")), "TldResPathExplicitWebXmlTest.jsp");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/TldResPathMultiTldTest.jsp")), "TldResPathMultiTldTest.jsp");
archive.add(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/TldResPathWebInfUriTest.jsp")), "TldResPathWebInfUriTest.jsp");
-
+
JavaArchive jsp11taglibJar = ShrinkWrap.create(JavaArchive.class, "jsp11taglib.jar");
jsp11taglibJar.addAsResource(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/taglib.tld")), "META-INF/taglib.tld");
jsp11taglibJar.addClass(Tld11Tag.class);
@@ -91,7 +90,7 @@ public static WebArchive createDeployment() throws IOException {
multitaglibJar.addAsResource(new UrlAsset(URLClientIT.class.getClassLoader().getResource(packagePath+"/multi2.tld")), "META-INF/tlds/multi2.tld");
multitaglibJar.addClasses(HSListenerMetaInf.class, HSListenerMetaInfSub.class, Multi1Tag.class, Multi2Tag.class);
-
+
archive.addAsLibrary(multitaglibJar);
return archive;
@@ -107,9 +106,9 @@ public static WebArchive createDeployment() throws IOException {
/*
* @testName: tldResourcePathJsp11Test
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: Validate that a taglibrary packaged as specified by the JSP
* 1.1 specification will be properly added to the containers taglib map and
* that the defined tag within can be used.
@@ -124,9 +123,9 @@ public void tldResourcePathJsp11Test() throws Exception {
/*
* @testName: tldResourcePathMultiTldJarTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: Validate the container can properly process a JAR
* containing multiple TLDs and adds the TLDs that are found containing a
* element to the taglib map.
@@ -142,9 +141,9 @@ public void tldResourcePathMultiTldJarTest() throws Exception {
/*
* @testName: tldResourcePathWebInfUriTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: Validate that if a TLD exists in the WEB-INF directory or
* some subdirectory thereof, and that TLD contains a element, the
* container will add that taglibrary to the taglibrary map.
@@ -159,9 +158,9 @@ public void tldResourcePathWebInfUriTest() throws Exception {
/*
* @testName: tldResourcePathWebXmlTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: Valdiate that the container adds any explicit taglibrary
* entries found in the deployment descriptor to the taglib map and that the
* tag or tags within can be properly used.
@@ -176,9 +175,9 @@ public void tldResourcePathWebXmlTest() throws Exception {
/*
* @testName: tldResourcePathDirectTldReference
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: Validate the TLD can be directly referenced in the taglib
* directive and that the tag(s) declared in this TLD can be properly used.
*/
@@ -192,9 +191,9 @@ public void tldResourcePathDirectTldReference() throws Exception {
/*
* @testName: tldExplicitWebXmlPrecedenceTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: Validate that tag library entries explicity defined in the
* web deployment descriptor (web.xml) have precedence over other tag
* libraries defined with the same URI.
@@ -209,9 +208,9 @@ public void tldExplicitWebXmlPrecedenceTest() throws Exception {
/*
* @testName: tldResPathRelativeUriTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: Validate a tag library can be resolved when referenced
* though a relative path (no leading '/'). No translation error should occur
* and the tag should be usable within the translation unit.
@@ -226,9 +225,9 @@ public void tldResPathRelativeUriTest() throws Exception {
/*
* @testName: tldResPathAbsUriNotFoundTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: Validate that if the uri attribute of the taglib directive
* is an absolute URI that is not present in the container's tag library map,
* that a translation time error is raised.
@@ -243,11 +242,11 @@ public void tldResPathAbsUriNotFoundTest() throws Exception {
/*
* @testName: tld12DefaultBodyContentTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: omit body-content in a 1.2 style tld and a container is
- * required to apply default JSP.
+ * required to apply the default of "JSP".
*/
@Test
@@ -261,9 +260,9 @@ public void tld12DefaultBodyContentTest() throws Exception {
/*
* @testName: negativeJSPPrefixTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: use jsp prefix for an element that is not a standard action
* and expect a translation error.
*/
@@ -280,9 +279,9 @@ public void negativeJSPPrefixTest() throws Exception {
/*
* @testName: listenerTldTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: A container is required to read listener element in all TLD
* files and treat them as extension to web.xml.
*/
@@ -299,9 +298,9 @@ public void listenerTldTest() throws Exception {
/*
* @testName: negativeTaglibAfterActionTest
- *
+ *
* @assertion_ids: PENDING
- *
+ *
* @test_Strategy: It is a fatal translation error for the taglib directive to
* appear after actions or functions using the prefix.
*/
diff --git a/tck/src/main/resources/ee/jakarta/tck/pages/signaturetest/jsp/sig-test.map b/tck/src/main/resources/ee/jakarta/tck/pages/signaturetest/jsp/sig-test.map
index 5a8f9676..98f9070e 100644
--- a/tck/src/main/resources/ee/jakarta/tck/pages/signaturetest/jsp/sig-test.map
+++ b/tck/src/main/resources/ee/jakarta/tck/pages/signaturetest/jsp/sig-test.map
@@ -16,13 +16,13 @@
#
###############################################################
-# The signature test mapping file for the JSP TCK. This file
+# The signature test mapping file for the Pages TCK. This file
# should be formatted as a standard java properties file. The
# name is the package name and the value is the version of the
# package that should be tested by the signature tests.
###############################################################
-# JSP
+# Pages
=======
jakarta.servlet.jsp=4.1
diff --git a/tck/src/main/resources/ee/jakarta/tck/pages/spec/configuration/elevaluation/jsp_config_eleval_web.xml b/tck/src/main/resources/ee/jakarta/tck/pages/spec/configuration/elevaluation/jsp_config_eleval_web.xml
index 9c489a3d..7a440517 100644
--- a/tck/src/main/resources/ee/jakarta/tck/pages/spec/configuration/elevaluation/jsp_config_eleval_web.xml
+++ b/tck/src/main/resources/ee/jakarta/tck/pages/spec/configuration/elevaluation/jsp_config_eleval_web.xml
@@ -23,18 +23,18 @@
5
-
+
- Unspecified in configuration and by JSP
+ Unspecified in configuration and by page
/elunspec/*
- Set to false in configuration not specified in JSP
+ Set to false in configuration not specified in page
/elconffalse/*
false
- Set to true in config not specified in JSP
+ Set to true in config not specified in page
/elconftrue/*
true
@@ -48,20 +48,20 @@
/elpagetrue/*
false
-
+
- Unspecified in configuration and by JSP
+ Unspecified in configuration and by document
/elunspecx/*
true
- Set to false in configuration not specified in JSP
+ Set to false in configuration not specified in document
/elconffalsex/*
false
true
- Set to true in config not specified in JSP
+ Set to true in config not specified in document
/elconftruex/*
true
true
diff --git a/tck/src/main/resources/ee/jakarta/tck/pages/spec/configuration/scripting/jsp_config_scr_web.xml b/tck/src/main/resources/ee/jakarta/tck/pages/spec/configuration/scripting/jsp_config_scr_web.xml
index 6884758c..cb446f7b 100644
--- a/tck/src/main/resources/ee/jakarta/tck/pages/spec/configuration/scripting/jsp_config_scr_web.xml
+++ b/tck/src/main/resources/ee/jakarta/tck/pages/spec/configuration/scripting/jsp_config_scr_web.xml
@@ -27,7 +27,7 @@
http://java.sun.com/tck/jsp/scr
/WEB-INF/tag.tld
-
+
Unspecified in property-group
/scrunspec/*
@@ -42,7 +42,7 @@
/scrtrue/*
true
-
+
Unspecified in property-group
/scrunspecx/*
diff --git a/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/actions/getproperty/positiveGetProps.jsp b/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/actions/getproperty/positiveGetProps.jsp
index 79396a3b..87ec3730 100644
--- a/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/actions/getproperty/positiveGetProps.jsp
+++ b/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/actions/getproperty/positiveGetProps.jsp
@@ -20,7 +20,7 @@
positiveGetProps
<% /** Name : positiveGetProps
- Description : Create a valid useBean tag in the JSP. Access one of its
+ Description : Create a valid useBean tag in the page. Access one of its
properties through a getProperty tag.
Result : Should return the value of the property as part of the returned
HTML
diff --git a/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/actions/setproperty/positiveSetPropAll.jsp b/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/actions/setproperty/positiveSetPropAll.jsp
index 9f25efbb..4742e1ff 100644
--- a/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/actions/setproperty/positiveSetPropAll.jsp
+++ b/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/actions/setproperty/positiveSetPropAll.jsp
@@ -20,7 +20,7 @@
positiveSetPropAll
<% /** Name : positiveSetPropAll
- Description : Create a valid useBean action in JSP. Set all properties
+ Description : Create a valid useBean action in page. Set all properties
of that bean from the request using a
action. Then access all
properties of the bean.
diff --git a/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/actions/setproperty/positiveSetPropNoParam.jsp b/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/actions/setproperty/positiveSetPropNoParam.jsp
index 042393cc..9b3bfe2c 100644
--- a/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/actions/setproperty/positiveSetPropNoParam.jsp
+++ b/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/actions/setproperty/positiveSetPropNoParam.jsp
@@ -20,7 +20,7 @@
positiveSetPropNoParam
<% /** Name : positiveSetPropNoParam
- Description : Create a valid useBean action in JSP. Set a specific
+ Description : Create a valid useBean action in page. Set a specific
property of that bean from the request using a
action. Then access
that property.Ensure that the request contains a parameter
diff --git a/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/actions/setproperty/positiveSetPropParam.jsp b/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/actions/setproperty/positiveSetPropParam.jsp
index aa97335d..319becc5 100644
--- a/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/actions/setproperty/positiveSetPropParam.jsp
+++ b/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/actions/setproperty/positiveSetPropParam.jsp
@@ -20,7 +20,7 @@
positiveSetPropParam
<% /** Name : positiveSetPropParam
- Description : Create a valid useBean action in JSP. Set a specific
+ Description : Create a valid useBean action in page. Set a specific
property of that bean from the request using a
action.
Then access that property.
diff --git a/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/actions/setproperty/positiveSetPropValue.jsp b/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/actions/setproperty/positiveSetPropValue.jsp
index 205e78f1..bd12a28b 100644
--- a/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/actions/setproperty/positiveSetPropValue.jsp
+++ b/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/actions/setproperty/positiveSetPropValue.jsp
@@ -20,7 +20,7 @@
positiveSetPropValue
<% /** Name : positiveSetPropValue
- Description : Create a valid useBean action in JSP. Set a specific
+ Description : Create a valid useBean action in page. Set a specific
property of that bean from the request using a
action.
Then access that property.
diff --git a/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/actions/usebean/ScopeResult.jsp b/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/actions/usebean/ScopeResult.jsp
index 8c5b4d52..8d9b5446 100644
--- a/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/actions/usebean/ScopeResult.jsp
+++ b/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/actions/usebean/ScopeResult.jsp
@@ -18,7 +18,7 @@
<%@ page contentType="text/plain;charset=ISO-8859-1" %>
<%--
- Simple JSP to valid scoped objects created with jsp:useBean
+ Simple page to valid scoped objects created with jsp:useBean
--%>
<%!
diff --git a/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/actions/usebean/positiveBodyNew.jsp b/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/actions/usebean/positiveBodyNew.jsp
index aafc84c5..db111272 100644
--- a/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/actions/usebean/positiveBodyNew.jsp
+++ b/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/actions/usebean/positiveBodyNew.jsp
@@ -20,7 +20,7 @@
positiveBodyNew
<% /** Name : positiveBodyNew
- Description : Try to create a valid useBean tag in the JSP page with a
+ Description : Try to create a valid useBean tag in the page with a
non-empty body. Ensure that the classname specified
does not exist.
Result :Should return the contents of the HTML page along with what
diff --git a/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/directives/include/positiveIncludeCtxRelativeDirective.jsp b/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/directives/include/positiveIncludeCtxRelativeDirective.jsp
index aa22cdcf..15fe57a0 100644
--- a/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/directives/include/positiveIncludeCtxRelativeDirective.jsp
+++ b/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/directives/include/positiveIncludeCtxRelativeDirective.jsp
@@ -20,7 +20,7 @@
positiveIncludeCtxRelativeDirective
<% /** Name : positiveIncludeCtxRelativeDirective
- Description : Create a JSP page with the include directive using
+ Description : Create a page with the include directive using
a context-relative path. The included
page should exist in the desired location
Result :Send out the HTML of the first page with the output of the
diff --git a/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/directives/include/positiveIncludePageRelativeDirective.jsp b/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/directives/include/positiveIncludePageRelativeDirective.jsp
index 7bcbe923..294dec17 100644
--- a/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/directives/include/positiveIncludePageRelativeDirective.jsp
+++ b/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/directives/include/positiveIncludePageRelativeDirective.jsp
@@ -20,7 +20,7 @@
positiveIncludePageRelative
<% /** Name : positiveIncludePageRelative
- Description : Create a JSP page with the include directive using a
+ Description : Create a page with the include directive using a
page-relative path. The included
page should exist in the desired location
Result :Send out the HTML of the first page with the output of the
diff --git a/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/scripting/declaration/positiveDeclaration.jsp b/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/scripting/declaration/positiveDeclaration.jsp
index 0fa1eee8..67d18a71 100644
--- a/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/scripting/declaration/positiveDeclaration.jsp
+++ b/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/scripting/declaration/positiveDeclaration.jsp
@@ -59,7 +59,7 @@
positiveDeclaration
<% /** Name : positiveDeclaration
- Description: Create a JSP page with a valid Java
+ Description: Create a page with a valid Java
declaration element. Use the declared variable
in the page in a scriptlet.
Result: No error
diff --git a/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/scripting/escaping/positiveEscapingTest.jsp b/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/scripting/escaping/positiveEscapingTest.jsp
index 287c297f..6b6cb735 100644
--- a/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/scripting/escaping/positiveEscapingTest.jsp
+++ b/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/scripting/escaping/positiveEscapingTest.jsp
@@ -16,7 +16,7 @@
--%>
-<%-- Validate recoginition and handling of JSP escape sequences --%>
+<%-- Validate recoginition and handling of Jakarta Pages escape sequences --%>
positiveEscapingTest
diff --git a/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/scripting/expressions/positiveExpr.jsp b/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/scripting/expressions/positiveExpr.jsp
index a01d66ba..91d8536e 100644
--- a/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/scripting/expressions/positiveExpr.jsp
+++ b/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/scripting/expressions/positiveExpr.jsp
@@ -59,8 +59,8 @@
positiveExpr
<% /** Name: positiveExpr
- Description:Create a valid JSP expression.
- Result: The JSP page output with the evaluated
+ Description:Create a valid Jakarta Pages expression.
+ Result: The Jakarta Pages page output with the evaluated
value of expression duly inserted in the
page.
**/ %>
diff --git a/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/scripting/expressions/positiveExprComment.jsp b/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/scripting/expressions/positiveExprComment.jsp
index 22dc5af7..436f431b 100644
--- a/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/scripting/expressions/positiveExprComment.jsp
+++ b/tck/src/main/resources/ee/jakarta/tck/pages/spec/core_syntax/scripting/expressions/positiveExprComment.jsp
@@ -59,7 +59,7 @@
positiveExprComment
<% /** Name:positiveExprComment
- Description: Create a JSP page with a JSP
+ Description: Create a Jakarta Pages page with a Jakarta Pages
expression inserted into a HTML comment
Result: The HTML should contain the value of the
expression inserted into the comment
diff --git a/tck/src/main/resources/ee/jakarta/tck/pages/spec/tagfiles/semantics/JspTagSemanticsAttributeNotSpecifiedTest.jsp b/tck/src/main/resources/ee/jakarta/tck/pages/spec/tagfiles/semantics/JspTagSemanticsAttributeNotSpecifiedTest.jsp
index 9965d0db..79ea73fc 100644
--- a/tck/src/main/resources/ee/jakarta/tck/pages/spec/tagfiles/semantics/JspTagSemanticsAttributeNotSpecifiedTest.jsp
+++ b/tck/src/main/resources/ee/jakarta/tck/pages/spec/tagfiles/semantics/JspTagSemanticsAttributeNotSpecifiedTest.jsp
@@ -21,7 +21,7 @@
<%--
Validate that if an attribute is declared, but not specified,
- that no page scoped variable is created in the JSP Context Wrapper.
+ that no page scoped variable is created in the Jakarta Pages Context Wrapper.
--%>
diff --git a/tck/src/main/resources/ee/jakarta/tck/pages/spec/tagfiles/semantics/JspTagSemanticsDeclaredAttributesTest.jsp b/tck/src/main/resources/ee/jakarta/tck/pages/spec/tagfiles/semantics/JspTagSemanticsDeclaredAttributesTest.jsp
index fe91098c..dfc67ac8 100644
--- a/tck/src/main/resources/ee/jakarta/tck/pages/spec/tagfiles/semantics/JspTagSemanticsDeclaredAttributesTest.jsp
+++ b/tck/src/main/resources/ee/jakarta/tck/pages/spec/tagfiles/semantics/JspTagSemanticsDeclaredAttributesTest.jsp
@@ -21,7 +21,7 @@
<%--
For each attribute declared and specified, a page-scoped variable
- must be created in the page scope of the JSP Context Wrapper.
+ must be created in the page scope of the Jakarta Pages Context Wrapper.
The name of the variable must be the same as the declared attribute name.
The value of the variable must be the value of the attribute passed in
during invocation.
diff --git a/tck/src/main/resources/ee/jakarta/tck/pages/spec/tagfiles/semantics/JspTagSemanticsJspContextWrapperTest.jsp b/tck/src/main/resources/ee/jakarta/tck/pages/spec/tagfiles/semantics/JspTagSemanticsJspContextWrapperTest.jsp
index 5f16590e..d3cd9fd3 100644
--- a/tck/src/main/resources/ee/jakarta/tck/pages/spec/tagfiles/semantics/JspTagSemanticsJspContextWrapperTest.jsp
+++ b/tck/src/main/resources/ee/jakarta/tck/pages/spec/tagfiles/semantics/JspTagSemanticsJspContextWrapperTest.jsp
@@ -20,13 +20,13 @@
<%@ taglib tagdir="/WEB-INF/tags" prefix="tags" %>
<%--
The tag file implementation must create and maintain a second
- instance of JspContext called a JSP ontext Wrapper. If the
- invoking JSP Context is an instance of PageContext, the JSP Context Wrapper
+ instance of JspContext called a Jakarta Pages Context Wrapper. If the
+ invoking Jakarta Pages Context is an instance of PageContext, the Jakarta Pages Context Wrapper
must also be an instance of PageContext. This wrapper must be returned
when getJspContext() is called.
--%>
-<%-- Store the invoking JSP context in the current request --%>
+<%-- Store the invoking Jakarta Pages context in the current request --%>
<% request.setAttribute("INVOKING_CONTEXT", pageContext); %>
<%-- invoke the tag --%>
diff --git a/tck/src/main/resources/ee/jakarta/tck/pages/spec/tagfiles/semantics/JspTagSemanticsScopesTest.jsp b/tck/src/main/resources/ee/jakarta/tck/pages/spec/tagfiles/semantics/JspTagSemanticsScopesTest.jsp
index ad9861bd..b0a0289d 100644
--- a/tck/src/main/resources/ee/jakarta/tck/pages/spec/tagfiles/semantics/JspTagSemanticsScopesTest.jsp
+++ b/tck/src/main/resources/ee/jakarta/tck/pages/spec/tagfiles/semantics/JspTagSemanticsScopesTest.jsp
@@ -125,12 +125,12 @@
%>
<%--
- For each invocation to the tag, the JSP Context Wrapper must
+ For each invocation to the tag, the Jakarta Pages Context Wrapper must
present a clean page scope containing no initial elements.
All scopes other than the page scope must be identical to those
- in the Invoking JSP Context and must be modified accordingly when updates
- are made to those scopes in the JSP Context Wrapper. Any modifications
- to the page scope, however, must not affect the Invoking JSP Context.
+ in the Invoking Jakarta Pages Context and must be modified accordingly when updates
+ are made to those scopes in the Jakarta Pages Context Wrapper. Any modifications
+ to the page scope, however, must not affect the Invoking Jakarta Pages Context.
--%>
<%-- Init the PageContext scopes --%>
diff --git a/tck/src/main/resources/ee/jakarta/tck/pages/spec/tagfiles/semantics/WEB-INF/tags/JspContextWrapperScopesTag.tag b/tck/src/main/resources/ee/jakarta/tck/pages/spec/tagfiles/semantics/WEB-INF/tags/JspContextWrapperScopesTag.tag
index e49098f9..2b7f678c 100644
--- a/tck/src/main/resources/ee/jakarta/tck/pages/spec/tagfiles/semantics/WEB-INF/tags/JspContextWrapperScopesTag.tag
+++ b/tck/src/main/resources/ee/jakarta/tck/pages/spec/tagfiles/semantics/WEB-INF/tags/JspContextWrapperScopesTag.tag
@@ -22,7 +22,7 @@
// check to make sure the page scope of wrapper context is emtpy.
Enumeration e = jspContext.getAttributeNamesInScope(PageContext.PAGE_SCOPE);
if (e.hasMoreElements()) {
- out.println("Test FAILED. The JSP Context Wrapper did not have a clean " +
+ out.println("Test FAILED. The Jakarta Pages Context Wrapper did not have a clean " +
"page scope.");
out.println("Attribute names found:");
for (String name = (String) e.nextElement();
diff --git a/tck/src/main/resources/ee/jakarta/tck/pages/spec/tagfiles/semantics/WEB-INF/tags/JspContextWrapperTag.tag b/tck/src/main/resources/ee/jakarta/tck/pages/spec/tagfiles/semantics/WEB-INF/tags/JspContextWrapperTag.tag
index b1345236..5eafc88b 100644
--- a/tck/src/main/resources/ee/jakarta/tck/pages/spec/tagfiles/semantics/WEB-INF/tags/JspContextWrapperTag.tag
+++ b/tck/src/main/resources/ee/jakarta/tck/pages/spec/tagfiles/semantics/WEB-INF/tags/JspContextWrapperTag.tag
@@ -34,13 +34,13 @@
"by getJspContext()");
}
} else {
- out.println("Test FAILED. The JSP Context Wrapper is the " +
- "same object as the invoking JSP Context.");
+ out.println("Test FAILED. The Jakarta Pages Context Wrapper is the " +
+ "same object as the invoking Jakarta Pages Context.");
}
} else {
- out.println("Test FAILED. The JSP Context Wrapper returned by" +
+ out.println("Test FAILED. The Jakarta Pages Context Wrapper returned by" +
" getJspContext() should have been an instance of PageContext\n" +
- " as the invoking JSP Context is Servlet-based.");
+ " as the invoking Jakarta Pages Context is Servlet-based.");
}
} else {
out.println("Test FAILED. The invocation of getJspContext() " +
| |