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

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

I think some aspects of this issue can be considered a bug and other parts 
represent a non-default implementation.  As mentioned in the description, most 
of us agree that not being able to define the same interceptor in multiple jars 
of a .war is a bug.  

I understand your point (Mark) about having to repackage a jar.  In such a 
case, the user would simply use the default OWB behavior.  

If a war contains utility.jar with numerous common classes (some of which are 
not well-known) and app1classes.jar  with application-specific logic, then 
there should be a way to only enable the modifiers (interceptors, decorators, & 
alternatives) in app1classes.jar.  In this case, a property would be set to 
enable the archive centric beans.xml solution.

> 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