<div dir="ltr"><span class="">Hi,<br></span><div><div><span class=""><br></span></div><span class="">Some Java EE 6 apps still have issues with implicit scanning, even 
though they don&#39;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.<br></span><span class=""></span><br><span class=""></span><div><span class="">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. </span>

                


                        




                <div class="">


                

        </div>


                

                

        <div class="">
                
                </div><a href="https://javaee-wg.slack.com/archives/cdi2_0-jsr-365/p1458060907000004" target="new_1458059692471" title="Today at 5:55:07 PM&lt;br&gt;Click to open in archives" class=""><span class=""></span></a><div class="">
                <span class=""><span class=""></span></span>
        </div>

        <div class="">
                        
                
                <br><span class=""></span>
                

                        <span class="">I think it would make sense to consider some standardization of this approach in CDI 2, as I&#39;ve seen issues with this on stackoverflow also with other app servers. Or is it already planned?<br><br></span></div><div class=""><span class="">Ondrej<br></span></div></div></div></div>