[jira] [Updated] (OWB-652) Introduce HierarchicBeanManager

["Mark Struberg (Updated) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OWB-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Struberg updated OWB-652:
------------------------------

    Fix Version/s:     (was: 1.1.4)
                   1.2.0
    
> Introduce HierarchicBeanManager
> -------------------------------
>
>                 Key: OWB-652
>                 URL: https://issues.apache.org/jira/browse/OWB-652
>             Project: OpenWebBeans
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.1.3
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
>             Fix For: 1.2.0
>
>
> The currently implemented BeanManager cannot properly deal with multiple ClassLoaders forming an isolation hierarchy.
> This mainly hits EAR deployment in Java EE servers. The spec is not really clear about this scenario and in fact no existing EE server currently solves this problem sattisfyingly. 
> I already explained quite a few times how we can overcome this problem:
> http://mail-archives.apache.org/mod_mbox/openwebbeans-dev/201202.mbox/%3C1329169509.62085.YahooMailNeo@web171506.mail.ir2.yahoo.com%3E
> GERONIMO-6005
> https://issues.jboss.org/browse/CDI-142
> https://issues.jboss.org/browse/CDI-18
> https://issues.jboss.org/browse/CDI-129
> The solution:
> Each ClassLoader which has a BeanArchive will get it's own Beans. Any Beans accessible through a parent BeanManager will not be contained. Instead they must be resolved via the parent ClassLoader.
> It should be possible to easily implement this by introducing a HierarchicScannerService as a child-Interface of ScannerService which knows how to exclude parent BDAs. If a HierarchicScannerService is configured, the BeanManager will automatically delegate the detection to it's parent BeanManager. Otherwise all remains the way it is right now.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira