[
https://issues.jboss.org/browse/AS7-708?page=com.atlassian.jira.plugin.sy...
]
Richard Kennard commented on AS7-708:
-------------------------------------
Yeah, agreed. It seems odd that this problem is not evident in other app servers, but
there's much I don't understand about the new AS 7 scanning/instantiation
architecture.
Still presumably Metawidget is not the only JAR that has optional dependencies, so this is
probably going to impact a lot of frameworks? I would love to work with you to try and
improve my user's experience. The first question I would like to ask is:
"Given that metawidget-all.jar does not contain any EJBs/Managed Beans/etc, what is
the use case that is tripping up the instantiation architecture?"
My hunch would be the TLD tag libraries? But couldn't these be exempted?
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