+++ This bug was initially created as a clone of Bug #1050963 +++ +++ This bug was initially created as a clone of Bug #1050959 +++ Description of problem: org.jboss.weld.exceptions.DeploymentException: WELD-001414 Bean name is ambiguous when deploying application Version-Release number of selected component (if applicable): EAP 6.0.1 How reproducible: See attached reproducer Steps to Reproduce: 1. Build project 2. Deploy --- Additional comment from on 2014-01-09 08:23:41 EST --- I test the project with EAP6.2.0 with the same result. 14:19:14,822 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-13) MSC000001: Failed to start service jboss.deployment.unit."twoWarProject.ear".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."twoWarProject.ear".WeldStartService: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45] Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414 Bean name is ambiguous. Name echo resolves to beans [Managed Bean [class org.jboss.tools.s2.EchoS2] with qualifiers [@Any @Default @Named], Managed Bean [class org.jboss.tools.s1.EchoS1] with qualifiers [@Any @Default @Named]] at org.jboss.weld.bootstrap.Validator.validateBeanNames(Validator.java:480) at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:374) at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:379) at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:64) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] ... 3 more 14:19:15,032 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "twoWarProject.ear" was rolled back with the following failure message: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"twoWarProject.ear\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"twoWarProject.ear\".WeldStartService: Failed to start service Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414 Bean name is ambiguous. Name echo resolves to beans [Managed Bean [class org.jboss.tools.s2.EchoS2] with qualifiers [@Any @Default @Named], Managed Bean [class org.jboss.tools.s1.EchoS1] with qualifiers [@Any @Default @Named]]"}} --- Additional comment from Jozef Hartinger on 2014-01-10 09:49:12 EST --- Fixed upstream. The fix will be available in Weld 1.1.17.Final
A draft release note has been added to the Docs Text field above.
Marek Schmidt <maschmid> updated the status of jira WELD-1584 to Reopened
The fix introduces a regression, https://bugzilla.redhat.com/show_bug.cgi?id=1057134 Changing back to assigned so it can be verified again properly together with the fix for #1057134.
Setting back to modified: https://github.com/jbossas/jboss-eap/pull/849
Jozef Hartinger <jharting> updated the status of jira WELD-1584 to Resolved
Verified on EAP 6.2.1.CP.CR3
Release note for 6.2.1 +'d