[ https://issues.jboss.org/browse/CDI-392?page=com.atlassian.jira.plugin.sy... ] Mark Struberg commented on CDI-392: ----------------------------------- Well, there is nothing in the API which says that this is optional for the BeanManager. We usually use the wording 'non-portable behaviour results' for parts which does exactly that. But in the case of calling getBeans during the build-up of the Beans itself it's not non-portable but it's really just broken due to the randomness of the bean-discovery order. This has nothing to do with non-portable but really is broken. This is hardly detectable by junior developers as it is similar to concurrency issues in such that it appears randomly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira