Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@manovotn
Copy link
Contributor

Fixes #628

I will also create tracking TCK issue.
Also, I've checked in Weld that this is indeed trivial to implement as all BeanManager instances hold references to all contexts anyway.

@manovotn manovotn requested a review from Ladicek July 18, 2022 09:15
@Ladicek Ladicek requested a review from graemerocher July 18, 2022 09:31
@Ladicek Ladicek added this to the CDI 4.1/5.0 milestone Jan 31, 2023
@Ladicek Ladicek removed the CDI.next label Jan 31, 2023
@Ladicek Ladicek merged commit edae31c into jakartaee:master May 23, 2023
* {@linkplain jakarta.enterprise.context scope}.
*
* @param scopeType the {@linkplain jakarta.enterprise.context scope}; must not be {@code null}
* @return immutable collection of {@linkplain Context context objects}; never {@code null}, but may be empty
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* @return immutable collection of {@linkplain Context context objects}; never {@code null}, but may be empty
* @return an immutable collection of {@linkplain Context context objects}; never {@code null}, but may be empty

@Ladicek
Copy link
Contributor

Ladicek commented May 23, 2023

Need to file a TCK tracking issue now.

EDIT: actually a TCK tracking issue already exists: jakartaee/cdi-tck#396

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Accessing custom context objects in CDI Lite

3 participants