0 Replies Latest reply on Aug 24, 2012 2:49 PM by Mauricio Salatino

    Duplicated Interceptor definition is breaking the deployment

    Mauricio Salatino Master

      Hi,

      I have a very seriuos problem which is breaking the weld container when it is trying to start:

       

      0:00:01.139 [WARN] Failed startup of context org.jboss.errai.cdi.server.gwt.JettyLauncher$WebAppContextWithReload@4870888a{/,/Users/salaboy/Projects/droolsjbpm/form-builder-ng/form-builder-ng-showcase/target/form-builder-ng-showcase-0.1-SNAPSHOT}

      org.jboss.weld.exceptions.DeploymentException: WELD-001416 Enabled interceptor class [<class>org.jboss.seam.transaction.TransactionInterceptor</class> in jar:file:/Users/salaboy/Projects/droolsjbpm/form-builder-ng/form-builder-ng-showcase/target/form-builder-ng-showcase-0.1-SNAPSHOT/WEB-INF/lib/form-builder-services-cdi-0.1-SNAPSHOT.jar!/META-INF/beans.xml@27, <class>org.jboss.seam.transaction.TransactionInterceptor</class> in jar:file:/Users/salaboy/Projects/droolsjbpm/form-builder-ng/form-builder-ng-showcase/target/form-builder-ng-showcase-0.1-SNAPSHOT/WEB-INF/lib/jbpm-human-task-core-cdi-5.4.0-SNAPSHOT.jar!/META-INF/beans.xml@35] specified twice

                at org.jboss.weld.manager.Enabled.createMetadataMap(Enabled.java:123)

                at org.jboss.weld.manager.Enabled.<init>(Enabled.java:96)

                at org.jboss.weld.manager.Enabled.of(Enabled.java:79)

                at org.jboss.weld.bootstrap.BeanDeployment.<init>(BeanDeployment.java:114)

                at org.jboss.weld.bootstrap.WeldBootstrap$DeploymentVisitor.visit(WeldBootstrap.java:184)

                at org.jboss.weld.bootstrap.WeldBootstrap$DeploymentVisitor.visit(WeldBootstrap.java:153)

                at org.jboss.weld.bootstrap.WeldBootstrap.startContainer(WeldBootstrap.java:284)

                at org.jboss.errai.container.CDIServletStateListener.contextInitialized(CDIServletStateListener.java:105)

                at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:543)

                at org.mortbay.jetty.servlet.Context.startContext(Context.java:136)

                at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1220)

                at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:513)

                at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:448)

                at org.jboss.errai.cdi.server.gwt.JettyLauncher$WebAppContextWithReload.doStart(JettyLauncher.java:486)

                at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)

                at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)

                at org.mortbay.jetty.handler.RequestLogHandler.doStart(RequestLogHandler.java:115)

                at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)

                at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)

                at org.mortbay.jetty.Server.doStart(Server.java:222)

                at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)

                at org.jboss.errai.cdi.server.gwt.JettyLauncher.start(JettyLauncher.java:692)

                at com.google.gwt.dev.DevMode.doStartUpServer(DevMode.java:509)

                at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:1068)

                at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:811)

                at com.google.gwt.dev.DevMode.main(DevMode.java:311)

       

      This exception is caused because I have a Web App which contains two dependencies. Each of these two dependencies are using seam-persistence which push me to set up the Transactional Interceptor. Both modules (the dependencies) works fine, but when I combine them into the same application everything breaks.

      Can someone suggest me a good practice about how to avoid these kinds of problems?

      The beans.xml files needs to be in the way they are now.. which leads me to think that this is a seam-persistence bug.

       

      Cheers