[
https://issues.jboss.org/browse/AS7-708?page=com.atlassian.jira.plugin.sy...
]
Lincoln Baxter III commented on AS7-708:
----------------------------------------
In addition, even if this is something that is "wrong" with the metawidget JAR,
if it is not a beans, EJB, JPA (or other EE type) archive, I don't think it should be
able to break deployment. Just from a user-experience standpoint, this means that people
can include jars that might have "problems" that would break otherwise
successful deployments. True, there may be something "wrong" but say for
example, they are doing classloading at runtime (URLClassLoader) to pull in these JAR
files from somewhere else on the server to satisfy these dependencies before they are
consumed in the application. That means they would no longer be able to utilize the
strategy... now... that may not be the best example in the world becuase they should
really put those libs in the server lib (more difficult on AS7?) but in reality, we should
not introduce limitations like this, even if it is "not a great idea"
My 2 cents.
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