[ 
https://issues.apache.org/jira/browse/OWB-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921042#action_12921042
 ] 

Jacquelle Leggett commented on OWB-472:
---------------------------------------

I have already started working on a patch for this problem.  It only enables 
decorators, interceptors, and alternatives in the BDA that contains such a 
definition in its beans.xml.  This behavior is non-default and enabled via an 
OWB property.

> archive centric beans.xml enabling 
> -----------------------------------
>
>                 Key: OWB-472
>                 URL: https://issues.apache.org/jira/browse/OWB-472
>             Project: OpenWebBeans
>          Issue Type: Improvement
>          Components: Injection and Lookup
>            Reporter: Jacquelle Leggett
>            Assignee: Gurkan Erdogdu
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> This issue was discussed in great detail in June 
> (http://mail-archives.apache.org/mod_mbox/openwebbeans-dev/201006.mbox/browser)
>  on the developers forum.  The title of the thread is "problems with lack of 
> archive-centric BeanManager".  
> The main problem is described below (snippet from discussion):
> "...Our current design does not permit either of the following scenarions, 
> AFAICT:
>   b.jar and c.jar both enable the interceptor defined in a.jar
> (treated as a duplicate)
>   Exactly one of b.jar and c.jar enables the interceptor defined in
> a.jar (ends up enabled for beans from either archive if enabled in one
> -- this is in the more troubling neighborhood)..."

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to