title: How to choose a specific bean implementation without using qualifier?
body: <p>I am providing implementation of an injected service interface at runtime , through a <code>producer</code> in my app.</p>
  
  <p>Recently, another implementation of the same service interface has been created by someone in a collaborating team and that class has been added in a jar I can not avoid in my application. This is therefore throwing <code>ambiguous dependency exception</code> which I can obviously solve through a CDI qualifier on my producer method and at injection point. I wanted to ask if there is any other way to avoid this overhead. Can I use my <code>@Produces</code> method as the default implementation to make container ignore the second implementation? I added <code>@Default</code> annotation along with <code>@Produces</code> annotation on the producer method to check if this solves the problem since every injection by default is annotated with <code>@Default</code>. But that didn't work.</p>