[weld-issues] [JBoss JIRA] Commented: (WELD-521) Introduce a way to exclude classes or packages from scanning

Morten Christensen (JIRA) jira-events at lists.jboss.org
Tue Jun 1 12:45:51 EDT 2010

    [ https://jira.jboss.org/browse/WELD-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12533464#action_12533464 ] 

Morten Christensen commented on WELD-521:

Oh, sad news about being to late for Glassfish 3.01. I will need to check for other workarounds (f.x. if the OSGI classes that I embed can resolve under glassfish so Weld does not blow up). If I can't do a workaround, I will have to either drop glassfish 3 support or replace Weld with another dependency management framework.

As for the format, what about something with multiple include and exclude regular expressions where exclude has priority over include and where the include/exclude's can be enabled/disabled dynamically using a static method that returns true/false. Fx.
 <include regExpr="com.mypackage.*"/>
 <include regExpr="org.somelib.*" if="com.mypackage.MyUtil.isProfessional">
 <exclude regExpr="com.mypackage.container.osgi.*" unless="com.mypackage.MyUtil.isOsgi"/>

Where the default would be:
 <include regExpr=".*"/>

And it would be easy to optimize this so when the default is used, then the performance impact of filtering would be zero. In other cases, there would be a slight added performance overhead for filtering but that would likely be offset by improved performance of weld not having to deal with the excluded classes.

> Introduce a way to exclude classes or packages from scanning
> ------------------------------------------------------------
>                 Key: WELD-521
>                 URL: https://jira.jboss.org/browse/WELD-521
>             Project: Weld
>          Issue Type: Feature Request
>          Components: Bootstrap and Metamodel API
>         Environment: Java SE and Java EE + weld
>            Reporter: Morten Christensen
>         Attachments: weld-se-ee-passifier.jar
> Better support for dual SE and EE applications. I have some weld-using jar's that can be deployed on a Java EE and work standalone. It is possible to get this to work using both weld SE and weld EE but it is a pain. F.x. when deployed under glassfish weld will fail unless I include a few weld SE dummy classes.... Weld should either combine weld SE and weld EE OR there should at least be some support for having weld ignoring some of my classes/packages depending on which environment it is running under.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the weld-issues mailing list