Hello, I have the same error whenever deploy an EAR into JBoss 7.1.x. I don't have this error when I deploy a WAR.
This is due I think to the fact that : * JBoss uses the EAR classloader to initialize CDI (and DS BeanManagerProvider). * JBoss uses the WAR classloader when serving a request. From what I remember, BeanManagerProvider register the BeanManager with the TCCL at initialization time. When asked, BeanManagerProvider tries to retrieve the BeanManager using the TCCL. Since the request TCCL is different from the classloader used for initialization, you get this warning. I just set BeanManagerProvider log level to ERROR to get rid of this error. ________________________________ De : Maik Ebert <m.eb...@paysafecard.com> À : "deltaspike-users@incubator.apache.org" <deltaspike-users@incubator.apache.org> Envoyé le : Vendredi 26 avril 2013 14h46 Objet : Fix log message "When using the BeanManager to retrieve Beans before the Container is started, non-portable behaviour results!" Hello, We are using on JBoss AS 7.1.3.Final DeltaSpike 0.3 in several applications we all deploy into one container. Through debugging I see that each of these applications is setting at a BeanManagerProvider instance the BeanManagerInfo.booted flag to true. That should be fine. But when the application is executed we still get the following log again and again: WARNING [org.apache.deltaspike.core.api.provider.BeanManagerProvider] (ajp-/10.100.222.113:8009-7) When using the BeanManager to retrieve Beans before the Container is started, non-portable behaviour results! When I debug to BeanManagerProvider. getBeanManager() I see the bmi.booted is now false... Must be some kind of classloading issue... Does someone has an idea how to fix that warning? Thanks in advance, Maik
