Jakarta EE 11 Platform and Profile specification updates

- Update URLs to not require redirect to their directory and/or https
equivalent.
- Remove references of applet, aplplet container and applet
requirements.
- Update XML Schemas to their EE 11 versions.
- Remove references to and requirements for Java Security Manager except
to say it isn't required any longer in EE 11.
- Update minimum Java SE requirement to Java SE 17.
- Remove references to Jakarta SOAP with Attachments, XML Binding and
XML Web Services except to say they are no longer required by the EE 11
platform.
- Update component version numbers to be their EE 11 equivalent.
- Update references to Bean Validation to be just Validation except when
referencing older versions of the specification.
- Fix spelling errors found along the way.
- Add EE 11 specific sections to the appropriate places where there is
something added for each EE version.
- Remove reference to now non-existent http://javaee-spec.java.net URL
and only reference https://javaee.github.io/javaee-spec/
-

specification/src/main/asciidoc/coreprofile/CoreProfileDefinition.adoc

@@ -1,27 +1,29 @@
 == Core Profile Definition
 
-This chapter defines the contents of the Jakarta™ EE 10.0 Core Profile.
+This chapter defines the contents of the Jakarta™ EE 11.0 Core Profile.
 
 [[required_components]]
 === Required Components
 
 The following technologies are required components of the Core Profile:
 
-* Jakarta Annotations 2.1
-* Jakarta Contexts and Dependency Injection (CDI) 4.0 (CDI Lite section)
+* Jakarta Annotations 3.0*
+* Jakarta Contexts and Dependency Injection (CDI) 4.1 (CDI Lite section)*
 * Jakarta Dependency Injection 2.0
-* Jakarta Interceptors 2.1
+* Jakarta Interceptors 2.2*
 * Jakarta JSON Processing 2.1
 * Jakarta JSON Binding 3.0
-* Jakarta RESTful Web Services 3.1
+* Jakarta RESTful Web Services 4.0*
+
+*Note:* technologies with an asterisk after them represent updated versions.
 
 === Optional Components
 
 The optional Jakarta XML Binding support in Jakarta RESTful Web Services implementations is not required for the Core Profile.
 
 Jakarta Expression Language support is not required in Jakarta Contexts and Dependency Injection Lite implementations since this is part of the Full CDI specification.
 
-The Java SE section of the CDI 4.0 specification is not required for Core Profile implementations. Only Full CDI implementations are required to support the (CDI) Java SE API classes.
+The Java SE section of the CDI 4.1 specification is not required for Core Profile implementations. Only Full CDI implementations are required to support the (CDI) Java SE API classes.
 
 [[additional_requirements]]
 === Additional Requirements

specification/src/main/asciidoc/coreprofile/Introduction.adoc

@@ -8,7 +8,7 @@ Edition specifically targeted at smaller applications built around microservices
 The Core Profile is targeted at developers of
 modern cloud applications with focus on a minimal set of APIs
 that support microservices with a focus on enabling implementations
-that make use of ahead of time complitation build to minimize startup
+that make use of ahead of time compilation build to minimize startup
 time and memory footprint.
 
 It is worth noting that Core Profile products are allowed to ship with more technologies than the
@@ -34,7 +34,7 @@ technology or combinations of technologies.
 Let’s look at some examples of requirements from each grouping.
 
 For the first one, the Jakarta EE Platform
-specification mandates support for Java(TM) Platform, Standard Edition 11 API.  Because of this, all Core Profile 10.0 APIs must support the Java(TM) Platform, Standard Edition 11 API.
+specification mandates support for Java(TM) Platform, Standard Edition 17 API.  Because of this, all Core Profile 11.0 APIs must support the Java(TM) Platform, Standard Edition 17 API.
 
 In the second category one can point out the
 that Jakarta XML Binding support is not required for Jakarta RESTful Web Services in the Core Profile.
@@ -49,3 +49,8 @@ The fourth category is the most complex. The Jakarta Core Profile TCK attempts t
 
 The Jakarta EE 10.0 specification was created by the Jakarta EE Platform
 Specification Project with guidance provided by the Jakarta EE Working Group.
+
+=== Acknowledgements for Jakarta EE 11.0
+
+The Jakarta EE 11.0 specification was created by the Jakarta EE Platform
+Specification Project with guidance provided by the Jakarta EE Working Group.

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

@@ -6,23 +6,25 @@ This specification refers to the following
 documents. The terms used to refer to the documents in this
 specification are included in parentheses.
 
-_Java™ Platform, Standard Edition (Java SE specification), v11_. Available at: https://www.jcp.org/en/jsr/detail?id=384
+_Jakarta™ EE Platform Specification, Version 11.0_. Available at: _https://jakarta.ee/specifications/platform/11/_
 
-_Java™ Platform, Standard Edition, v11 API Specification_. Available at: _https://docs.oracle.com/en/java/javase/11/_
+_Java™ Platform, Standard Edition (Java SE specification), v17_. Available at: _https://www.jcp.org/en/jsr/detail?id=392_
 
-_Jakarta™ RESTful Web Services Specification, Version 3.1_. Available at: _https://jakarta.ee/specifications/restful-ws/3.1_
+_Java™ Platform, Standard Edition, v17 API Specification_. Available at: _https://docs.oracle.com/javase/17/docs/_
 
-_Jakarta™ Annotations Specification, Version 2.1_. Available at: _https://jakarta.ee/specifications/annotations/2.1_
+_Jakarta™ RESTful Web Services Specification, Version 4.0_. Available at: _https://jakarta.ee/specifications/restful-ws/4.0/_
 
-_Jakarta™ Interceptors Specification, Version 2.1_. Available at: _https://jakarta.ee/specifications/interceptors/2.1_
+_Jakarta™ Annotations Specification, Version 3.0_. Available at: _https://jakarta.ee/specifications/annotations/3.0/_
 
-_Jakarta™ Contexts and Dependency Injection Specification (CDI Lite section), Version 4.0_. Available at: _https://jakarta.ee/specifications/cdi/4.0_
+_Jakarta™ Interceptors Specification, Version 2.2_. Available at: _https://jakarta.ee/specifications/interceptors/2.2/_
 
-_Jakarta™ Dependency Injection Specification, Version 2.0_. Available at: _https://jakarta.ee/specifications/dependency-injection/2.0_
+_Jakarta™ Contexts and Dependency Injection Specification (CDI Lite section), Version 4.1_. Available at: _https://jakarta.ee/specifications/cdi/4.1/_
 
-_Jakarta™ JSON Processing Specification, Version 2.1_. Available at: _https://jakarta.ee/specifications/jsonp/2.1_
+_Jakarta™ Dependency Injection Specification, Version 2.0_. Available at: _https://jakarta.ee/specifications/dependency-injection/2.0/_
 
-_Jakarta™ JSON Binding Specification, Version 3.0_. Available at: _https://jakarta.ee/specifications/jsonb/3.0_
+_Jakarta™ JSON Processing Specification, Version 2.1_. Available at: _https://jakarta.ee/specifications/jsonp/2.1/_
+
+_Jakarta™ JSON Binding Specification, Version 3.0_. Available at: _https://jakarta.ee/specifications/jsonb/3.0/_
 
 _Jakarta™ EE Working Group_
 (_https://jakarta.ee/about/working-group/_)

specification/src/main/asciidoc/coreprofile/RevisionHistory.adoc

@@ -2,5 +2,9 @@
 
 == Revision History
 
+=== Changes in Final Release for EE11
+* Updated Java SE base version to 17.
+* Updated <<relateddocs, “Related Documents">> for the updated Specifications in Jakarta EE 11.
+
 === Changes in Final Release EE 10
 * Initial version

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

@@ -244,9 +244,9 @@ Jakarta EE products are required to support the
 use of bundled and installed libraries as specified in the _Extension
 Mechanism Architecture_ and _Optional Package Versioning_ specifications
 (available at
-_http://docs.oracle.com/javase/8/docs/technotes/guides/extensions/_ )
+_https://docs.oracle.com/javase/8/docs/technotes/guides/extensions/_ )
 and the JAR File Specification (available at
-_http://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html_ ).
+_https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html_ ).
 Using this mechanism a Jakarta EE JAR file can reference utility classes or
 other shared classes or resources packaged in a separate _.jar_ file or
 directory that is included in the same Jakarta EE application package, or
@@ -320,7 +320,7 @@ may be referenced in the following way:
 . JAR format files of all types may contain
 an _Extension-List_ attribute in their Manifest file, indicating a
 dependency on an installed library. The JAR File Specification defines
-the semantics of such attributes for use by applets; this specification
+the semantics of such attributes; this specification
 requires support for such attributes for all component types and
 corresponding JAR format files. The deployment tool is required to check
 such dependency information and reject the deployment of any component
@@ -753,10 +753,6 @@ access to the classes in other application client jar files in the same
 ear file, nor should it have access to the classes in web applications
 or Jakarta Enterprise Beans jar files in the same ear file.
 
-==== Applet Container Class Loading Requirements (Deprecated, removal in Java SE 17)
-
-Applets were deprecated in Java SE 9, and are slated for removal post Java SE 17.
-
 === Application Assembly
 
 This section specifies the sequence of steps
@@ -1290,7 +1286,7 @@ as defined by <<a3447, Previous Version Deployment Descriptors>>.
 The deployment descriptor must be named
 _META-INF/application.xml_ in the _.ear_ file. Note that this name is
 case-sensitive. The XML Schema located at
-_https://jakarta.ee/xml/ns/jakartaee/application_9.xsd_ defines the XML
+_https://jakarta.ee/xml/ns/jakartaee/application_11.xsd_ defines the XML
 grammar for a Jakarta EE application deployment descriptor.
 
 <<a3208, Jakarta EE Application XML Schema Structure>> shows a graphic representation
@@ -1303,6 +1299,6 @@ image::JavaEEapplication_schema_7.svg[]
 === Common Jakarta EE XML Schema Definitions
 
 The XML Schema located at
-_https://jakarta.ee/xml/ns/jakartaee/jakartaee_9.xsd_ defines types that are
+_https://jakarta.ee/xml/ns/jakartaee/jakartaee_11.xsd_ defines types that are
 used by many other Jakarta EE deployment descriptor schemas, both in this
 specification and in other specifications.

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

@@ -70,12 +70,6 @@ used, the authentication user interface provided by the server (in the
 form of an HTML page delivered in response to an HTTP request) must be
 displayed by the application client.
 
-Application clients typically execute in an
-environment with a SecurityManager installed, and have similar security
-permission requirements as servlets. The security permission
-requirements are described fully in
-<<a2339, Java Platform, Standard Edition (Java SE) Requirements>>.
-
 === Transactions
 
 Application clients are not required to have
@@ -115,8 +109,8 @@ start execution at the _main_ method of the class specified in the
 _Main-Class_ attribute in the manifest file of the application client’s
 JAR file (although note that application client container code will
 typically execute before the application client itself, in order to
-prepare the environment of the container, install a _SecurityManager_ ,
-initialize the name service client library, and so on).
+prepare the environment of the container, initialize the name service 
+client library, and so on).
 
 [[a3315]]
 === Packaging and Deployment
@@ -309,7 +303,7 @@ file. Note that this name is case-sensitive.
 <<a3404, Jakarta EE Application Client XML Schema Structure>> shows the structure of the Jakarta EE
 application-client XML Schema. The Jakarta EE application-client XML Schema
 is located at
-_https://jakarta.ee/xml/ns/jakartaee/application-client_9.xsd_.
+_https://jakarta.ee/xml/ns/jakartaee/application-client_10.xsd_.
 
 [[a3404]]
 .Jakarta EE Application Client XML Schema Structure