<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Weld SE only supports bean archives with beans.xml (all
bean-discovery-modes are supported in such an archive). Therefore,
it will only scan locations marked explicitly with beans.xml files,
not the entire classpath.<br>
<br>
<div class="moz-cite-prefix">On 03/04/2015 12:42 PM, John D. Ament
wrote:<br>
</div>
<blockquote
cite="mid:CAOqetn9L9e0W2+JCqDrMhoNSw-R4zP5JpCaJuVutZV51Lg-wdA@mail.gmail.com"
type="cite">
<div dir="ltr">Jozef,
<div><br>
</div>
<div>How does Weld SE deal with it right now? I run two
components, one using WildFly 8.2 and the other just SE mode
w/ Weld SE. I don't notice much of a difference in scanning,
even though the SE one needs to scan 50 mb of classpath.</div>
<div><br>
</div>
<div>John<br>
<br>
<div class="gmail_quote">On Wed, Mar 4, 2015 at 4:14 AM Jozef
Hartinger <<a moz-do-not-send="true"
href="mailto:jharting@redhat.com">jharting@redhat.com</a>>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> For EE assuming
bean-discovery-mode="annotated" by default if no
beans.xml is found is OK as the scope of scanning is
limited by the deployment. In SE however this would
require that we scan the entire classpath for scope
annotations, stereotypes, etc. I am therefore concerned
about the performance implications of this.</div>
<div text="#000000" bgcolor="#FFFFFF"><br>
<br>
<div>On 03/01/2015 04:18 PM, John D. Ament wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">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
:-)
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>Any concerns with that?<br>
<br>
John<br>
<br>
<div class="gmail_quote">On Sun, Mar 1, 2015 at
10:10 AM Romain Manni-Bucau <<a
moz-do-not-send="true"
href="mailto:rmannibucau@gmail.com"
target="_blank"
onclick="window.open('https://mail.google.com/mail/?view=cm&tf=1&to=rmannibucau@gmail.com&cc=&bcc=&su=&body=','_blank');return
false;">rmannibucau@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0
0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
<p dir="ltr">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.</p>
<div class="gmail_quote">Le 1 mars 2015 15:54,
"John D. Ament" <<a
moz-do-not-send="true"
href="mailto:john.d.ament@gmail.com"
target="_blank"
onclick="window.open('https://mail.google.com/mail/?view=cm&tf=1&to=john.d.ament@gmail.com&cc=&bcc=&su=&body=','_blank');return
false;">john.d.ament@gmail.com</a>> a
écrit :<br type="attribution">
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex">
<div dir="ltr">All,
<div><br>
</div>
<div>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)</div>
<div><br>
</div>
<div>It's a bit different than how EE
works, but I could imagine it causing
fewer headaches when running on SE
classpaths.</div>
<div><br>
</div>
<div>Any thoughts/comments?</div>
<div><br>
</div>
<div>John</div>
</div>
<br>
</blockquote>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px
#ccc solid;padding-left:1ex">_______________________________________________<br>
cdi-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:cdi-dev@lists.jboss.org"
target="_blank"
onclick="window.open('https://mail.google.com/mail/?view=cm&tf=1&to=cdi-dev@lists.jboss.org&cc=&bcc=&su=&body=','_blank');return
false;">cdi-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/cdi-dev"
target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
<br>
Note that for all code provided on this
list, the provider licenses the code under
the Apache License, Version 2 (<a
moz-do-not-send="true"
href="http://www.apache.org/licenses/LICENSE-2.0.html"
target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html</a>).
For all other ideas provided on this list,
the provider waives all patent and other
intellectual property rights inherent in
such information.<br>
</blockquote>
</div>
</blockquote>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
cdi-dev mailing list
<a moz-do-not-send="true" href="mailto:cdi-dev@lists.jboss.org" target="_blank" onclick="window.open('https://mail.google.com/mail/?view=cm&tf=1&to=cdi-dev@lists.jboss.org&cc=&bcc=&su=&body=','_blank');return false;">cdi-dev@lists.jboss.org</a>
<a moz-do-not-send="true" href="https://lists.jboss.org/mailman/listinfo/cdi-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a>
Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (<a moz-do-not-send="true" href="http://www.apache.org/licenses/LICENSE-2.0.html" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html</a>). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.</pre>
</blockquote>
<br>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>