Right, I knew the workaround. We should just have consistent resolution logic such that a deployment that works with version 1 of a class, continues to work with version 2 provided that version 2 is backward compatibile. The case of adding single argument ctors to a class is guarenteed to be backward compatibile. I see this related issue: http://jira.jboss.com/jira/browse/JBMICROCONT-40 but its not about trying to have consistent resolution. Its really about telling the user that the current configuration is amiguous, and the choice made by the mc needs to be validated. Is there another issue I'm missing that uses the parameter type in the ctor selection? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978636#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...