[cdi-dev] Bean discovery question

Laird Nelson ljnelson at gmail.com
Wed Mar 22 11:51:28 EDT 2017

On Wed, Mar 22, 2017 at 4:17 AM Martin Kouba <mkouba at redhat.com> wrote:

> > That project's META-INF/beans.xml has bean discovery set to none
> > (
> https://github.com/ljnelson/microbean-main/blob/master/src/main/resources/META-INF/beans.xml#L7
> ),
> > since there are no beans in that bean archive (it houses only the main
> > class).  John indicated that this was likely the source of the problem:
> I don't think this is the problem. In Weld SE bean archive isolation is
> enabled by default. Ie. for
> https://github.com/ljnelson/microbean-maven-cdi/blob/master/src/main/java/org/microbean/maven/cdi/MavenExtension.java
> the beans.xml is
> https://github.com/ljnelson/microbean-maven-cdi/blob/master/src/main/resources/META-INF/beans.xml

Good; that confirms what I expected.

> > Perhaps I have misunderstood bean discovery: I thought that the
> > discovery mode applied to the bean archive in question alone, not to an
> > aggregate.
> What do you mean with "aggregate"? Bean discovery mode is applied to a
> specific bean archive only.

What I meant was: *if* I had misunderstood bean discovery, which I have
not, then perhaps something about that bean archive's "none" mode was
affecting other bean archives.  But I did not misunderstand bean discovery,
so this is moot.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20170322/12a207e6/attachment.html 

More information about the cdi-dev mailing list