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

Pete Muir (JIRA) jira-events at lists.jboss.org
Mon Jun 7 03:46:38 EDT 2010

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

Pete Muir commented on WELD-521:

To have this work in all environments, in such a way that we don't actually load class definitions we don't need, we need to change the Weld SPI so that rather than passing in Collection<Class<?>> we pass in Collection<String> (containing the class names of the classes to load). This way, we can apply the include/exclude before we load the class definition.

> Such a plain list of classnames can be mapped into a bunch of includes but it might
> be better performance-wise to support both patterns and fully qualified class names
> directly in weld ? I.e. both a "pattern" attribute and a "name" attribute ?

We're starting to produce a pretty complex API for a simple problem. Let's try to keep it simple.

> Finally, in our examples we need to change the regular expressions as we forgot to escape the "." in package names.

Ugh! Now I'm wondering if supporting real regular expressions is a good idea at all. I think supporting Ant style include/exclude names might be much better (and scrap the regular expressions totally).

> 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