[cdi-dev] Bean Discovery Mode in SE

Romain Manni-Bucau rmannibucau at gmail.com
Sun Mar 1 11:27:45 EST 2015


It is consistent so ok.

Wonder if we can get some rule we could pass to the container to say "dont
scan jackson*jar" - issue begin we have to suppose we run with a classpath
we dont control. Or the opposite "scan myapp*jar".

wdyt?


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber
<http://www.tomitribe.com>

2015-03-01 16:18 GMT+01:00 John D. Ament <john.d.ament at gmail.com>:

> Yeah actually you're right.  For some reason I had in my head that "all"
> was the default.  It's very clearly not.  Too early for some of this :-)
>
> So let me rephrase.  "annotated" will be the default bean discovery mode
> if a classpath entry contains no META-INF/beans.xml, based on the exact
> same rules used in EE.
>
> Any concerns with that?
>
> John
>
>
> On Sun, Mar 1, 2015 at 10:10 AM Romain Manni-Bucau <rmannibucau at gmail.com>
> wrote:
>
>> For me it is 100% the same as ee where you have the same issues so
>> keeping them aligned is better IMO. That said configuring globally the
>> scanning would be nice.
>> Le 1 mars 2015 15:54, "John D. Ament" <john.d.ament at gmail.com> a écrit :
>>
>>> All,
>>>
>>> I'd like to propose in my doc changes for CDI-26 that if a classpath
>>> entry does not contain a META-INF/beans.xml that it is treated as if it
>>> were bean-discovery-mode=none, e.g. no beans will be scanned in that entry.
>>> (BTW, I'm using classpath entry rather than archive in the document to
>>> account for cases where someone does -cp
>>> "./classes:./extra-classes:./lib/*" to define their classpath)
>>>
>>> It's a bit different than how EE works, but I could imagine it causing
>>> fewer headaches when running on SE classpaths.
>>>
>>> Any thoughts/comments?
>>>
>>> John
>>>
>>> _______________________________________________
>>> cdi-dev mailing list
>>> cdi-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/cdi-dev
>>>
>>> Note that for all code provided on this list, the provider licenses the
>>> code under the Apache License, Version 2 (
>>> http://www.apache.org/licenses/LICENSE-2.0.html). For all other ideas
>>> provided on this list, the provider waives all patent and other
>>> intellectual property rights inherent in such information.
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20150301/6b10a609/attachment.html 


More information about the cdi-dev mailing list