[jboss-jira] [JBoss JIRA] Issue Comment Edited: (AS7-708) Ability to specify classloading exceptions to ignore similar to scanning-deployers-jboss-beans.xml

Tue May 17 02:42:01 EDT 2011

    [ https://issues.jboss.org/browse/AS7-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602485#comment-12602485 ] 

jaikiran pai edited comment on AS7-708 at 5/17/11 2:41 AM:
-----------------------------------------------------------

Your .war contains a .war/WEB-INF/lib/metawidget-all.jar which contains metawidget-all.jar/META-INF/metawidget-spring.tld (among other tlds). This tld file leads to the org.metawidget.jsp.tagext.html.spring.SpringMetawidgetTag class being picked up as a EE module class and this later leads to the NoClassDefFoundError due to the missing Spring libraries.

Technically, as per spec, all tlds at spec defined locations (like this one) are eligible for annotation processing (among other things). So I believe you'll have to probably repackage that jar to include the Spring tlds only in a Spring environment or maybe in general, we could somehow allow skipping certain tlds (and other such component defining artifacts) during deployment (David?).

As of now, I've added some log messages in the code (at DEBUG level) https://github.com/jaikiran/jboss-as/commit/7b79aa658066b1e355975249101b557ae626fd31 to atleast help us identify which class leads to this problem. I'll ask David to pull this upstream.

      was (Author: jaikiran):
    Your .war contains a .war/WEB-INF/lib/metawidget-all.jar which contains metawidget-all.jar/META-INF/metawidget-spring.tld (among other tlds). This tld file leads to the org.metawidget.jsp.tagext.html.spring.SpringMetawidgetTag class being picked up as a EE module class and this later leads to the NoClassDefFoundError due to the missing Spring libraries.

Technically, as per spec, all tlds at spec defined locations (like this one) are eligible for annotation processing (among other things). So I believe you'll have to probably repackage that jar to include the Spring tlds only in a Spring environment or maybe in general, we could somehow allow certain tlds (and other such component defining artifacts) from being picked up during deployment (David?).

As of now, I've added some log messages in the code (at DEBUG level) https://github.com/jaikiran/jboss-as/commit/7b79aa658066b1e355975249101b557ae626fd31 to atleast help us identify which class leads to this problem. I'll ask David to pull this upstream.

> 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