-
Notifications
You must be signed in to change notification settings - Fork 39
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
Missing annotation literal in @Asynchronous annotation #176
Comments
What's the thinking behind it? Would be good to know to understand whether to push to get in this release? |
Annotation literals are essential when adding annotations programmatically to beans in CDI. This is the exact reason why all CDI's own annotations (where applicable) have literals. Omission of literals in annotations is still one of the reasons why the programmatic API in CDI feels sub-par, hence why, in principle, all annotations intended to be used in a CDI environment should have them. |
Adding the annotation programmatically seems like a more obscure scenario for |
I hear you, though it's perhaps less obscure for when you translate between the give or take 7 existing |
p.s. annotation literals are not just for adding them programmatically, you also use them for look-ups. |
It's general a good practice to add annotation literals to annotations that are used in CDI environments. We forgot these for the Faces 2.3 spec, and got quite a bit of feedback about those.
We added them in 4.0 as per e.g. this example:
https://github.com/eclipse-ee4j/mojarra/blob/master/impl/src/main/java/jakarta/faces/annotation/ApplicationMap.java#L52
Would be good for Concurrency to do the same.
The text was updated successfully, but these errors were encountered: