[cdi-dev] [Vote] @ApplicationScoped and visibility

Stuart Douglas stuart.w.douglas at gmail.com
Mon Nov 26 17:11:26 EST 2012

In AS7 we set the TCCL on each EJB invocation. There is no explicit requirement to do this is in the EJB spec as far as I can see, however I can't really imagine an implementation not doing this, as you could potentially end up with a TCCL that cannot see the EJB class. 


Pete Muir wrote:
> On 26 Nov 2012, at 19:41, Mark Struberg wrote:
>>> I believe the OWB actually follows 1a
>>> as the question is currently written.  When the EJB is executing,
>>> the thread context classloader would be that of the ejb module so the correct
>>> bean would be injected for that module.
>> Nope, OWB follows 1b and is thus perfectly in sync with all the other EE containers I tested (feel free to grab my app and test yourself!). CDI != EJB. There is (currently) no magical TCCL change involved in any CDI call chain. Not in OWB and also not in Weld so far afaik.
> Right. Weld never sets the TCCL. But other things such as EJB might to in JBoss AS. Stuart, can you comment?
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev

More information about the cdi-dev mailing list