title: Where can I place eligible candidates for CDI in a Glassfish v3 deployment?
body: <p>I have code in one jar (a.jar) which contains an <code>@Inject X x</code>.</p>
  
  <p>I want to satisfy the injection with an implementation in <em>another</em> jar (b.jar, being a valid bean archive etc.).</p>
  
  <p>To my understanding, I cannot deploy a.jar and b.jar in separate WAR standalone archives as these are independent CDI-wise.    I may be able to put b.jar in the lib folder that Glassfish provides to all deployments (but is this "pure Java 6 EE" and this mean I cannot deploy in the same way as a war or an ear?).  I may be able to provide b.jar in an EAR placed in lib along with a.war or a.jar but I am unfamiliar with this.</p>
  
  <p>My question is <strong>which options do I have for deploying a.jar and b.jar</strong> so that Glassfish (currently 3.0.1 but I will consider 3.1.1 if it works better) will correctly resolve this dependency?   I am looking for an exhaustive list.</p>
  
  <p>(EDIT:  I'd prefer a solution where b.jar can be deployed independently of a.jar)</p>