Re: [cdi-dev] explicit bean archives discovery-mode 'annotated'
yes, but the pure fact that there is a beans.xml in the jar actually MAKE them a CDI lib
for EE6 and CDI-1.0 containers…
LieGrue,
strub
Am 06.03.2015 um 09:48 schrieb Romain Manni-Bucau
<rmannibucau(a)gmail.com>:
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*.
Romain Manni-Bucau
@rmannibucau | Blog | Github | LinkedIn | Tomitriber
2015-03-06 9:44 GMT+01:00 Mark Struberg <struberg(a)yahoo.de>:
While we are at it: the ’none’ mode is broken as well ;)
Imagine you have a jar in say DeltaSpike with a bean-discovery-mode=„none“.
Now let’s run this in CDI-1.1++ containers: all fine jar gets ignored
But in CDI-1.0 containers: whoops, due to having a beans.xml at all (marker interface)
the container must scan this jar.
There is simply no backward compatible way to tell the container that it should ignore a
jar.
LieGure,
strub