[cdi-dev] [JBoss JIRA] Commented: (CDI-87) Declarative control over classes including in bean archive scanning

[Mark Struberg (JIRA)]

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

Mark Struberg commented on CDI-87:
----------------------------------

To clarify what is meant (I guess): 

The beans.xml syntax should get extended with explicit <exclude> and <include> tags which can be used for performance tuning of the classpath scanning. 

E.g. if you have a backend project which contains a big amount of JPA entities, it would not make sense to scan this directory. So you can just add

<beans>
 <scan>
  <exclude>org/myproject/entities</exclude>
 </scan>
</beans>

Of course we need to clarify include/exclude order and stuff. e.g. 

<beans>
 <scan>
  <exclude>/</exclude>
  <include>org/myproject/services</include>
 </scan>
</beans>

We also need to clarify how the syntax of the include and exclude tags should look like: regexp or package names, etc

> Declarative control over classes including in bean archive scanning
> -------------------------------------------------------------------
>
>                 Key: CDI-87
>                 URL: https://issues.jboss.org/browse/CDI-87
>             Project: CDI Specification Issues
>          Issue Type: Feature Request
>          Components: Packaging and Deployment
>    Affects Versions: 1.0
>            Reporter: Pete Muir
>             Fix For: 1.1 (Proposed)
>
>
> Weld introduced a XML syntax for this

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira