Skander created TOMEE-4530:
------------------------------
Summary: Jakarta EE 11
Key: TOMEE-4530
URL: https://issues.apache.org/jira/browse/TOMEE-4530
Project: TomEE
Issue Type: New Feature
Components: TomEE Core Server
Affects Versions: 10.1.2
Reporter: Skander
Fix For: 10.1.3
h1. Specifications and Implementations changes for TomEE 11
|*Specification*|*Spec Version*|*Implementation(s)*|*Version*|
|Jakarta Servlet, JSP, Expression Language (EL), Annotations, Authentication
(JASPIC), WebSocket, ...|11|Apache Tomcat|11|
|Jakarta Faces (JSF)|4.1|Apache MyFaces (all TomEE flavors except Plume)
Eclipse Mojarra (TomEE Plume)|4.1.x (released)
4.1.x (released)|
|Jakarta Contexts and Dependency Injection (CDI)|4.1|Apache OpenWebBeans (with
jakarta classifier)|No release yet|
|Jakarta Persistence (JPA)|3.2|Apache OpenJPA|OPENJPA-2940|
|Jakarta Persistence (JPA)|3.2|EclipseLink (TomEE Plume)|Pre-released
EclipseLink 5.0.0|
|Jakarta Persistence (JPA)|3.2|Hibernate |7.2|
|Jakarta Data|1.0|Hibernate|7.2|
|Jakarta Data|1.0|Write an Apache implementation (May be needed)|TomEE 11|
|Jakarta Validation|3.1|Apache BVal|Not release yet|
|Web Services|4.0|Apache CXF|4.2 (Not released yet)|
|Jakarta Concurrency|3.1|TomEE|TomEE 11|
|Jakarta Security|4.0|TomEE|TomEE 11|
|Jakarta Interceptors|2.2|TomEE|TomEE 11|
|Jakarta Authorization (JACC)|3.1|TomEE|TomEE 11|
h2. Color codes
{color:#00875a}Dependency Upgrade{color}
{color:#ff8b00}Need to be implemented for TomEE 11 / No release planned for
dependency yet{color}
{color:#ffab00}Dependency release is going on{color}
h1. Need to be implemented in TomEE 11
h2. Jakarta Concurrency 3.1
h3. New features, enhancements or additions
* [Integration with Java 21 Virtual
Threads|https://github.com/jakartaee/concurrency/issues/268]
* [Java Flow/ReactiveStreams and context
propagation|https://github.com/jakartaee/concurrency/issues/257]
* [Replace more features from
EJB|https://github.com/jakartaee/concurrency/issues/252], such as
[Schedule|https://github.com/jakartaee/concurrency/issues/98] and annotations
* [Become more CDI-centric|https://github.com/jakartaee/concurrency/issues/229]
* Specification bug fixes and clarifications
* TCK fixes and
[enhancements|https://github.com/jakartaee/concurrency/issues/269]
h2. Jakarta Security 4.0
h3. New features, enhancements or additions
* Basic API (handler) for Multiple authentication mechanisms
* Qualifiers for build-in authentication mechanisms
* In-memory identity store
h3. Removals, deprecations or backwards incompatible changes
* Remove references to the SecurityManager (as listed here:
[https://github.com/search?q=repo%3Ajakartaee%2Fsecurity%20SecurityManager&type=code])
* Build-in authentication mechanisms now have a qualifier by default, whereas
before they were unqualified
h2. Jakarta Authorization 3.0
h3. New features, enhancements or additions
* Register a policy provider programmatically per application [AUTHORIZATION
#98|https://github.com/jakartaee/authorization/issues/98]
* Standarize the context ID for Servlet containers
* Several convenience methods to make the API easier to use
h3. Removals, deprecations or backwards incompatible changes
* Design and implement replacement for Policy [AUTHORIZATION
#99|https://github.com/jakartaee/authorization/issues/99]
* Remove references to the SecurityManager
h2. Jakarta Interceptors 2.2
h3. New features, enhancements or additions
* Updated dependencies for Jakarta EE 11
** Jakarta Annotations to 3.0.0
* [Add standard accessor to interceptor
bindings|https://github.com/jakartaee/interceptors/issues/100]
* [Provide access to interceptor bindings from
InvocationContext|https://jakarta.ee/specifications/interceptors/2.2/#https://github.com/jakartaee/interceptors/pull/99]
* Improve InvocationContext.getInterceptorBindings() language
** [More precise language for
InvocationContext.getInterceptorBindings()|https://github.com/jakartaee/interceptors/pull/103]
** [Clarify behavior of InvocationContext.getInterceptorBindings() in case of
inherited/transitive
bindings|https://github.com/jakartaee/interceptors/pull/106]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
