Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Requirements for CDI centric EE11 release #552

Open
starksm64 opened this issue Sep 27, 2022 · 1 comment
Open

Requirements for CDI centric EE11 release #552

starksm64 opened this issue Sep 27, 2022 · 1 comment
Assignees
@arjantijms
Labels
EE11 Jakarta EE 11 Release Epic Top level issue for tracking work jea-linked Linked in jakarta-ee-azdo project

Comments

@starksm64
Copy link
Contributor

starksm64 commented Sep 27, 2022 •
edited by azure-boards bot

Is your feature request related to a problem? Please describe.
A top-level objective for the EE 11 release is to improve the CDI centric focus across specifications.

Describe the solution you'd like
We need to gather requirements on what this actually means with input from specification teams.

Additional context
CDI Centric section of EE next discussion doc.

AB#69
@starksm64 starksm64 added the Epic Top level issue for tracking work label Sep 27, 2022
@ivargrimstad ivargrimstad added the EE11 Jakarta EE 11 Release label Mar 28, 2023
@edburns edburns added the jea-linked Linked in jakarta-ee-azdo project label Jul 5, 2023
@edburns edburns self-assigned this Sep 1, 2023
@edburns edburns assigned arjantijms and unassigned edburns Oct 23, 2023
@arjantijms
Copy link

Some requirement ideas:

  1. Servlets to become full CDI beans -> only in EE environment
  2. Think about repositioning EJB as CDI extension

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@arjantijms arjantijms

Labels
EE11 Jakarta EE 11 Release Epic Top level issue for tracking work jea-linked Linked in jakarta-ee-azdo project
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@edburns @ivargrimstad @starksm64 @arjantijms