tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Romain Manni-Bucau <>
Subject Re: CDI not working inside EAR with Atmosphere (BeanManager)
Date Tue, 22 Apr 2014 11:36:57 GMT

EAR handling of TomEE is different from other servers ATM (AFAIK it is
the choice done in CDI spec but other servers did other choice before
the discussion at spec level). We maybe have a bug but we need a
sample to have a look otherwise, out of the box, I'm tempted to say
the bug is in Atmosphere which relies on other impl behavior (well if
my phrase is ambiguous: to not 'troll' on which has the bug just
provide a sample to let Atmos and TomEE guys analyze the issue).

Romain Manni-Bucau
Twitter: @rmannibucau

2014-04-22 12:47 GMT+02:00 Lars Knemeyer <>:
> Hi,
> I am currently migrating my application from javax.websocket API to the
> Atmosphere framework.
> Sadly this migration is now stuck because CDI is not working inside my
> Atmosphere service.
> At first I thought it was an Atmosphere-specific problem so I filed an issue
> on the Atmosphere issue tracker:
> There the problem is described in detail and a sample project is provided.
> Short story: CDI works with Atmosphere only if the application is deployed
> as a WAR but not inside an EAR.
> There more I dig into this issue myself, the more I believe it might not be
> specifically related to Atmosphere but might be a problem with TomEE and
> classloading inside EAR. (as I wrote in the github issue, the sample works
> fine in WildFly 8.0.0.Final)
> I also tested TomEE and today's TomEE 1.6.1-SNAPSHOT, there the
> problem also exists.
> The Atmosphere code that fails to inject the beans can be found here:
> bm.getBeans() does not return any results when looking for the beans that
> should be injected.
> It would be great if anyone could look into this issue. Thanks in advance!
> Best regards
> Lars
> --
> View this message in context:
> Sent from the OpenEJB User mailing list archive at

View raw message