-
Bug
-
Resolution: Done
-
Major
-
2.1.2.Final
-
None
Two session beans:
- same name
- implementing the same local interface (Animal) and declaring no other views
- deployed in two different modules, one module (A) is visible to the other (B).
When trying to inject Animal in the module B, once I get an instance of the first bean, next time an instance of the second one. The correct behavior would be DeploymentException due to ambiguous dependency.
interface Animal {}
@Stateful(name = "Animal") public class Cat implements Animal {}
@Stateful(name = "Animal") public class Dog implements Animal {}
public class Bar { @Inject private Animal animal; }
Deployment structure:
EAR
- ejb.jar: Animal, Dog
- test.war: Bar, Cat
- is duplicated by
-
WELD-1680 Only one of two EJBs with equal class name gets discovered
- Resolved