How to use version 2.4.2 of Demoiselle?

Asked

Viewed 239 times

0

I’m trying to use Demoiselle 2.4.2.

So I declared my pom Parent:

<parent>
    <groupId>br.gov.frameworkdemoiselle</groupId>
    <artifactId>demoiselle-servlet-parent</artifactId>
    <version>2.4.2</version>
</parent>

I also put in my pom the Property

<demoiselle.framework.version>2.4.2</demoiselle.framework.version>

But when it’s time for Jboss to come up, he makes that mistake:

10:27:34,342 ERROR [org.jboss.Msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.Unit." sislv-Ws.War". Weldstartservice: org.jboss.Msc.service.Startexception in service jboss.deployment.Unit." sislv-Ws.War". Weldstartservice: Failed to start service at org.jboss.Msc.service.Servicecontrollerimpl$Starttask.run(Servicecontrollerimpl.java:1936) [jboss-Msc-1.1.5.Final-Redhat-1.jar:1.1.5.Final-Redhat-1] at java.util.Concurrent.ThreadPoolExecutor.runWorker(Threadpoolexecutor.java:1145) [rt.jar:1.7.0_51] at java.util.Concurrent.Threadpoolexecutor$Worker.run(Threadpoolexecutor.java:615) [rt.jar:1.7.0_51] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] Caused by: org.jboss.Weld.exceptions.Deploymentexception: WELD-001409 Ambiguous dependencies for type [Httpservletrequest] with Qualifiers [@Default] at Injection point [[Parameter 1] of [method] @Default @Produces public br.gov.frameworkdemoiselle.internal.Producer.HttpSessionProducer.create(Httpservletrequest)]. Possible dependencies [[Producer Method [Httpservletrequest] with Qualifiers [@Any @Default] declared as [[method] @Default @Produces public br.gov.frameworkdemoiselle.internal.Producer.HttpServletRequestProducer.create()], Producer Method [Httpservletrequest] with Qualifiers [@Any @Default] declared as [[method] @Default @Produces public br.gov.frameworkdemoiselle.internal.Producer.HttpServletRequestProducer.create()]] at org.jboss.Weld.bootstrap.Validator.validateInjectionPoint(Validator.java:318) at org.jboss.Weld.bootstrap.Validator.validateInjectionPoint(Validator.java:284) at org.jboss.Weld.bootstrap.Validator.validateBean(Validator.java:147) at org.jboss.Weld.bootstrap.Validator.validateRIBean(Validator.java:167) at org.jboss.Weld.bootstrap.Validator.validateBeans(Validator.java:386) at org.jboss.Weld.bootstrap.Validator.validateDeployment(Validator.java:371) 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:1980) [jboss-Msc-1.1.5.Final-Redhat-1.jar:1.1.5.Final-Redhat-1] at org.jboss.Msc.service.Servicecontrollerimpl$Starttask.run(Servicecontrollerimpl.java:1913) [jboss-Msc-1.1.5.Final-Redhat-1.jar:1.1.5.Final-Redhat-1] ... 3 more

And also this:

10:27:34,378 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Report JBAS014777 service status: Services that fail on startup: service jboss.deployment.Unit." sislv-Ws.War". Weldstartservice: org.jboss.Msc.service.Startexception in service jboss.deployment.Unit." sislv-Ws.War". Weldstartservice: Failed to start service

Is the declaration of my Parent pom wrong? Or is something else missing?

Ah, my dependency section:

<dependencies>
    <dependency>
        <groupId>com.sun.xml.ws</groupId>
        <artifactId>jaxws-rt</artifactId>
        <version>2.2.10</version>
    </dependency>
    <dependency>
        <groupId>junit</groupId>
        <artifactId>junit</artifactId>
        <type>jar</type>
    </dependency>
    <dependency>
        <groupId>log4j</groupId>
        <artifactId>log4j</artifactId>
        <version>1.2.17</version>
        <type>jar</type>
    </dependency>
    <dependency>
        <groupId>org.jboss.logging</groupId>
        <artifactId>jboss-logging</artifactId>
        <version>3.2.1.Final</version>
    </dependency>
    <dependency>
        <groupId>org.mockito</groupId>
        <artifactId>mockito-all</artifactId>
        <version>1.10.19</version>
    </dependency>
    <dependency>
        <groupId>br.gov.serpro</groupId>
        <artifactId>sqladaj</artifactId>
        <version>2.0.0</version>
    </dependency>
    <dependency>
        <groupId>commons-io</groupId>
        <artifactId>commons-io</artifactId>
        <version>2.4</version>
    </dependency>
    <dependency>
        <groupId>javax</groupId>
        <artifactId>javaee-web-api</artifactId>
        <scope>provided</scope>
    </dependency>
    <dependency>
        <groupId>org.hibernate</groupId>
        <artifactId>hibernate-core</artifactId>
        <version>4.3.8.Final</version>
        <scope>provided</scope>
    </dependency>
    <dependency>
        <groupId>org.jboss.weld</groupId>
        <artifactId>weld-core</artifactId>
        <scope>provided</scope>
    </dependency>
    <dependency>
        <groupId>br.gov.frameworkdemoiselle</groupId>
        <artifactId>demoiselle-jpa</artifactId>
        <scope>compile</scope>
    </dependency>
    <dependency>
        <groupId>br.gov.frameworkdemoiselle</groupId>
        <artifactId>demoiselle-jta</artifactId>
        <scope>compile</scope>
    </dependency>
</dependencies>
demoiselle

  • The statement is correct yes. Are you upgrading the project version? If so, which version are you departing from? And which version of Jboss are you using? You can post the full POM.XML?

  • The project is new, but I am based on another project that was Demoiselle 2.4.0-BETA2

  • Ah, Jboss is the EAP 6.3.

  • Your project is passing the build? mnv clean ?

  • yes. but the problem seems to be right in Demoiselle, since he says that a class produced by Demoiselle is ambiguous for the CDI.

2 answers

2


Oops, problem solved itself. I’m not sure what took, but some things I did:

  • Add the repository

    <repository>
    <id>component.internal</id>
    <name>SERPRO Component Maven Repository</name>
    <url>http://archiva.desenv.serpro/repository/component-internal</url>
    <snapshots>
        <enabled>false</enabled>
    </snapshots>
    <releases>
        <enabled>true</enabled>
    </releases>
</repository>

  • And recompile the project so that in fact some dependencies were downloaded (I was only doing the m2eclipse update project).

  • Is there any way to mark the post as solved?

  • Your answer already indicates this. The "unanswered" are considered open.

  • @Leonardoleite after 48 hours you can mark your answer as accepted, as indicated here.

0

Browser other questions tagged demoiselle

You are not signed in. Login or sign up in order to post.