<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">After some discussion with <font class="Apple-style-span" face="'Lucida Grande', Geneva, Verdana, Arial, sans-serif">Tihomir I have added an @XmlConfigured annotation to seam-xml. This prevents the bean from being installed, so it is possible to create beans with ambiguous dependencies and allow the user to pick which one they want with XML configuration. </font><div><font class="Apple-style-span" face="'Lucida Grande', Geneva, Verdana, Arial, sans-serif"><br></font></div><div><font class="Apple-style-span" face="'Lucida Grande', Geneva, Verdana, Arial, sans-serif">The problem with this is that if you want to use it you now need a compile time dependency on seam-xml just to get one annotation. Should we have a @DoNotInstall (or whatever) annotation in weld-extensions instead, or is a compile time dependency on seam-xml ok? </font></div><div><font class="Apple-style-span" face="'Lucida Grande', Geneva, Verdana, Arial, sans-serif"><br></font></div><div><font class="Apple-style-span" face="'Lucida Grande', Geneva, Verdana, Arial, sans-serif">Tihomir has pointed out that @XmlConfigured makes it much clearer what is going on, and tells anyone reading the code to look in beans.xml, and I am inclined to agree with him, but I would like to know what everyone else thinks. </font></div><div><font class="Apple-style-span" face="'Lucida Grande', Geneva, Verdana, Arial, sans-serif"><br></font></div><div><font class="Apple-style-span" face="'Lucida Grande', Geneva, Verdana, Arial, sans-serif">Stuart<br></font><div><font class="Apple-style-span" face="'Lucida Grande', Geneva, Verdana, Arial, sans-serif"><br></font></div><div><font class="Apple-style-span" face="'Lucida Grande', Geneva, Verdana, Arial, sans-serif"><br></font></div></div></body></html>