[
https://issues.apache.org/jira/browse/OWB-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13274500#comment-13274500
]
Mark Struberg commented on OWB-667:
-----------------------------------
I've now talked with a few EG community members and created
https://issues.jboss.org/browse/CDI-231
What Weld does atm is that it _partially_ filters in getBeans() (dropping
non-enabled beans) and partially in resolve().
I'll wait for a reply from Pete to finally clarify the exact behaviour and then
might change this in OWB (should not be a problem, just move the logic).
> 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: Mark Struberg
> 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
