Hi,
Some Java EE 6 apps still have issues with implicit scanning, even though
they don't use guava and sometimes it is not possible to put beans.xml file
into the problematic JARs. People are having issues with this when
migrating to Glassfish 4 or Payara from Glassfish 3. For example, an EJB
itself triggers CDI.
With Payara server, we are thinking of creating an option in
server-specific app descriptor to disable CDI completely either for whole
application or just for specific modules.
<
https://javaee-wg.slack.com/archives/cdi2_0-jsr-365/p1458060907000004>
I think it would make sense to consider some standardization of this
approach in CDI 2, as I've seen issues with this on stackoverflow also with
other app servers. Or is it already planned?
Ondrej