[ https://issues.jboss.org/browse/CDI-377?page=com.atlassian.jira.plugin.sy... ] Jozef Hartinger commented on CDI-377: ------------------------------------- {quote}The other obvious solution I see is to remove @Singleton from the list of Bean defining annotations. As CDI doesn't really support it, it wouldn't be too harmful for existing CDI app. It would fix the problem since all beans in Spring or Guice libs that triggers CDI does it with this annotation.{quote} This is much better than the previous solution. I can see these options: # To introduce a no-bean-archive marker file (e.g. no-beans.xml). This solution: #* is backwards compatible #* only solves the problem for libraries that care and only in new or repackaged versions of the lib # Deal with @Singleton somehow. For instance, we could keep @Singleton a bean defining annotation but say that out of the bean defining annotations used in a bean archive, at least one has to be a normal scope or a built-in scope for the bean archive to be recognized. That way we would still be picking up @Singletons as long as they are used together with pure CDI scopes. If there are only @Singletons or non-normal non-builtin scopes in the archive, it will not be recognized. This solution is: #* similar to your recent proposal #* probably trickier to define nicely #* backwards incompatible, but the class of applications possibly affected by this is very small (basically only the apps using only @Singleton or non-normal non-builtin scopes) -- 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