[jboss-jira] [JBoss JIRA] Issue Comment Edited: (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... ] David Lloyd edited comment on AS7-708 at 5/2/11 11:50 PM: ---------------------------------------------------------- Ah I see. That's not actually what is happening here. The class reflection index is something that is used to cache information about classes which are referenced by deployment descriptors, annotated with Java EE annotations, or referenced thereby. The error here is the result of actually attempting to install a component (usually an EJB but could also be a ManagedBean or a servlet) which can't actually be loaded. Suppressing the exception is definitely not the appropriate solution here, since AS 7 approaches annotation scanning completely differently from AS 6, which used reflection and thus detected linkage errors in a completely different phase of processing. What might be a better solution is to allow the specification of a pattern which class names can be matched against, which tells the scanner to ignore annotations (maybe just certain annotations) from that class. As an aside, the error message here is pretty awful. However, we are retooling part of the EE component installation process so I suspect that once that is done it will look somewhat better. But ideally we'd have an error saying "Failed to install EJB class org.foo.MyWhatever" before going into the mind-numbing detail, so the user at least knows where to look. Solutions for deployment issues should follow directly from the errors describing them. was (Author: dmlloyd): Ah I see. That's not actually what is happening here. The class reflection index is something that is used to cache information about classes which are referenced by deployment descriptors, annotated with Java EE annotations, or referenced thereby. Suppressing the exception is definitely not the appropriate solution here, since AS 7 approaches annotation scanning completely differently from AS 6. What might be a better solution is to allow the specification of a pattern which class names can be matched against, which tells the scanner to ignore annotations (maybe just certain annotations) from that class. As an aside, the error message here is pretty awful. However, we are retooling part of the EE component installation process so I suspect that once that is done it will look somewhat better. But ideally we'd have an error saying "Failed to install EJB class org.foo.MyWhatever" before going into the mind-numbing detail, so the user at least knows where to look. Solutions for deployment issues should follow directly from the errors describing them. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira