We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We verbally agreed that we want to narrow down how interceptors may be declared and bound in CDI Lite. We need to write it down to the spec.
A big part of the discussion happened in this issue: jakartaee/cdi-tck#262 I'm copying the table that we agreed upon:
✔️ means "part of CDI Lite" ❌ means "not part of CDI Lite, only CDI Full" ❔ means "I don't know, please help" :-) ☣️ means "can't happen"
@AroundConstruct
@PostConstruct
@PreDestroy
@AroundInvoke
@Priority
@Interceptors
beans.xml
Interceptor
InterceptionFactory
I'm leaving @AroundInvoke on target class as ❔, but all things considered, it should really be ❌.
The text was updated successfully, but these errors were encountered:
Looks good!
Sorry, something went wrong.
+1 from me
manovotn
Successfully merging a pull request may close this issue.
We verbally agreed that we want to narrow down how interceptors may be declared and bound in CDI Lite. We need to write it down to the spec.
A big part of the discussion happened in this issue: jakartaee/cdi-tck#262 I'm copying the table that we agreed upon:
✔️ means "part of CDI Lite"
❌ means "not part of CDI Lite, only CDI Full"
❔ means "I don't know, please help" :-)
☣️ means "can't happen"
@AroundConstruct
@PostConstruct
,@PreDestroy
@AroundInvoke
@Priority
@Interceptors
beans.xml
Interceptor
InterceptionFactory
I'm leaving
@AroundInvoke
on target class as ❔, but all things considered, it should really be ❌.The text was updated successfully, but these errors were encountered: