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
Review all CDI related workarounds against currently available servers #281
Comments
If you mean the dynamic producers, then this was fixed in OWB, but unfortunately broke in Weld later again. See: https://issues.jboss.org/browse/CDI-610 |
No, I didn't mean
|
(it was previously done in container listener because GF crashed when JNDI was accessed in a container initializer; JNDI is not used anymore) Additionally, explicitly check for JSF 2.2 as well.
Also re-test all CDI functionality in multi-module EAR (two WARs in EAR) and update https://github.com/omnifaces/omnifaces/wiki/Known-Issues-(CDI) |
Important news: since Weld 2.3.5 (https://issues.jboss.org/browse/WELD-2143) there are no anymore issues when using OmniFaces in multiple WARs in multi-module EAR! |
(became obsolete since CDI 1.1 beans.xml <scan><exclude>)
Closing off as 2.5-RC1 has been released. |
beans.xml
was for long only CDI 1.0 in order to be TomEE 1.7.x compatible. Now TomEE 7.x is out for some time, it can be updated to CDI 1.1 and give us the opportunity to reliably useCDI.current()
.WebXml
andFacesConfigXml
enums have some awkward initialization workaround in order to be WebLogic 12.1 compatible. Check if it can be removed for WebLogic 12.2.@Inject InjectionPoint
workaround in all CDI producers can be removed in current OWB 1.6.3 version.Beans#getReference()
call can be replaced by@Inject
orCDI.current().select()
and still work in all current servers.The text was updated successfully, but these errors were encountered: