Remove applet requirements, #298, update Java SE #331

specification/src/main/asciidoc/platform/ApplicationProgrammingInterface.adoc

@@ -13,9 +13,9 @@ technologies.
 
 Jakarta EE application components execute in
 runtime environments provided by the containers that are a part of the
-Jakarta EE platform. The full Jakarta EE platform supports four types of
+Jakarta EE platform. The full Jakarta EE platform supports three types of
 containers corresponding to Jakarta EE application component types:
-application client containers; applet containers; web containers for
+application client containers; web containers for
 servlets, Jakarta Server Pages, Jakarta Server Faces applications,
 Jakarta RESTful Web Services applications;
 and enterprise bean containers. A Jakarta EE profile may support only a subset
@@ -34,25 +34,24 @@ apply.
 ==== Java Compatible APIs
 
 The containers provide all application
-components with at least the Java Platform, Standard Edition, v8 (Java
+components with at least the Java Platform, Standard Edition, v11 (Java
 SE) APIs. Containers may provide newer versions of the Java SE platform,
 provided they meet all the Jakarta EE platform requirements as outlined below.
 
 ===== Java SE Enterprise Technologies
 
-The Java SE 8 platform includes a number of enterprise technologies. Except
+The Java SE 11 platform includes a number of enterprise technologies. Except
 for technologies noted in this specification as being optional, containers
 must provide all application components with the APIs associated with these
 technologies. If a newer version of the Java SE platform provided by
 a container has removed some of these technologies, the container must
 provide these technologies in some other manner.
 
-The Java SE 8 platform includes the following enterprise technologies:
+The Java SE 11 platform includes the following enterprise technologies:
 
-* Java IDL footnote:[Removed from Java SE 11. Support for Java IDL is optional (see <<a3539, Java IDL (Optional)>>.) Product vendors that wish to support Java IDL on a Java SE version that does not provide the Java IDL APIs must otherwise provide those APIs to application components.]
+* Java IDL footnote:[Removed from Java SE 11. Support for Java IDL is optional (see <<a3539, Java IDL (Optional)>>.) Product vendors that wish to support Java IDL on a Java SE version that does not provide the Java IDL APIs must otherwise provide those APIs to application components. ]
 * JDBC
 * RMI-JRMP
-* RMI-IIOP footnote:[Removed from Java SE 11. Support for RMI-IIOP is optional (see <<a3538, RMI-IIOP (Optional)>>.) Product vendors that wish to support RMI-IIOP on a Java SE version that does not provide the RMI-IIOP APIs must otherwise provide those APIs to application components.]
 * javax.rmi.PortableRemoteObject footnote:[Removed from Java SE 11. Product vendors that support the optional Enterprise Beans 2.x API group must ensure that the javax.rmi.PortableRemoteObject class is available to application components.]
 * JNDI
 * JAXP
@@ -70,12 +69,12 @@ by Java SE 8 are now provided by Jakarta EE specifications and are
 included in the list of <<a2161, Required Jakarta Technologies>>.
 
 The specifications for the Java SE APIs are
-available at _http://docs.oracle.com/javase/8/docs/_ .
+available at _http://docs.oracle.com/javase/11/docs/_ .
 
 ===== Java Module Names
 Java(TM) SE 9 introduced the concept of a modularity system, known as the Java Platform Module System (JPMS).
 Defined modules need a _name_ to allow for references by other modules.
-Jakarta EE 9 does not define a module naming convention.
+Jakarta EE 10 does not define a module naming convention.
 However, some Java EE(TM) 8 and Jakarta EE features had already defined their corresponding module names.
 Due to these previous module naming efforts, the following guidelines are strongly suggested for Jakarta EE 9:
 
@@ -1109,9 +1108,7 @@ read-only access to the data in the name service.
 A Jakarta EE product may be required to provide
 a COSNaming name service to meet the Jakarta Enterprise Beans interoperability
 requirements.  In such a case, a COSNaming JNDI service provider must be available
-through the web, Enterprise Beans, and application client containers. It will also
-typically be available in the applet container, but this is not
-required.
+through the web, Enterprise Beans, and application client containers.
 
 A COSNaming JNDI service provider is a part
 of the Java SE 8 SDK and JRE from Oracle, but is not a required
@@ -1691,8 +1688,7 @@ found at _https://jakarta.ee/specifications/faces_ .
 The Jakarta Annotations specification defines
 Java language annotations that are used by several other specifications,
 including this specification. The specifications that use these
-annotations fully define the requirements for these annotations. The
-applet container need not support any of these annotations. All other
+annotations fully define the requirements for these annotations. All other
 containers must provide definitions for all of these annotations, and
 must support the semantics of these annotations as described in the
 corresponding specifications and summarized in the following table.

specification/src/main/asciidoc/platform/PlatformOverview.adoc

@@ -132,12 +132,6 @@ language programs that are typically GUI programs that execute on a
 desktop computer. Application clients offer a user experience similar to
 that of native applications and have access to all of the facilities of
 the Jakarta EE middle tier.
-* Applets are GUI components that typically
-execute in a web browser, but can execute in a variety of other
-applications or devices that support the applet programming model.
-Applets can be used to provide a powerful user interface for Jakarta EE
-applications. (Simple HTML pages can also be used to provide a more
-limited user interface for Jakarta EE applications.)
 * servlets, server pages, server faces applications,
 filters, and web event listeners typically execute in a web container
 and may respond to HTTP requests from web clients. Servlets, server pages,
@@ -193,14 +187,14 @@ security checks, resource pooling, and state management.
 
 A typical Jakarta EE product will provide a
 container for each application component type: application client
-container, applet container, web component container, and enterprise
+container, web component container, and enterprise
 bean container.
 
 ==== Container Requirements
 
 This specification requires that containers
 support execution in a Java™ runtime environment, as defined by the Java
-Platform, Standard Edition specification, v8 or later (Java SE 8 or later).
+Platform, Standard Edition specification, v11 or later (Java SE 11 or later).
 
 The container tools must understand the file
 formats for the packaging of application components for deployment.
@@ -532,7 +526,6 @@ see fit. A Jakarta EE product must be able to deploy application components
 that execute with the semantics described by this specification.
 
 A typical low end Jakarta EE product will support
-applets using the Java Plugin in one of the popular browsers,
 application clients each in their own Java virtual machine, and will
 provide a single server that supports both web components and enterprise
 beans. A high end Jakarta EE product might split the server components into

specification/src/main/asciidoc/platform/RelatedDocuments.adoc

@@ -8,8 +8,6 @@ specification are included in parentheses.
 
 _Jakarta™ EE Web Profile Version 9.1_. Available at: _https://jakarta.ee/specifications/webprofile/9.1_
 
-_Java™ Platform, Standard Edition, v8 API Specification (Java SE specification)_. Available at: _https://docs.oracle.com/javase/8/docs/_
-
 _Java™ Platform, Standard Edition, v9 API Specification (Java SE specification)_. Available at: _https://docs.oracle.com/javase/9/_
 
 _Java™ Platform, Standard Edition, v11 API Specification (Java SE specification)_. Available at: _https://docs.oracle.com/en/java/javase/11/_

specification/src/main/asciidoc/platform/ResourcesNamingInjection.adoc

@@ -2508,7 +2508,7 @@ of the CORBA ORB to perform certain operations. Such applications can
 find an appropriate object implementing the _ORB_ interface by looking
 up the JNDI name _java:comp/ORB_ or by requesting injection of an _ORB_
 object. The container is required to provide the _java:comp/ORB_ name
-for all components except applets. Any such reference to a _ORB_ object
+for all components. Any such reference to a _ORB_ object
 is only valid within the component instance that performed the lookup.
 
 The following example illustrates how an

specification/src/main/asciidoc/platform/Security.adoc

@@ -606,7 +606,7 @@ needed. With lazy authentication, a user is not required to authenticate
 until there is a request to access a protected resource.
 
 Lazy authentication can be used with first-tier
-clients (applets, application clients) when they request access to
+application clients when they request access to
 protected resources that require authentication. At that point the user
 can be asked to provide appropriate authentication data. If a user is
 successfully authenticated, the user is allowed to access the resource.

specification/src/main/asciidoc/platform/TransactionManagement.adoc

@@ -215,11 +215,6 @@ in the Jakarta Enterprise Beans specification.
 The Jakarta EE Product Provider is not required to provide transaction
 management support for application clients.
 
-==== Applet Clients
-
-The Jakarta EE Product Provider is not required to provide transaction
-management support for applets.
-
 [[a516]]
 ==== Transactional JDBC™ Technology Support
 

specification/src/main/asciidoc/webprofile/RelatedDocuments.adoc

@@ -8,8 +8,6 @@ specification are included in parentheses.
 
 _Jakarta™ EE Platform Specification Version 9.1_. Available at: _https://jakarta.ee/specifications/platform/9.1_
 
-_Java™ Platform, Standard Edition, v8 API Specification (Java SE specification)_. Available at: _https://docs.oracle.com/javase/8/docs/_
-
 _Java™ Platform, Standard Edition, v11 API Specification (Java SE specification)_. Available at: _https://docs.oracle.com/en/java/javase/11/_
 
 _Jakarta™ Enterprise Beans Specification, Version 4.0_. Available at: _https://jakarta.ee/specifications/enterprise-beans/4.0_