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

@Priority on Sterotypes do not enable an Alternative as per the Spec #649

Closed
struberg opened this issue Jan 25, 2023 · 3 comments · Fixed by #674
Closed

@Priority on Sterotypes do not enable an Alternative as per the Spec #649

struberg opened this issue Jan 25, 2023 · 3 comments · Fixed by #674
Milestone

Comments

@struberg
Copy link
Contributor

In StereotypeWithPriorityTest it is assumed that @Priority on a Stereotype does enable the Alternative. But this is imo not defined in the spec.
The specification only defines 2 cases as per section 2.4.1.1:

An alternative may be given a priority for the application:
• by placing the @Priority annotation on the bean class of a managed bean, or
• by placing the @Priority annotation on the bean class that declares the producer method, field or resource.

Can you please point me to the paragraph which defines that Priority on Stereotypes do also count? Txs!

@Ladicek
Copy link
Contributor

Ladicek commented Jan 25, 2023

It's over here: https://jakarta.ee/specifications/cdi/4.0/jakarta-cdi-spec-4.0.html#priority_stereotype

But I agree that the section you point to should also mention it.

@struberg
Copy link
Contributor Author

struberg commented Jan 25, 2023

txs!

Closing, or do you want to keep it open for the spec wording change?

@Ladicek
Copy link
Contributor

Ladicek commented Jan 27, 2023

Yeah, let me reopen this. There's also a section in the CDI Full part of the spec that needs similar updating.

@Ladicek Ladicek reopened this Jan 27, 2023
@Ladicek Ladicek transferred this issue from jakartaee/cdi-tck Feb 2, 2023
@Ladicek Ladicek added this to the CDI 4.1/5.0 milestone Feb 2, 2023
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 a pull request may close this issue.

2 participants