-
Clarification
-
Resolution: Done
-
Major
-
2.0-EDR2
-
None
-
None
Currently there are several read methods used to initialize given configurator. These methods are at:
- BeanConfigurator
- InjectionPointConfigurator
- ObserverMethodConfigurator
I think we should review all of them. I don't understand to usage or let say additional value of the following ones:
- ObserverMethodConfigurator#read(javax.enterprise.inject.spi.ObserverMethod<T>)
This allows you to add new observer method based on exsiting one. Although when you want to define some observed type (of this new method) you need to specify subtype of the original type or you will end up with ClassCastException.
Then there are those at InjectionPointConfigurator which appears to me completely useless:
- InjectionPointConfigurator#read(java.lang.reflect.Field)
- InjectionPointConfigurator#read(java.lang.reflect.Parameter)
- InjectionPointConfigurator#read(javax.enterprise.inject.spi.AnnotatedField<?>)
- InjectionPointConfigurator#read(javax.enterprise.inject.spi.AnnotatedParameter<?>)
- InjectionPointConfigurator#read(javax.enterprise.inject.spi.InjectionPoint)
AFAIK the InjectionPointConfigurator is available only during ProcessInjectionPoint lifecycle event. My question is why should I use any of these during this lifecycle event since I can easily call event.configureInjectionPoint()? Do we want to allow to configure different injection point in non corresponding ProcessInjectionPoint lifecycle event?
- is related to
-
CDITCK-514 Cover assertions for 11.5.7.1. InjectionPointConfigurator interface chapter
- Resolved