[cdi-dev] [Vote] @ApplicationScoped and visibility
pmuir at redhat.com
Mon Nov 26 15:47:10 EST 2012
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?
More information about the cdi-dev