13 Replies Latest reply on Mar 11, 2014 6:14 PM by Roger Lee

    Seam 2.3.1.Final on WildFly 8.0.0.Final-929

    Roger Lee Apprentice

      I've been trying to move a live Seam App from JBoss 6.1.0 Final to WildFly 8.0.0, with no success.

       

      I have now created the basic Seam App using Seam Gen from 2.3.1.Final.

       

      When I deploy the EAR and enable it I get the errors below.

       

      Can someone (from RedHat) give me a definitive answer to whether Seam 2.3.1.Final will deploy on WildFly 8.x? TIA.

       

      C:\wildfly-8.0.0.Final-929\bin>standalone.bat  -server-config=standalone-full.xml

      Calling "C:\wildfly-8.0.0.Final-929\bin\standalone.conf.bat"

      Setting JAVA property to "C:\Program Files\Java\jdk1.7.0_40\\bin\java"

      ===============================================================================

        JBoss Bootstrap Environment

        JBOSS_HOME: "C:\wildfly-8.0.0.Final-929"

       

       

        JAVA: "C:\Program Files\Java\jdk1.7.0_40\\bin\java"

       

       

        JAVA_OPTS: "-client -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Djava.net.preferIPv4Stack=true -Djboss.modules.sy

      stem.pkgs=org.jboss.byteman"

       

       

      ===============================================================================

       

       

      20:49:07,156 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final

      20:49:08,472 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.0.Final

      20:49:08,598 INFO  [org.jboss.as] (MSC service thread 1-6) JBAS015899: WildFly 8.0.0.Final-SNAPSHOT "WildFly" starting

      20:49:12,348 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (managem

      ent-http)

      20:49:12,372 INFO  [org.xnio] (MSC service thread 1-1) XNIO version 3.2.0.Final

      20:49:12,381 INFO  [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.2.0.Final

      20:49:12,459 INFO  [org.jboss.as.jacorb] (ServerService Thread Pool -- 37) JBAS016300: Activating JacORB Subsystem

      20:49:12,473 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 36) JBAS010280: Activating Infinispan subsystem.

      20:49:12,500 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 47) JBAS011800: Activating Naming Subsystem

      20:49:12,501 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 56) JBAS015537: Activating WebServices Extension

      20:49:12,491 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 52) JBAS013171: Activating Security Subsystem

      20:49:12,503 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 43) JBAS012615: Activated the following JSF Implementations: [main]

      20:49:12,620 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017502: Undertow 1.0.0.CR1 starting

      20:49:12,626 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) JBAS017502: Undertow 1.0.0.CR1 starting

      20:49:12,632 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-5) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.3.Final)

      20:49:12,636 INFO  [org.jboss.as.security] (MSC service thread 1-6) JBAS013170: Current PicketBox version=4.0.20.Final

      20:49:12,889 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) JBAS017527: Creating file handler for path C:\wildfly-

      8.0.0.Final-929/welcome-content

      20:49:12,900 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017525: Started server default-server.

      20:49:12,904 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017531: Host default-host starting

      20:49:13,426 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 31) JBAS010404: Deploying non-JDBC-complian

      t driver class com.mysql.jdbc.Driver (version 5.1)

      20:49:13,429 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) JBAS010417: Started Driver service with driver-name = my

      sql

      20:49:13,479 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 31) JBAS010403: Deploying JDBC-compliant dr

      iver class org.h2.Driver (version 1.3)

      20:49:13,481 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010417: Started Driver service with driver-name = h2

       

       

      20:49:13,497 INFO  [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service

      20:49:13,498 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-6) JBAS015400: Bound mail session [java:jboss/mail/Default]

      20:49:13,703 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) JBAS010400: Bound data source [java:jboss/ViViFY

      dDatasource]

      20:49:13,713 INFO  [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.0.Final

      20:49:13,888 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017519: Undertow HTTP listener default listening on /127.0.

      0.1:8080

      20:49:13,891 INFO  [org.jboss.as.remoting] (MSC service thread 1-5) JBAS017100: Listening on 127.0.0.1:9999

      20:49:13,894 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for dir

      ectory C:\wildfly-8.0.0.Final-929\standalone\deployments

      20:49:14,035 WARN  [org.jboss.as.messaging] (MSC service thread 1-7) JBAS011600: AIO wasn't located on this platform, it will fall back to u

      sing pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal

      20:49:14,131 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) JBAS010400: Bound data source [java:jboss/dataso

      urces/ExampleDS]

      20:49:14,136 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221000: live server is starting with configuration HornetQ

      Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=C:\wildfly-8.0.0.Final-929\standalone\data\messagingjournal,bi

      ndingsDirectory=C:\wildfly-8.0.0.Final-929\standalone\data\messagingbindings,largeMessagesDirectory=C:\wildfly-8.0.0.Final-929\standalone\da

      ta\messaginglargemessages,pagingDirectory=C:\wildfly-8.0.0.Final-929\standalone\data\messagingpaging)

      20:49:14,137 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221006: Waiting to obtain live lock

      20:49:14,318 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221013: Using NIO Journal

      20:49:14,457 INFO  [io.netty.util.internal.PlatformDependent] (ServerService Thread Pool -- 58) Your platform does not provide complete low-

      level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to avoid potential system

      unstability.

      20:49:14,486 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221043: Adding protocol support CORE

      20:49:14,526 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221043: Adding protocol support AMQP

      20:49:14,530 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221043: Adding protocol support STOMP

      20:49:14,677 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221034: Waiting to obtain live lock

      20:49:14,680 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221035: Live Server Obtained live lock

      20:49:14,694 WARN  [jacorb.codeset] (MSC service thread 1-8) Warning - unknown codeset (Cp1252) - defaulting to ISO-8859-1

      20:49:14,938 INFO  [org.jboss.as.jacorb] (MSC service thread 1-8) JBAS016330: CORBA ORB Service started

      20:49:15,661 INFO  [org.jboss.messaging] (MSC service thread 1-4) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled

      by http-acceptor acceptor

      20:49:15,663 INFO  [org.jboss.messaging] (MSC service thread 1-1) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled

      by http-acceptor-throughput acceptor

      20:49:15,679 INFO  [org.jboss.as.jacorb] (MSC service thread 1-7) JBAS016328: CORBA Naming Service started

      20:49:15,697 INFO  [org.jboss.ws.common.management] (MSC service thread 1-3) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.2.

      3.Final

      20:49:15,754 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221007: Server is now live

      20:49:15,755 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221001: HornetQ Server version 2.4.1.Final (Fast Hornet, 12

      4) [951e9d00-8d23-11e3-bdfc-95d335c09bd1]

      20:49:15,783 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name java:jboss/exp

      orted/jms/RemoteConnectionFactory

      20:49:15,786 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name java:/Connecti

      onFactory

      20:49:15,828 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-8) JBAS010406: Registered connection factory java:/JmsXA

      20:49:16,036 INFO  [org.hornetq.ra] (MSC service thread 1-8) HornetQ resource adaptor started

      20:49:16,037 INFO  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service

      thread 1-8) IJ020002: Deployed: file://RaActivatorhornetq-ra

      20:49:16,039 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-4) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]

      20:49:16,039 INFO  [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011601: Bound messaging object to jndi name java:jboss/DefaultJMSCo

      nnectionFactory

      20:49:16,267 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/manageme

      nt

      20:49:16,268 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990

      20:49:16,271 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.0.0.Final-SNAPSHOT "WildFly" started in 11431ms - Started 2

      22 of 269 services (87 services are lazy, passive or on-demand)

      20:49:40,875 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "ViViFYdServer.ear" (runtime

      -name: "ViViFYdServer.ear")

      20:49:44,380 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry derbyLocale_cs.jar in /C:/wildfly-

      8.0.0.Final-929/bin/content/ViViFYdServer.ear/lib/derby.jar  does not point to a valid jar for a Class-Path reference.

      20:49:44,381 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry derbyLocale_de_DE.jar in /C:/wildf

      ly-8.0.0.Final-929/bin/content/ViViFYdServer.ear/lib/derby.jar  does not point to a valid jar for a Class-Path reference.

      20:49:44,391 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry derbyLocale_es.jar in /C:/wildfly-

      8.0.0.Final-929/bin/content/ViViFYdServer.ear/lib/derby.jar  does not point to a valid jar for a Class-Path reference.

      20:49:44,397 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry derbyLocale_fr.jar in /C:/wildfly-

      8.0.0.Final-929/bin/content/ViViFYdServer.ear/lib/derby.jar  does not point to a valid jar for a Class-Path reference.

      20:49:44,404 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry derbyLocale_hu.jar in /C:/wildfly-

      8.0.0.Final-929/bin/content/ViViFYdServer.ear/lib/derby.jar  does not point to a valid jar for a Class-Path reference.

      20:49:44,422 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry derbyLocale_it.jar in /C:/wildfly-

      8.0.0.Final-929/bin/content/ViViFYdServer.ear/lib/derby.jar  does not point to a valid jar for a Class-Path reference.

      20:49:44,440 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry derbyLocale_ja_JP.jar in /C:/wildf

      ly-8.0.0.Final-929/bin/content/ViViFYdServer.ear/lib/derby.jar  does not point to a valid jar for a Class-Path reference.

      20:49:44,448 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry derbyLocale_ko_KR.jar in /C:/wildf

      ly-8.0.0.Final-929/bin/content/ViViFYdServer.ear/lib/derby.jar  does not point to a valid jar for a Class-Path reference.

      20:49:44,455 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry derbyLocale_pl.jar in /C:/wildfly-

      8.0.0.Final-929/bin/content/ViViFYdServer.ear/lib/derby.jar  does not point to a valid jar for a Class-Path reference.

      20:49:44,475 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry derbyLocale_pt_BR.jar in /C:/wildf

      ly-8.0.0.Final-929/bin/content/ViViFYdServer.ear/lib/derby.jar  does not point to a valid jar for a Class-Path reference.

      20:49:44,483 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry derbyLocale_ru.jar in /C:/wildfly-

      8.0.0.Final-929/bin/content/ViViFYdServer.ear/lib/derby.jar  does not point to a valid jar for a Class-Path reference.

      20:49:44,500 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry derbyLocale_zh_CN.jar in /C:/wildf

      ly-8.0.0.Final-929/bin/content/ViViFYdServer.ear/lib/derby.jar  does not point to a valid jar for a Class-Path reference.

      20:49:44,519 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015960: Class Path entry derbyLocale_zh_TW.jar in /C:/wildf

      ly-8.0.0.Final-929/bin/content/ViViFYdServer.ear/lib/derby.jar  does not point to a valid jar for a Class-Path reference.

      20:49:44,564 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "null" (runtime-name: "ViViF

      YdServer.war")

      20:49:44,564 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "null" (runtime-name: "ViViF

      YdServer.jar")

      20:49:44,564 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "null" (runtime-name: "jboss

      -seam.jar")

      20:49:45,966 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015850: /C:/wildfly-8.0.0.Final-929/bin/content/ViViFYdServ

      er.ear/ViViFYdServer.war/WEB-INF/jboss-deployment-structure.xml in subdeployment ignored. jboss-deployment-structure.xml is only parsed for

      top level deployments.

      20:49:45,971 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry iText-toolbox.jar in /C:/wildfly-8

      .0.0.Final-929/bin/content/ViViFYdServer.ear/ViViFYdServer.war/WEB-INF/lib/itext.jar  does not point to a valid jar for a Class-Path referen

      ce.

      20:49:45,973 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry iText-toolbox-2.1.2.jar in /C:/wil

      dfly-8.0.0.Final-929/bin/content/ViViFYdServer.ear/ViViFYdServer.war/WEB-INF/lib/itext.jar  does not point to a valid jar for a Class-Path r

      eference.

      20:49:45,975 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry bcmail-jdk14-138.jar in /C:/wildfl

      y-8.0.0.Final-929/bin/content/ViViFYdServer.ear/ViViFYdServer.war/WEB-INF/lib/itext.jar  does not point to a valid jar for a Class-Path refe

      rence.

      20:49:45,977 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry bcprov-jdk14-138.jar in /C:/wildfl

      y-8.0.0.Final-929/bin/content/ViViFYdServer.ear/ViViFYdServer.war/WEB-INF/lib/itext.jar  does not point to a valid jar for a Class-Path refe

      rence.

      20:49:46,444 INFO  [org.jboss.as.jpa] (MSC service thread 1-6) JBAS011401: Read persistence.xml for ViViFYdServerEntityManagerFactory

      20:49:46,651 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS018567: Deployment "deployment.ViViFYdServer.ear" is using

      a private module ("com.sun.jsf-impl:main") which may be changed or removed in future versions without notice.

      20:49:46,652 WARN  [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS018567: Deployment "deployment.ViViFYdServer.ear" is using

      a private module ("com.sun.jsf-impl:main") which may be changed or removed in future versions without notice.

      20:49:46,791 INFO  [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002: Processing weld deployment ViViFYdServer.ear

      20:49:46,977 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-3) HV000001: Hibernate Validator 5.0.3.Final

      20:49:47,147 INFO  [org.jboss.weld.deployer] (MSC service thread 1-8) JBAS016002: Processing weld deployment jboss-seam.jar

      20:49:47,173 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-8) JNDI bindings f

      or session bean named EjbSynchronizations in deployment unit subdeployment "jboss-seam.jar" of deployment "ViViFYdServer.ear" are as follows

      :

       

       

              java:global/ViViFYdServer/jboss-seam/EjbSynchronizations!org.jboss.seam.transaction.LocalEjbSynchronizations

              java:app/jboss-seam/EjbSynchronizations!org.jboss.seam.transaction.LocalEjbSynchronizations

              java:module/EjbSynchronizations!org.jboss.seam.transaction.LocalEjbSynchronizations

              java:global/ViViFYdServer/jboss-seam/EjbSynchronizations

              java:app/jboss-seam/EjbSynchronizations

              java:module/EjbSynchronizations

       

       

      20:49:47,183 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-8) JNDI bindings f

      or session bean named TimerServiceDispatcher in deployment unit subdeployment "jboss-seam.jar" of deployment "ViViFYdServer.ear" are as foll

      ows:

       

       

              java:global/ViViFYdServer/jboss-seam/TimerServiceDispatcher!org.jboss.seam.async.LocalTimerServiceDispatcher

              java:app/jboss-seam/TimerServiceDispatcher!org.jboss.seam.async.LocalTimerServiceDispatcher

              java:module/TimerServiceDispatcher!org.jboss.seam.async.LocalTimerServiceDispatcher

              java:global/ViViFYdServer/jboss-seam/TimerServiceDispatcher

              java:app/jboss-seam/TimerServiceDispatcher

              java:module/TimerServiceDispatcher

       

       

      20:49:47,200 INFO  [org.jboss.weld.deployer] (MSC service thread 1-5) JBAS016002: Processing weld deployment ViViFYdServer.war

      20:49:47,220 ERROR [org.jboss.as.controller.management-operation] (XNIO-1 task-2) JBAS014613: Operation ("deploy") failed - address: ([("dep

      loyment" => "ViViFYdServer.ear")]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => [

          "jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.EjbSynchronizations.ORB is missing [jboss.naming.context.java.comp.ViViFYdServe

      r.jboss-seam.EjbSynchronizations]",

          "jboss.deployment.unit.\"ViViFYdServer.ear\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"ViViFYdServer.ear\".beanmana

      ger]",

          "jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.EjbSynchronizations.HandleDelegate is missing [jboss.naming.context.java.comp.V

      iViFYdServer.jboss-seam.EjbSynchronizations]",

          "jboss.deployment.subunit.\"ViViFYdServer.ear\".\"jboss-seam.jar\".weld.weldClassIntrospector is missing [jboss.deployment.subunit.\"ViV

      iFYdServer.ear\".\"jboss-seam.jar\".beanmanager]",

          "jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.TimerServiceDispatcher.ORB is missing [jboss.naming.context.java.comp.ViViFYdSe

      rver.jboss-seam.TimerServiceDispatcher]",

          "jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.TimerServiceDispatcher.Validator is missing [jboss.naming.context.java.comp.ViV

      iFYdServer.jboss-seam.TimerServiceDispatcher]",

          "jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.TimerServiceDispatcher.InstanceName is missing [jboss.naming.context.java.comp.

      ViViFYdServer.jboss-seam.TimerServiceDispatcher]",

          "jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.EjbSynchronizations.Validator is missing [jboss.naming.context.java.comp.ViViFY

      dServer.jboss-seam.EjbSynchronizations]",

          "jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.TimerServiceDispatcher.ValidatorFactory is missing [jboss.naming.context.java.c

      omp.ViViFYdServer.jboss-seam.TimerServiceDispatcher]",

          "jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.EjbSynchronizations.InstanceName is missing [jboss.naming.context.java.comp.ViV

      iFYdServer.jboss-seam.EjbSynchronizations]",

          "jboss.deployment.subunit.\"ViViFYdServer.ear\".\"ViViFYdServer.war\".weld.weldClassIntrospector is missing [jboss.deployment.subunit.\"

      ViViFYdServer.ear\".\"ViViFYdServer.war\".beanmanager]",

          "jboss.persistenceunit.\"ViViFYdServer.ear/ViViFYdServer.jar#ViViFYdServerEntityManagerFactory\".__FIRST_PHASE__ is missing [jboss.namin

      g.context.java.ViViFYdServerDatasource]",

          "jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.EjbSynchronizations.ValidatorFactory is missing [jboss.naming.context.java.comp

      .ViViFYdServer.jboss-seam.EjbSynchronizations]",

          "jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.EjbSynchronizations.InAppClientContainer is missing [jboss.naming.context.java.

      comp.ViViFYdServer.jboss-seam.EjbSynchronizations]",

          "jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.TimerServiceDispatcher.InAppClientContainer is missing [jboss.naming.context.ja

      va.comp.ViViFYdServer.jboss-seam.TimerServiceDispatcher]",

          "jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.TimerServiceDispatcher.HandleDelegate is missing [jboss.naming.context.java.com

      p.ViViFYdServer.jboss-seam.TimerServiceDispatcher]"

      ]}

      20:49:47,246 ERROR [org.jboss.as.server] (XNIO-1 task-2) JBAS015870: Deploy of deployment "ViViFYdServer.ear" was rolled back with the follo

      wing failure message:

      {"JBAS014771: Services with missing/unavailable dependencies" => [

          "jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.EjbSynchronizations.ORB is missing [jboss.naming.context.java.comp.ViViFYdServe

      r.jboss-seam.EjbSynchronizations]",

          "jboss.deployment.unit.\"ViViFYdServer.ear\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"ViViFYdServer.ear\".beanmana

      ger]",

          "jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.EjbSynchronizations.HandleDelegate is missing [jboss.naming.context.java.comp.V

      iViFYdServer.jboss-seam.EjbSynchronizations]",

          "jboss.deployment.subunit.\"ViViFYdServer.ear\".\"jboss-seam.jar\".weld.weldClassIntrospector is missing [jboss.deployment.subunit.\"ViV

      iFYdServer.ear\".\"jboss-seam.jar\".beanmanager]",

          "jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.TimerServiceDispatcher.ORB is missing [jboss.naming.context.java.comp.ViViFYdSe

      rver.jboss-seam.TimerServiceDispatcher]",

          "jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.TimerServiceDispatcher.Validator is missing [jboss.naming.context.java.comp.ViV

      iFYdServer.jboss-seam.TimerServiceDispatcher]",

          "jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.TimerServiceDispatcher.InstanceName is missing [jboss.naming.context.java.comp.

      ViViFYdServer.jboss-seam.TimerServiceDispatcher]",

          "jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.EjbSynchronizations.Validator is missing [jboss.naming.context.java.comp.ViViFY

      dServer.jboss-seam.EjbSynchronizations]",

          "jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.TimerServiceDispatcher.ValidatorFactory is missing [jboss.naming.context.java.c

      omp.ViViFYdServer.jboss-seam.TimerServiceDispatcher]",

          "jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.EjbSynchronizations.InstanceName is missing [jboss.naming.context.java.comp.ViV

      iFYdServer.jboss-seam.EjbSynchronizations]",

          "jboss.deployment.subunit.\"ViViFYdServer.ear\".\"ViViFYdServer.war\".weld.weldClassIntrospector is missing [jboss.deployment.subunit.\"

      ViViFYdServer.ear\".\"ViViFYdServer.war\".beanmanager]",

          "jboss.persistenceunit.\"ViViFYdServer.ear/ViViFYdServer.jar#ViViFYdServerEntityManagerFactory\".__FIRST_PHASE__ is missing [jboss.namin

      g.context.java.ViViFYdServerDatasource]",

          "jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.EjbSynchronizations.ValidatorFactory is missing [jboss.naming.context.java.comp

      .ViViFYdServer.jboss-seam.EjbSynchronizations]",

          "jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.EjbSynchronizations.InAppClientContainer is missing [jboss.naming.context.java.

      comp.ViViFYdServer.jboss-seam.EjbSynchronizations]",

          "jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.TimerServiceDispatcher.InAppClientContainer is missing [jboss.naming.context.ja

      va.comp.ViViFYdServer.jboss-seam.TimerServiceDispatcher]",

          "jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.TimerServiceDispatcher.HandleDelegate is missing [jboss.naming.context.java.com

      p.ViViFYdServer.jboss-seam.TimerServiceDispatcher]"

      ]}

      20:49:47,279 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment null (runtime-name: ViViFYdServe

      r.jar) in 31ms

      20:49:47,280 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment null (runtime-name: jboss-seam.j

      ar) in 33ms

      20:49:48,203 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment null (runtime-name: ViViFYdServe

      r.war) in 955ms

      20:49:49,265 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015877: Stopped deployment ViViFYdServer.ear (runtime-name:

      ViViFYdServer.ear) in 2019ms

      20:49:49,268 INFO  [org.jboss.as.controller] (XNIO-1 task-2) JBAS014774: Service status report

      JBAS014775:    New missing/unsatisfied dependencies:

            service jboss.deployment.subunit."ViViFYdServer.ear"."ViViFYdServer.war".beanmanager (missing) dependents: [service jboss.deployment.s

      ubunit."ViViFYdServer.ear"."ViViFYdServer.war".weld.weldClassIntrospector]

            service jboss.deployment.subunit."ViViFYdServer.ear"."jboss-seam.jar".beanmanager (missing) dependents: [service jboss.deployment.subu

      nit."ViViFYdServer.ear"."jboss-seam.jar".weld.weldClassIntrospector]

            service jboss.deployment.unit."ViViFYdServer.ear".beanmanager (missing) dependents: [service jboss.deployment.unit."ViViFYdServer.ear"

      .weld.weldClassIntrospector]

            service jboss.naming.context.java.ViViFYdServerDatasource (missing) dependents: [service jboss.persistenceunit."ViViFYdServer.ear/ViVi

      FYdServer.jar#ViViFYdServerEntityManagerFactory".__FIRST_PHASE__]

            service jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.EjbSynchronizations (missing) dependents: [service jboss.naming.contex

      t.java.comp.ViViFYdServer.jboss-seam.EjbSynchronizations.Validator, service jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.EjbSynch

      ronizations.InAppClientContainer, service jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.EjbSynchronizations.InstanceName, service

      jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.EjbSynchronizations.HandleDelegate, JBAS014799: ... and 3 more ]

            service jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.TimerServiceDispatcher (missing) dependents: [service jboss.naming.con

      text.java.comp.ViViFYdServer.jboss-seam.TimerServiceDispatcher.ORB, service jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.TimerSer

      viceDispatcher.ValidatorFactory, service jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.TimerServiceDispatcher.HandleDelegate, serv

      ice jboss.naming.context.java.comp.ViViFYdServer.jboss-seam.TimerServiceDispatcher.InstanceName, JBAS014799: ... and 3 more ]

            service jboss.naming.context.java.module.ViViFYdServer."ViViFYdServer.war" (missing) dependents: [service jboss.deployment.subunit."Vi

      ViFYdServer.ear"."ViViFYdServer.war".INSTALL]

            service jboss.naming.context.java.module.ViViFYdServer.jboss-seam (missing) dependents: [service jboss.deployment.subunit."ViViFYdServ

      er.ear"."jboss-seam.jar".INSTALL]

        • 1. Re: Seam 2.3.1.Final on WildFly 8.0.0.Final-929
          Tomas Remes Expert

          Hi! Weld is scanning your archive (Processing weld deployment ViViFYdServer.war), which seems to cause the problem. You can try to set require-bean-descriptor to true in weld subsystem in your standalone configuration. Seam apps should be deployable on WildFly (I guess you can face some issue with persistence provider naming, but just guessing), however it won't be supported, so you might face any other issues. 

          • 2. Re: Seam 2.3.1.Final on WildFly 8.0.0.Final-929
            Roger Lee Apprentice

            Tomas,

             

            Can you elaborate please.

             

            The Weld Docs say;

             

            You can either set this up for your deployment only by adding the following content to the META-INF/jboss-all.xml file of your application:

             

            <jboss xmlns="urn:jboss:1.0">

                <weld xmlns="urn:jboss:weld:1.0" require-bean-descriptor="true"/>

            </jboss>

             

            I thought jboss-all.xml is not longer used in WildFly? 

            • 3. Re: Seam 2.3.1.Final on WildFly 8.0.0.Final-929
              Tomaz Cerar Master

              jboss-all.xml was recently added to WildFly to be fair around 7.2 time...

              • 4. Re: Seam 2.3.1.Final on WildFly 8.0.0.Final-929
                Roger Lee Apprentice

                Thanks for your reply.

                 

                However according to the WildFly docs:- Deployment Descriptors used In WildFly

                 

                Deployment Descriptors used In WildFly - WildFly 8 - Project Documentation Editor

                 

                There's no jboss-all.xml listed!

                 

                Where does it go and have you an example for above.

                 

                TIA

                • 5. Re: Seam 2.3.1.Final on WildFly 8.0.0.Final-929
                  Marek Novotny Master

                  Seam2 was not tested on Wildfly and it doesn't work AFAIK, i tried 8.0.0.Final with very simple example - jboss-seam/examples/registration at Seam_2_3 · seam2/jboss-seam · GitHub and it throws:

                   

                  Context Path:

                  /seam-registration

                   

                  Servlet Path:

                  /register.seam

                   

                  Path Info:

                  null

                   

                  Query String:

                  null

                   

                  Stack Trace

                  javax.servlet.ServletException: WELD-000340: A request must be associated with the context in order to load the known conversations

                  javax.faces.webapp.FacesServlet.service(FacesServlet.java:659)

                  io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85)

                  io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61)

                  io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)

                  org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)

                  io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25)

                  io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113)

                  io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52)

                  io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45)

                  io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61)

                  io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70)

                  io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76)

                  io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25)

                  org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)

                  io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25)

                  io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25)

                  io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240)

                  io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227)

                  io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73)

                  io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146)

                  io.undertow.server.Connectors.executeRootHandler(Connectors.java:168)

                  io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:687)

                  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

                  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

                  java.lang.Thread.run(Thread.java:744)

                  • 6. Re: Seam 2.3.1.Final on WildFly 8.0.0.Final-929
                    Tomas Remes Expert

                    jboss-all.xml file goes to your META-INF for ear archive and likely to WEB-INF for war archive. It should like this - to prevent Weld from scanning your archive:

                     

                    <jboss umlns="urn:jboss:1.0">

                        <weld xmlns="urn:jboss:weld:1.0" require-bean-descriptor="true"/>

                    </jboss>

                     

                    I guess the above exception from Marek is exactly this case. I consider this issue [WFLY-2936] "Only session and message-driven beans with bean-managed transaction demarcation are allowed to access UserT   as most interesting (problematic) with regarding Seam on WildFly.

                    • 7. Re: Seam 2.3.1.Final on WildFly 8.0.0.Final-929
                      Roger Lee Apprentice

                      So would you recommend dropping Seam and moving to Java CDI with WELD?

                       

                      As I understand it WELD is inlcuded in WildFly.

                       

                      I am loathed to move to Spring. I am a great EJB user and just want to refactor my existing systems now to use CDI.

                       

                      Thanks,

                      • 8. Re: Seam 2.3.1.Final on WildFly 8.0.0.Final-929
                        Marek Novotny Master

                        Roger Lee wrote:

                         

                        So would you recommend dropping Seam and moving to Java CDI with WELD?

                         

                        As I understand it WELD is inlcuded in WildFly.

                         

                        I am loathed to move to Spring. I am a great EJB user and just want to refactor my existing systems now to use CDI.

                         

                        Thanks,

                        It depends on your preferences. If you would like to change just server runtime, I would recommend to use EAP 6.2.0.GA as the latest download from JBoss Application Server Downloads - JBoss Community

                        • 9. Re: Seam 2.3.1.Final on WildFly 8.0.0.Final-929
                          Ben Software Engineer Newbie

                          Hi - FYI our application uses seam 2 heavily and we cannot move off easily.  It is complicated, uses lots of seam scopes and magic, as well as big on hibernate.  We are having success migrating to wildfly after recent patch to wildfly fixing userTransaction access issues.  You guys may be interested in this thread where we have got nice support from wildfly community.

                          https://issues.jboss.org/browse/WFLY-2936

                           

                          Only other issues we facing is seam's navigation handler for page.xml files needs to be extended to support developers not handling all navigation conditions, it should default to current page which was relied on, but doesnt anymore in jsf2 world.  Also some hibernate validator issues that are simple enough just need to move to standard JPA 2 versions.

                          -Ben

                          • 10. Re: Seam 2.3.1.Final on WildFly 8.0.0.Final-929
                            Roger Lee Apprentice

                            Thanks. I even more confused what to do

                             

                            The whole thing started when I couldn't get a JBoss AS 6.1 .0 Final Web Service to work which I needed for an Android App to connect to the server side using;-


                            @GET

                            @Produces("text/html")

                             

                            When I deployed the same EAR on JBoss AS 7,1.1 Final it worked but the XHTML wasn't working correctly and the CSS not applied, So then I decided to upgrade to latest version of SEAM and then WildFly (8.0) came along so moved to that version.

                             

                            I use JPA from database access BTW.

                             

                            As SEAM is now being moved to be part of Apache DeltaSpike.I thought it would be wise to move.

                             

                            I work on my own and these are all my projects, so I can make whatever decision I like. I also want to make myself marketable for the contract work I do. The only time I've used SEAM is when I've specified it in SME, never used in UK Corporates, it's all Spring, Spring, Spring!

                             

                            Is CDI the way to go? If so would it be worth investing in WELD?

                             

                            Basically all I want to do is have the XHTML using RichFaces communicating directly with my 3.1 EJBs (AKA SEAM).

                            • 11. Re: Seam 2.3.1.Final on WildFly 8.0.0.Final-929
                              Marek Novotny Master

                              Roger,

                               

                              it is definitely right direction to use Weld with Deltaspike.

                              Seam 2.x is not moving into Deltaspike that is the Seam 3 which was merged with Apache CODI into Deltaspike.

                               

                              In your case for your application you probably should use EAP 6.2 with Seam 2.x to reduce the impact on required changes. But if you would like to learn something new, Weld and Deltaspike is our bright future

                              • 12. Re: Seam 2.3.1.Final on WildFly 8.0.0.Final-929
                                Ben Software Engineer Newbie

                                Thanks Marek, and Roger I would also agree that is our internal long term plan.  We could not do a big bang rewrite though with 90% of our codebase using something seam 2 related.  Figuring out the correct pom versionsing to align with wildfly was a key task, once we got it deploying things are going smoothly with seam 2.3.  We could not figure a way out without upgrading first, so we plan to get to new world of JSF 2, Hibernate 4, Wildfly 8 (servlet 3.1, latest EJB, CDI/Weld, etc) and then iteratively rewrite each component to the new world.  Doing iterative approach on old stack is not possible.  If you can make a full migration work from old to new including major code refactoring it may be right for you.  FYI our situation we tried that first, but we had to keep stable branch of code progressing with business needs, refactoring all for CDI was large undertaking and everything didn't play seamless in new world, seam does some magic to make EJB and non ejb transactions work.  Specifically we found lazy initialization, use of outjection, and coding to Context specifically to set event, conversatoin, and sessoin scope variables to be problematic in the migration.  The code base became unmanagable to keep merging stable with the upgrade code branch, so we abandoned that approach.

                                1 of 1 people found this helpful
                                • 13. Re: Seam 2.3.1.Final on WildFly 8.0.0.Final-929
                                  Roger Lee Apprentice

                                  Marek & Ben,

                                   

                                  Thank you both for your input.

                                   

                                  The project I want to convert is 'fairly basic' so I'm prepared to give it a go with WELD/CDI and try some of the CDI extensions created by the Apache DeltaSpike.