Red Hat Bugzilla – Bug 991462
Ambiguity when there are 2 implementations of one interface
Last modified: 2015-08-02 19:44:10 EDT
Created attachment 781960 [details] switchyard-example Description of problem: Assume that we have 2 implementations of the same interface, say BeanA and BeanB. In switchyard.xml we add only BeanA, promote it as service with file binding. After creating a file in the specified folder, BeanB is used instead of BeanA. Version-Release number of selected component (if applicable): SOA 6.0.0 DR7 How reproducible: Always Steps to Reproduce: 1. You can find a maven project in the attachment (it is also an eclipse project) 2. Deploy the project and create any file in JBOSS_HOME/bin/target/input Actual results: In log you will see output "B" (which means InfoBeanB was used) Expected results: In log you should see output "A"
This is because we automatically register beans as services and BeanA and BeanB are using the same service name. If you modify the annotation on InfoBeanB to look like this you should only see BeanA invoked: @Service(value=Info.class, name="InfoB") public class InfoBeanB implements Info { ...