<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<br>
<div class="moz-cite-prefix">On 05/27/2015 03:34 PM, Antoine
Sabot-Durand wrote:<br>
</div>
<blockquote
cite="mid:1C903501-7D3B-4164-BEF1-689CBD5ACBA7@sabot-durand.net"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">Le 27 mai 2015 à 14:57, John D. Ament <<a
moz-do-not-send="true"
href="mailto:john.d.ament@gmail.com" class="">john.d.ament@gmail.com</a>>
a écrit :</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">Jozef,<br class="">
<br class="">
Neither was lost, just not in scope for us to get EDR1 out
the door.
<div class=""><br class="">
</div>
<div class="">1. Antoine just now raised a separate issue.</div>
</div>
</div>
</blockquote>
<div><br class="">
</div>
<div>Perhaps we should state in EDR (in a side note) that it
will be addressed later and ask for user input. Wdyt?</div>
<div><br class="">
</div>
<div>Now if there are real issues in producing a EDR1 simple
with all discovery mode we could restrict the bean discovery
mode by supporting only “none” for the EDR1 (side note again).</div>
</div>
</blockquote>
It's neither "all" nor "none" discovery modes that I am concerned
about. It' implicit bean archives with no beans.xml that are
problematic.<br>
<blockquote
cite="mid:1C903501-7D3B-4164-BEF1-689CBD5ACBA7@sabot-durand.net"
type="cite">
<div>
<div><br class="">
</div>
<div>I understand that it’s not totally satisfying to not be
able to release all the feature at once, but let’s face it,
CDI-26 has been around for 4,5 years so splitting it in
smaller part to resolve them one by one seems the best
solution to get out Java SE support.</div>
<br class="">
<blockquote type="cite" class="">
<div class="">
<div dir="ltr" class="">
<div class=""><br class="">
</div>
<div class="">2. EDR1 infers that only a single CDI
instance is associated to a CDIProvider (so they're
1:1). We can move this after EDR1.</div>
</div>
</div>
</blockquote>
<div><br class="">
</div>
Unless Jozef has a proposal to solve the issue for getCdi() and
that we all agree on.</div>
<div><br class="">
</div>
<div>In the other case I will add a ticket for the multiple
container support in SE. That could even be wise since it’s a
controversial feature (Mark is against it), so having a specific
place to discuss it could be a better solution.</div>
<div><br class="">
</div>
<div>Jozef, any thought about this ?</div>
</blockquote>
Sounds good to me.<br>
<blockquote
cite="mid:1C903501-7D3B-4164-BEF1-689CBD5ACBA7@sabot-durand.net"
type="cite">
<div><br class="">
</div>
<div>Antoine</div>
<div>
<div><br class="">
</div>
<br class="">
<blockquote type="cite" class="">
<div class="">
<div dir="ltr" class="">
<div class="">John</div>
</div>
<br class="">
<div class="gmail_quote">
<div dir="ltr" class="">On Wed, May 27, 2015 at 5:21 AM
Jozef Hartinger <<a moz-do-not-send="true"
href="mailto:jharting@redhat.com" class="">jharting@redhat.com</a>>
wrote:<br class="">
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF" class=""> Hi all,<br
class="">
<br class="">
I'd like to raise several concerns with the CDI-26
resolution that I either forgot to raise before or
were lost in the process.<br class="">
<br class="">
1) Bean discovery in SE<br class="">
<br class="">
I was under the impression that the task to define
bean discovery for SE was postponed post EDR1 yet the
PR for CDI-26 that has been merged defines bean
discovery in SE explicitly
<a moz-do-not-send="true"
href="https://github.com/johnament/cdi/commit/a112489f248ab9074da4d0a81a28abc67f8cdbe5#diff-ffe540480772deae967ea309fa5f3976R44"
target="_blank" class="">https://github.com/johnament/cdi/commit/a112489f248ab9074da4d0a81a28abc67f8cdbe5#diff-ffe540480772deae967ea309fa5f3976R44</a><br
class="">
<br class="">
I am concerned about the way it is defined currently
as it requires that the CDI implementation eagerly
loads/scans each and every class found on the
classpath during initialization. Due to performance
implications of this I am convinced that this is not
the desired behavior. It may be useful to support this
for some use-cases with e.g. a special container mode
but I doubt this should be the default behavior for
CDI in SE. Let's not forget to fix this.<br class="">
<br class="">
2) CDIProvider.isInitialized()<br class="">
<br class="">
First of all, good job on removing the constraints,
preventing multiple parallel container support, from
the API. One missing piece seems to be
CDIProvider.isInitialized(). The JavaDoc says: "
Determines whether or not this CDIProvider has been
initialized or not"<br class="">
<br class="">
My understanding is that it is supposed to indicate
whether a CDI object is in initialized state yet or
whether it has been shut down. If my understanding is
correct then this method should probably be moved to
the CDI class instead. Due to the possible 1-to-n
mapping between CDI and CDIProvider it's not correct
to have this method on CDIProvider<br class="">
<br class="">
Jozef<br class="">
</div>
_______________________________________________<br
class="">
cdi-dev mailing list<br class="">
<a moz-do-not-send="true"
href="mailto:cdi-dev@lists.jboss.org" target="_blank"
class="">cdi-dev@lists.jboss.org</a><br class="">
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/cdi-dev"
target="_blank" class="">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br
class="">
<br class="">
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" class="">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.</blockquote>
</div>
_______________________________________________<br class="">
cdi-dev mailing list<br class="">
<a moz-do-not-send="true"
href="mailto:cdi-dev@lists.jboss.org" class="">cdi-dev@lists.jboss.org</a><br
class="">
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/cdi-dev">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br class="">
<br class="">
Note that for all code provided on this list, the provider
licenses the code under the Apache License, Version 2
(<a class="moz-txt-link-freetext" href="http://www.apache.org/licenses/LICENSE-2.0.html">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.</div>
</blockquote>
</div>
<br class="">
</blockquote>
<br>
</body>
</html>