[jboss-jira] [JBoss JIRA] Commented: (AS7-708) Ability to specify classloading exceptions to ignore similar to scanning-deployers-jboss-beans.xml

[ https://issues.jboss.org/browse/AS7-708?page=com.atlassian.jira.plugin.sy... ] Richard Kennard commented on AS7-708: ------------------------------------- So the logic here is: JBoss AS 7 is trying to load the class to see what annotations it has, because *if* it has annotations like @ManagedBean or @Stateless then JBoss AS 7 needs to prepare it for injection/something? However, in this case the offending class does *not* have any such annotations. Could we perhaps say that 'being unable to determine if an eligible class has annotations' and 'being unable to act upon the annotations defined in an eligible class' are (subtly) different things? That the first could be a warning and the latter an error? Because presumably many classes are 'eligible' and this is going to cause problems for JARs with optional dependencies? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira