[
https://issues.jboss.org/browse/AS7-708?page=com.atlassian.jira.plugin.sy...
]
David Lloyd commented on AS7-708:
---------------------------------
I understand why we'd want this to work. The problem is that if there's no way to
distinguish this error from a legitimate problem in a user deployment, it will cause
management issues. If a deployment goes wrong, people will expect their deployment plans
to roll things back to prevent a possible disaster in customer-facing applications. So we
need to be able to tell the difference between a "safe" missing class and a
problematic one. That distinction might or might not be possible. If not, then we must
err on the side of proper error reporting.
Ability to specify classloading exceptions to ignore similar to
scanning-deployers-jboss-beans.xml
--------------------------------------------------------------------------------------------------
Key: AS7-708
URL:
https://issues.jboss.org/browse/AS7-708
Project: Application Server 7
Issue Type: Bug
Reporter: Jason Porter
Assignee: David Lloyd
Attachments: catch-demo.war
We need to be able to specify exceptions to ignore during classpath scanning. This was
available in AS6, we need it in AS7, or something similar. Please see
https://issues.jboss.org/browse/SEAMFORGE-156
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira