Re: broken CDI handling in MyFacesContainerInitializer

It seems this only happens with MaFaces-2.2.x and is fixed in 2.3.0! I'll update the ticket to reflect this info.Do we want to backport this change or just move forward? LieGrue,strub On Friday, 13 April 2018, 17:17:17 CEST, Mark Struberg wrote: Hi Leo! The point

[jira] [Commented] (MYFACES-4224) AnnotatedFlowConfigurator.configureAnnotatedFlows is broken

[ https://issues.apache.org/jira/browse/MYFACES-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16437884#comment-16437884 ] Mark Struberg commented on MYFACES-4224: The issue is already fixed in myfaces-2.3.0! >

[jira] [Commented] (MYFACES-4225) [perf] Cache whether a library exists in ExternalContextResourceLoader

[ https://issues.apache.org/jira/browse/MYFACES-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16437672#comment-16437672 ] Mark Struberg commented on MYFACES-4225: Probably just an oversight. Ofc for every negative

[jira] [Commented] (MYFACES-4225) [perf] Cache whether a library exists in ExternalContextResourceLoader

[ https://issues.apache.org/jira/browse/MYFACES-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16437555#comment-16437555 ] Leonardo Uribe commented on MYFACES-4225: - There is already a cache for that in place.

[jira] [Commented] (MYFACES-4225) [perf] Cache whether a library exists in ExternalContextResourceLoader

[ https://issues.apache.org/jira/browse/MYFACES-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16437655#comment-16437655 ] Christian Beikov commented on MYFACES-4225: --- Hmm, you are right. I must have overseen that,

[jira] [Commented] (TOBAGO-1867) Content of and should have "overflow: auto"

[ https://issues.apache.org/jira/browse/TOBAGO-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16437761#comment-16437761 ] Hudson commented on TOBAGO-1867: SUCCESS: Integrated in Jenkins build Tobago Trunk #1371 (See

broken CDI handling in MyFacesContainerInitializer

Hi folks! I've figured that we blow up pretty nasty when using latest MyFaces on Tomcat with any CDI container (OWB or Weld). That's because you must not use BeanManager#getBeans before AfterDeplyomentValidation gets fired. I think the whole handling should ONLY be done via a CDI Extension!

Re: broken CDI handling in MyFacesContainerInitializer

Puh, stupid problem I think we must move the "CDI-init stuff" into a extension, but the leave everything else as it is as MF can still be used without CDI. As the ServletContextInitializer runs before the CDI Extensions, the StartupFacesContext could be available, also in the extension?

Re: broken CDI handling in MyFacesContainerInitializer

Hi Leo! The point is that we do bean initialisation in FacesInitializer. But we actually should do it in the CDI Extensions. When we startup the FacesInitializer it is _not_ guaranteed that the CDI container is already started! And even we get our hand at the BeanManager then this is not a

[jira] [Resolved] (MYFACES-4222) MYFACES-4203 regresses ui:repeat , can't update the step

[ https://issues.apache.org/jira/browse/MYFACES-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Nicolucci resolved MYFACES-4222. - Resolution: Fixed > MYFACES-4203 regresses ui:repeat , can't update the step >

[jira] [Resolved] (TOBAGO-1888) Attribute 'level' for tc:section

[ https://issues.apache.org/jira/browse/TOBAGO-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henning Noeth resolved TOBAGO-1888. --- Resolution: Fixed > Attribute 'level' for tc:section > > >

Re: broken CDI handling in MyFacesContainerInitializer

Hi It looks like a chicken-egg problem. But if CDI is present, it should run before MyFaces, so BeanManager should be available on MyFaces startup, never the opposite. After all, it is the bean container and the code was not designed for the opposite. I don't know if something changed. As far as

[jira] [Created] (MYFACES-4225) Consider caching whether a library exists in ExternalContextResourceLoader when project stage is PRODUCTION

Christian Beikov created MYFACES-4225: - Summary: Consider caching whether a library exists in ExternalContextResourceLoader when project stage is PRODUCTION Key: MYFACES-4225 URL:

[jira] [Commented] (MYFACES-4225) [perf] Cache whether a library exists in ExternalContextResourceLoader

[ https://issues.apache.org/jira/browse/MYFACES-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16437493#comment-16437493 ] Thomas Andraschko commented on MYFACES-4225: Could you provide a patch? Would be great! >

[jira] [Commented] (MYFACES-4225) [perf] Cache whether a library exists in ExternalContextResourceLoader

[ https://issues.apache.org/jira/browse/MYFACES-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16437519#comment-16437519 ] Christian Beikov commented on MYFACES-4225: --- I guess I could, but we'd have to agree which

[jira] [Commented] (MYFACES-4225) [perf] Cache whether a library exists in ExternalContextResourceLoader

[ https://issues.apache.org/jira/browse/MYFACES-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16437522#comment-16437522 ] Thomas Andraschko commented on MYFACES-4225: I would do it in: