[
https://issues.apache.org/jira/browse/OWB-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13274332#comment-13274332
]
Phil Oser commented on OWB-667:
-------------------------------
Hello Mark
Yes, it is the same problem as owb 658. The RI has the behavior we expect. We
figured that we did not get our argument taken into account, so we tried again.
Given the javadoc (without the behavior of Weld), I could imagine a different
behavior, namely that all the beans that match the query (including
alternatives) are returned.
But the open web beans implementation throws away all results if just ONE
alternative is encountered (even if the query includes much more beans than
just the one matching the alternative).
I understand your pattern with the event. But I think it is a nuisance if a
framework that manages bean does not allow to query for beans?!
BTW: IMHO it would be great if open web beans could run CDI extensions such as
solder. I think it shows some advanced usages (we already filed another bug due
to it).
Thanks and cheers,
P
> Bean queries have strange behavior (difference between Open Web Beans and the
> Reference Implementation)
> -------------------------------------------------------------------------------------------------------
>
> Key: OWB-667
> URL: https://issues.apache.org/jira/browse/OWB-667
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.1.4
> Environment: All
> Reporter: Phil Oser
> Assignee: Gurkan Erdogdu
> Attachments: cdi-boot.zip
>
>
> We use the BeanManager#getBeans(java.lang.reflect.Type,
> java.lang.annotation.Annotation...) to find all beans of a certain type (to
> implement something like a service locator).
> As soon as one of the beans is an activated Alternative, the list of matching
> beans is reduced to this activated Alternative.
> The expected behavior is present in the Reference Implementation.
> Please refer to the attached test cases.
--
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
