[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... ] David Lloyd commented on AS7-708: --------------------------------- I'm not arguing that it shouldn't be fixed. I'm just saying that regardless of how this "seems", this is not part of the scanning phase like it was in AS 6, so arguing about ignoring the error in the scanning phase is wasting breath. This exception is being thrown once all components have been already been discovered (via scanning and descriptor processing), and are on their way to being instantiated, that is all. The scanning layer has no reason to believe that there is anything amiss about the components it is trying to instantiate. I don't think a blanket "ignore errors" is necessarily wise either. I think we should: # fix the error message to say exactly what component failed, what kind it is, and why it failed (right now it's just giving the "why" without the "what") ## In the component description, we can link the resource root, provide a textual component type ("EJB", "Managed Bean", etc.), and a source file (deployment descriptor, class file), so when exceptions are thrown, we can use that information to present cogent error messages. ## In the instantiation phase we can make sure to catch all exception types and supplement them with this info. # do one of the following: ## provide deployment descriptor overrides to disable certain components by name or class ## provide descriptor overrides to disable annotation and/or descriptor scanning on a per-JAR basis (if this error is being triggered by a bundled JAR for example) ## provide descriptor overrides to disable components by JAR (bundled JARs again) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira