[
https://issues.apache.org/jira/browse/OWB-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921155#action_12921155
]
Mark Struberg commented on OWB-472:
-----------------------------------
Hi Jacquelle!
Thanks for your effort, but please note that the current behaviour is not a bug
but a feature! As explained on the mail thread you already posted: the spec is
contradictory in itself and the BDA behaviour for alternatives, interceptors
and decorators is _not_ backed by the Spec, _not_ backed by the TCK (we pass
those parts of the TCK easily) and completely sick and weird (personal opinion
of course). So I'd rather go and report a spec issue than changing our
implementation.
The reason: if I e.g. need to enable an <alternative> _inside_ a JAR, then it's
completely useless! Because there is NO way to enable this alternative from
lets say your webapp _without_ repackaging your JAR every time. Same is true
for interceptors and decorators of course.
> 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.
