[
https://issues.apache.org/jira/browse/DELTASPIKE-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14075615#comment-14075615
]
Paa Kojo Konduah Amos commented on DELTASPIKE-678:
--------------------------------------------------
I think i figured out what might be the problem. I am using PicketLink as well
in my project. By definition of PicketLink BOM, Deltaspike libraries are added
by default. What this means is, if i am looking forward to using Deltaspike, i
can straight away add the modules without necessarily declaring Deltaspike
again in my POM.
So i summary this is what i did to produce the exception(Caused by:
org.jboss.weld.exceptions.DeploymentException: WELD-001414: Bean name is
ambiguous. Name dsWindowContext resolves to beans: ) again:
1. Define the PICKETLINK BOM.
<!-- Dependency Management for PicketLink and Java EE 6.0. -->
<dependency>
<groupId>org.picketlink</groupId>
<artifactId>picketlink-javaee-6.0</artifactId>
<version>${version.picketlink.javaee.bom}</version>
<scope>import</scope>
<type>pom</type>
</dependency>
2. Define the one-jar Picketlink Dependency.
<!-- PicketLink Uber Dependency. It provides all PicketLink dependencies
from a single JAR. You still can define each module
separately, if you want
to. -->
<dependency>
<groupId>org.picketlink</groupId>
<artifactId>picketlink</artifactId>
</dependency>
2. Define Deltaspike maven dependency.
<!-- Deltaspike Core -->
<dependency>
<groupId>org.apache.deltaspike.core</groupId>
<artifactId>deltaspike-core-api</artifactId>
<version>${deltaspike.version}</version><!--$NO-MVN-MAN-VER$ -->
<scope>compile</scope>
</dependency>
<dependency>
<groupId>org.apache.deltaspike.core</groupId>
<artifactId>deltaspike-core-impl</artifactId>
<version>${deltaspike.version}</version><!--$NO-MVN-MAN-VER$ -->
<scope>runtime</scope>
</dependency>
> Deployment of Deltaspike 1.0.0 fails on WILDFLY 8.1
> ---------------------------------------------------
>
> Key: DELTASPIKE-678
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-678
> Project: DeltaSpike
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.0
> Environment: JBoss Dev Studio, JSE 1.6/1.7 , Wildfly 8.1
> Reporter: Paa Kojo Konduah Amos
>
> on addition of the Deltaspike-core dependency in my pom.xml....wildfly 8.1
> fails at deployment time.
> 01:45:08,481 INFO [org.apache.deltaspike.core.util.ProjectStageProducer]
> (MSC service thread 1-4) Computed the following DeltaSpike ProjectStage:
> Production
> 01:45:12,813 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4)
> MSC000001: Failed to start service
> jboss.deployment.unit."jwi.war".WeldStartService:
> org.jboss.msc.service.StartException in service
> jboss.deployment.unit."jwi.war".WeldStartService: Failed to start service
> at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
> [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> [rt.jar:1.7.0_65]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> [rt.jar:1.7.0_65]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414: Bean
> name is ambiguous. Name dsWindowContext resolves to beans:
> - Producer Method [WindowContext] with qualifiers [@Default @Named @Any]
> declared as [[BackedAnnotatedMethod] @Produces @Named @Dependent public
> org.apache.deltaspike.core.impl.scope.window.WindowContextProducer.getWindowContext()],
> - Producer Method [WindowContext] with qualifiers [@Default @Named @Any]
> declared as [[BackedAnnotatedMethod] @Produces @Named @Dependent public
> org.apache.deltaspike.core.impl.scope.window.WindowContextProducer.getWindowContext()]
> at
> org.jboss.weld.bootstrap.ConcurrentValidator$5.doWork(ConcurrentValidator.java:134)
> at
> org.jboss.weld.bootstrap.ConcurrentValidator$5.doWork(ConcurrentValidator.java:130)
> 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.run(FutureTask.java:262)
> [rt.jar:1.7.0_65]
> ... 3 more
> 01:45:12,824 ERROR [org.jboss.as.controller.management-operation] (Controller
> Boot Thread) JBAS014613: Operation ("deploy") failed - address:
> ([("deployment" => "jwi.war")]) - failure description: {"JBAS014671: Failed
> services" => {"jboss.deployment.unit.\"jwi.war\".WeldStartService" =>
> "org.jboss.msc.service.StartException in service
> jboss.deployment.unit.\"jwi.war\".WeldStartService: Failed to start service
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414:
> Bean name is ambiguous. Name dsWindowContext resolves to beans:
> - Producer Method [WindowContext] with qualifiers [@Default @Named @Any]
> declared as [[BackedAnnotatedMethod] @Produces @Named @Dependent public
> org.apache.deltaspike.core.impl.scope.window.WindowContextProducer.getWindowContext()],
> - Producer Method [WindowContext] with qualifiers [@Default @Named @Any]
> declared as [[BackedAnnotatedMethod] @Produces @Named @Dependent public
> org.apache.deltaspike.core.impl.scope.window.WindowContextProducer.getWindowContext()]"}}
> 01:45:12,919 INFO [org.jboss.as.server] (ServerService Thread Pool -- 28)
> JBAS018559: Deployed "jwi.war" (runtime-name : "jwi.war")
> 01:45:12,928 INFO [org.jboss.as.controller] (Controller Boot Thread)
> JBAS014774: Service status report
> JBAS014777: Services which failed to start: service
> jboss.deployment.unit."jwi.war".WeldStartService:
> org.jboss.msc.service.StartException in service
> jboss.deployment.unit."jwi.war".WeldStartService: Failed to start service
--
This message was sent by Atlassian JIRA
(v6.2#6252)
