Loading...

XML

Word

Printable

Type: Feature Request
Resolution: Done
Priority: Major
Fix Version/s: 28.0.0.Beta1, 28.0.0.Final
Affects Version/s: None
Component/s: Build System, EE
Labels:
None

Git Pull Request:
https://github.com/wildfly/wildfly/pull/16549, https://github.com/wildfly/wildfly/pull/16651, https://github.com/wildfly/wildfly/pull/16663
[QE] How to address?:
---
[QE] Why QE missed?:
---

Implement a layer for the Jakarta EE 10 Core Profile. The Jakarta EE 10 Core Profile does not introduce any new specifications (other than the profile itself); rather it defines a subset of the full set of Jakarta EE specifications and a TCK for validating an implementation of that subset. It does not restrict implementations from shipping additional functionality (EE or otherwise) in their core profile implementation. This is all very similar to the Jakarta EE Web Profile that was introduced many years ago.

The following specifications are included in the Jakarta EE Core Profile.

Jakarta Annotations 2.1
Jakarta Contexts and Dependency Injection (CDI) 4.0 (CDI Lite section)
Jakarta Dependency Injection 2.0
Jakarta Interceptors 2.1
Jakarta JSON Processing 2.1
Jakarta JSON Binding 3.0
Jakarta RESTful Web Services 3.1

is blocked by

WFLY-13355 Add a Galleon layer for EE Concurrency

Closed

WFLY-17804 Add a servlet Galleon Layer

Closed

WFLY-17598 The jaxrs layer should not result in MicroProfile REST Client or Config provisioning

Closed

WFLY-17655 The TransactionsBootstrapDependencyInstaller should not assume the global transaction provider is available

Closed

relates to

WFLY-18763 Create a standalone-core-microprofile.xml example configuration file

Pull Request Sent

Assignee:: James Perkins

Reporter:: James Perkins

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2023/02/16 10:22 PM

Updated:: 2023/11/17 5:17 PM

Resolved:: 2023/03/29 5:20 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates