[cdi-dev] [JBoss JIRA] (CDI-447) Section 12.1 specifies that JVM classpath must be included in bean archive identification
Martin Kouba (JIRA)
issues at jboss.org
Tue Jul 1 09:38:25 EDT 2014
[ https://issues.jboss.org/browse/CDI-447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12981033#comment-12981033 ]
Martin Kouba commented on CDI-447:
----------------------------------
I think this only applies to an embeddable EJB container, see paragraph below:
{quote}
The container searches for beans in all bean archives in the application classpath:
* In an application deployed as an ear, ...
{quote}
And in fact, an embeddable EJB container is not even covered by the TCK.
> Section 12.1 specifies that JVM classpath must be included in bean archive identification
> -----------------------------------------------------------------------------------------
>
> Key: CDI-447
> URL: https://issues.jboss.org/browse/CDI-447
> Project: CDI Specification Issues
> Issue Type: Clarification
> Components: Packaging and Deployment
> Affects Versions: 1.2.Final
> Reporter: Phil Zampino
>
> Section 12.1 of the spec states:
> When determining which archives are bean archives, the container must consider:
> • Library jars, EJB jars or application client jars
> • The WEB-INF/classes directory of a war
> • Directories in the JVM classpath
> For CDI 1.0, I think the inclusion of "directories in the JVM classpath" would not be a big deal. However, since the introduction of implicit bean archives, I'm wondering if implementations are required to scan the JVM classpath for classes annotated with bean-defining annotations. This seems like it has the potential to be an expensive requirement, and it should not be required.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
More information about the cdi-dev
mailing list