[weld-dev] Weld 2.0.0.Beta6 released

[Jozef Hartinger]

Hi Daniel,

please file an issue at https://issues.jboss.org/browse/WELD. If 
possible include the sample application for us to be able to reproduce 
easily.

Jozef

On 03/19/2013 08:59 PM, Daniel Sachse wrote:
> Hey all,
>
> I just tried JBoss AS 7.1.1 with Weld 2.0.0.Beta3 and Weld 
> 2.0.0.Beta6, JBoss EAP 6.1 Alpha 1 with Weld 2.0.0.Beta6 and I have 
> encountered the following issue when deploying a small sample application:
>
> 20:55:52,495 ERROR [org.jboss.msc.service.fail] (MSC service thread 
> 1-14) MSC00001: Failed to start service 
> jboss.deployment.unit."Foodeys.war".WeldService: 
> org.jboss.msc.service.StartException in service 
> jboss.deployment.unit."Foodeys.war".WeldService: 
> org.jboss.weld.exceptions.DeploymentException: WELD-001414 Bean name 
> is ambiguous. Name csfFLOWDISCOVERYCDIHELPER resolves to beans 
> [Managed Bean [class com.sun.faces.flow.FlowDiscoveryCDIHelper] with 
> qualifiers [@Default @Named @Any], Managed Bean [class 
> com.sun.faces.flow.FlowDiscoveryCDIHelper] with qualifiers [@Default 
> @Named @Any]]
> at org.jboss.as.weld.services.WeldService.start(WeldService.java:84)
> at 
> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) 
> [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at 
> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) 
> [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 
> [rt.jar:1.7.0_15]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 
> [rt.jar:1.7.0_15]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_15]
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414 
> Bean name is ambiguous. Name csfFLOWDISCOVERYCDIHELPER resolves to 
> beans [Managed Bean [class com.sun.faces.flow.FlowDiscoveryCDIHelper] 
> with qualifiers [@Default @Named @Any], Managed Bean [class 
> com.sun.faces.flow.FlowDiscoveryCDIHelper] with qualifiers [@Default 
> @Named @Any]]
> at 
> org.jboss.weld.bootstrap.ConcurrentValidator$5.doWork(ConcurrentValidator.java:133)
> at 
> org.jboss.weld.bootstrap.ConcurrentValidator$5.doWork(ConcurrentValidator.java:129)
> at 
> org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60)
> at 
> org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) 
> [rt.jar:1.7.0_15]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) 
> [rt.jar:1.7.0_15]
> ... 3 more
>
> Do you know where this comes from and how one can solve it?
>
> Cheers,
>
> Daniel
>
> Am 18.03.2013 um 15:41 schrieb Jozef Hartinger <jharting at redhat.com 
> <mailto:jharting at redhat.com>>:
>
>> Hi all,
>>
>> Weld 2.0.0.Beta6 has been released. We are not quite yet at being a
>> feature-complete implementation of CDI 1.1 but we are getting there. You
>> can test it yourself if you take JBoss EAP 6.1 Alpha (from
>> http://www.jboss.org/jbossas/downloads/) and patch it using Weld 2
>> installer from here https://github.com/weld/as7-weld-subsystem (use the
>> 2.0.0.Beta6 tag).
>>
>> Jozef
>> _______________________________________________
>> weld-dev mailing list
>> weld-dev at lists.jboss.org <mailto:weld-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/weld-dev
>
>
>
> _______________________________________________
> weld-dev mailing list
> weld-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/weld-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/weld-dev/attachments/20130322/666660b9/attachment.html