I don't really see how that would happen.
On Tue, Apr 30, 2013 at 10:22 AM, Christian Kaltepoth < [email protected]> wrote: > I think the problem is related to the fact that the the context class > loader is used to access the BeanManagerInfo instance. > > > https://github.com/apache/incubator-deltaspike/blob/master/deltaspike/core/api/src/main/java/org/apache/deltaspike/core/api/provider/BeanManagerProvider.java#L152 > > If AfterBeanDiscovery is fired with a different context class loader, users > will get this message when using the BeanManagerProvider. > > WDYT? > > > 2013/4/30 Jason Porter <[email protected]> > > > I'm not sure where we're using this before weld finishes starting up. > > > > > > On Tue, Apr 30, 2013 at 3:05 AM, Łukasz Dywicki <[email protected]> > > wrote: > > > > > I have same classloading issue with EAR, however in JBoss AS 7.2 (EAP > 6.1 > > > Alpha). > > > > > > > > > > > > Wiadomość napisana przez Maik Ebert <[email protected]> w dniu > 29 > > > kwi 2013, o godz. 11:05: > > > > > > > Hi Jason, > > > > > > > > These messages are written when our normal application logic is > > running. > > > Nothing special. > > > > > > > > Greetings, > > > > > > > > Maik > > > > > > > > > > > > > > > > -- > > Jason Porter > > http://en.gravatar.com/lightguardjp > > > > > > -- > Christian Kaltepoth > Blog: http://blog.kaltepoth.de/ > Twitter: http://twitter.com/chkal > GitHub: https://github.com/chkal > -- Jason Porter http://en.gravatar.com/lightguardjp
