You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are certain bits in the specification that have been carried over as deprecated legacy for years.
I think for future versions we can easily shake them off.
I discovered the following deprecated parts that I think we can remove:
@New qualifier
Deprecated since CDI 1.1 and replaced by @Dependent
Bean.isNullable() method
Deprecated since CDI 1.1
BeanManager.fireEvent() method
Deprecated since CDI 2.0 and replaced by BeanManager.getEvent()
For compatibility with Contexts and Dependency 1.0, products must contain an option to cause an archive to be ignored by the container when no beans.xml is present.
Obviously, for all of the above changes might be needed in both, API and specification text.
The text was updated successfully, but these errors were encountered:
There are certain bits in the specification that have been carried over as deprecated legacy for years.
I think for future versions we can easily shake them off.
I discovered the following deprecated parts that I think we can remove:
@New
qualifier@Dependent
Bean.isNullable()
methodBeanManager.fireEvent()
methodBeanManager.getEvent()
BeanManager.createInjectionTarget(AnnotatedType)
methodBeanManager.getInjectionTargetFactory(AnnotatedType)
BeforeBeanDiscovery.addAnnotatedType(AnnotatedType)
methodBeforeBeanDiscovery.addAnnotatedType(AnnotatedType, String)
beans.xml
For compatibility with Contexts and Dependency 1.0, products must contain an option to cause an archive to be ignored by the container when no beans.xml is present.
Obviously, for all of the above changes might be needed in both, API and specification text.
The text was updated successfully, but these errors were encountered: