<div dir="ltr">that's not the issue of none. None was mainly designed for not cdi libs I think...which will never get modified for cdi *by design*.</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><br><span style="font-size:small">Romain Manni-Bucau</span><br><a href="https://twitter.com/rmannibucau" target="_blank">@rmannibucau</a> | <a href="http://rmannibucau.wordpress.com" target="_blank">Blog</a> | <a href="https://github.com/rmannibucau" target="_blank">Github</a> | <a href="https://www.linkedin.com/in/rmannibucau" target="_blank">LinkedIn</a> | <a href="http://www.tomitribe.com" target="_blank">Tomitriber</a></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">2015-03-06 9:44 GMT+01:00 Mark Struberg <span dir="ltr"><<a href="mailto:struberg@yahoo.de" target="_blank">struberg@yahoo.de</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">While we are at it: the ’none’ mode is broken as well ;)<br>
<br>
Imagine you have a jar in say DeltaSpike with a bean-discovery-mode=„none“.<br>
<br>
Now let’s run this in CDI-1.1++ containers: all fine jar gets ignored<br>
But in CDI-1.0 containers: whoops, due to having a beans.xml at all (marker interface) the container must scan this jar.<br>
<br>
<br>
There is simply no backward compatible way to tell the container that it should ignore a jar.<br>
<br>
LieGure,<br>
strub<br>
<br>
<br>
<br>
> Am 06.03.2015 um 09:15 schrieb Jozef Hartinger <<a href="mailto:jharting@redhat.com">jharting@redhat.com</a>>:<br>
<div class="HOEnZb"><div class="h5">><br>
><br>
> On 03/06/2015 09:03 AM, Romain Manni-Bucau wrote:<br>
>> Hi<br>
>><br>
>> Well you cant ask libs to change their programming model for it IMO. It is clearly a regression.<br>
>><br>
> Why not? Existing applications (empty beans.xml) will still work as before so there is no regression. If a lib wants to support bean-discovery-mode="annotated" then it has to adapt. It would be better if they did not have to but it's too late at this point.<br>
>> Another broken case is if any other IoC uses some of these annotations but doesnt rely on scanning. Now you scan the jar and can get surprises and even an Error.<br>
> Yes, this was a risk when implicit bean archives were introduced. This was in the end mitigated by only making CDI annotations as bean defining (most likely other IoC won't use CDI annotations) plus introducing bdm="none" mode.<br>
<br>
</div></div></blockquote></div><br></div>