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 |
| On target class |
☣️ |
✔️ |
❔ |
On interceptor class, binding annotation + @Priority |
✔️ |
✔️ |
✔️ |
On interceptor class, @Interceptors |
❌ |
❌ |
❌ |
On interceptor class, enabled using beans.xml |
❌ |
❌ |
❌ |
Implementing Interceptor |
❌ |
❌ |
❌ |
Using InterceptionFactory |
☣️ |
☣️ |
❌ |
I'm leaving @AroundInvoke on target class as ❔, but all things considered, it should really be ❌.
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@Interceptorsbeans.xmlInterceptorInterceptionFactoryI'm leaving
@AroundInvokeon target class as ❔, but all things considered, it should really be ❌.