[ https://issues.jboss.org/browse/CDI-43?page=com.atlassian.jira.plugin.sys... ] Pete Muir commented on CDI-43: ------------------------------ At the EG meeting we discussed this, and everyone agreed we should move ahead with it. These comments were made: * That we need to define whether we look on not only the concrete class for annotations, but also super types (feeling was that we should) * That this should be defined as a filter, not as a hint (ie. container will use this, not may use this) * That we may want to consider scanning not only annotations but also meta annotations. Stuart, any comment on whether this will affect performance substantially. We also discussed whether it should be RetentionPolicy.CLASS or RetentionPolicy.RUNTIME. Stuart proposed CLASS, as this is then available for a bytecode reader, but not for Reflection/classloading, which would allow an extension which defines this to continue running in CDI 1.0. In general, we felt this was not necessary, as most extensions will simply upgrade to CDI 1.1, and also make use of other CDI 1.1 features, such as new container lifecycle events. We discussed naming, and concluded we need a different name. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira