3 Replies Latest reply on Aug 24, 2011 11:50 PM by Jason Porter

    Seam 3 migration

    Trevor Sweeney Newbie
      I am migrating from seam 2 to 3.  i have repackaged my code in a new project for seam 3. when i deploy i get the failure shown below

      I'm not sure if this is a seam/jsf/jboss/jee problem.... any help is appreciated



      Calling C:\jboss-as-web-7.0.0.Final\bin\standalone.conf.bat
      ===============================================================================

        JBoss Bootstrap Environment

        JBOSS_HOME: C:\jboss-as-web-7.0.0.Final

        JAVA: C:\glassfish3\jdk7\jre\bin\java

        JAVA_OPTS: -Dprogram.name=standalone.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dorg.jboss.resolver.warning=true -Djboss.modules.system.pkgs=org.jboss.byteman -server

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

      10:26:28,500 INFO  [org.jboss.modules] JBoss Modules version 1.0.1.GA
      10:26:28,781 INFO  [org.jboss.msc] JBoss MSC version 1.0.0.GA
      10:26:28,844 INFO  [org.jboss.as] JBoss AS 7.0.0.Final "Lightning" starting
      10:26:29,703 INFO  [org.jboss.as] creating http management service using network interface (management) port (9990) securePort (-1)
      10:26:29,734 INFO  [org.jboss.as.logging] Removing bootstrap log handlers
      10:26:29,766 INFO  [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)
      10:26:29,781 INFO  [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread) Activating Infinispan subsystem.
      10:26:29,906 INFO  [org.jboss.as.naming] (Controller Boot Thread) Activating Naming Subsystem
      10:26:29,938 INFO  [org.jboss.as.osgi] (Controller Boot Thread) Activating OSGi Subsystem
      10:26:29,953 INFO  [org.jboss.as.naming] (MSC service thread 1-2) Starting Naming Service
      10:26:29,953 INFO  [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem
      10:26:29,969 INFO  [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 3.2.0.Beta2
      10:26:30,094 INFO  [org.xnio] (MSC service thread 1-3) XNIO Version 3.0.0.Beta3
      10:26:30,109 INFO  [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.0.0.Beta3
      10:26:30,406 INFO  [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-2) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\glassfish3\jdk7\jre\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\Python26;C:\Python26\DLLs;C:\Python26\Lib;C:\Program Files\MKS\IntegrityClient\bin;C:\app\trsweeney\product\11.1.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;c:\Program Files\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\Common Files\Roxio Shared\9.0\DLLShared\;C:\Perforce;C:\Program Files\Java\jdk1.6.0_12\bin;C:\Program Files\apache-ant-1.7.1\bin;C:\Program Files\QuickTime\QTSystem\;C:\Program Files\Common Files\Roxio Shared\DLLShared\;C:\Program Files\Re
      search In Motion\BlackBerry JDE 4.6.1\bin;c:\cygwin\bin;c:\cygwin\usr\bin;C:\jython2.5.1\bin ;C:\Program Files\TortoiseSVN\bin;C:\Python26;C\Python26\scripts;C:\Python26\Lib\site-packages\django\bin\;C:\Python26\Lib\site-packages\numpy;C:\Python26\Lib\site-packages\numpy\lib;C:\Program Files\Enterprise Vault\EVClient\;c:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Documents and Settings\trsweeney\Desktop\apache-maven-3.0.3\bin;.
      10:26:30,422 INFO  [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem
      10:26:30,469 INFO  [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-1) Starting remote JMX connector
      10:26:30,500 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
      10:26:30,516 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.mbean.connector: org.jboss.msc.service.StartException in service jboss.mbean.connector: java.rmi.server.ExportException: Port already in use: 1090; nested exception is:
              java.net.BindException: Address already in use: JVM_Bind
              at org.jboss.as.jmx.JMXConnectorService.start(JMXConnectorService.java:106)
              at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
              at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.7.0]
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.7.0]
              at java.lang.Thread.run(Thread.java:722) [:1.7.0]
      Caused by: java.rmi.server.ExportException: Port already in use: 1090; nested exception is:
              java.net.BindException: Address already in use: JVM_Bind
              at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:328) [:1.7.0]
              at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:236) [:1.7.0]
              at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:411) [:1.7.0]
              at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:147) [:1.7.0]
              at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:207) [:1.7.0]
              at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:112) [:1.7.0]
              at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:88) [:1.7.0]
              at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:239) [:1.7.0]
              at org.jboss.as.jmx.JMXConnectorService.start(JMXConnectorService.java:97)
              ... 5 more
      Caused by: java.net.BindException: Address already in use: JVM_Bind
              at java.net.TwoStacksPlainSocketImpl.socketBind(Native Method) [:1.7.0]
              at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:374) [:1.7.0]
              at java.net.TwoStacksPlainSocketImpl.bind(TwoStacksPlainSocketImpl.java:95) [:1.7.0]
              at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:175) [:1.7.0]
              at java.net.ServerSocket.bind(ServerSocket.java:376) [:1.7.0]
              at org.jboss.as.network.ManagedServerSocketBinding.bind(ManagedServerSocketBinding.java:73)
              at org.jboss.as.network.SocketBinding.createServerSocket(SocketBinding.java:149)
              at org.jboss.as.jmx.JMXConnectorService$JMXServerSocketFactory.createServerSocket(JMXConnectorService.java:194)
              at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:667) [:1.7.0]
              at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:317) [:1.7.0]
              ... 13 more

      10:26:30,531 INFO  [org.jboss.as.remoting] (MSC service thread 1-3) Listening on /127.0.0.1:9999
      10:26:30,609 INFO  [org.jboss.as.connector] (MSC service thread 1-1) Starting JCA Subsystem (JBoss IronJacamar 1.0.0.CR2)
      10:26:30,672 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) Bound data source [java:jboss/datasources/ExampleDS]
      10:26:31,000 INFO  [org.jboss.as.deployment] (MSC service thread 1-4) Started FileSystemDeploymentService for directory C:\jboss-as-web-7.0.0.Final\standalone\deployments
      10:26:31,016 INFO  [org.jboss.as.controller] (Controller Boot Thread) Service status report
        Services which failed to start:
            service jboss.mbean.connector: org.jboss.msc.service.StartException in service jboss.mbean.connector: java.rmi.server.ExportException: Port already in use: 1090; nested exception is:
              java.net.BindException: Address already in use: JVM_Bind

      10:26:31,031 ERROR [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.0.Final "Lightning" started (with errors) in 2843ms - Started 91 of 147 services (1 services failed or missing dependencies, 55 services are passive or on-demand)
      10:26:31,031 WARN  [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Deployment of 'A_P_P_N_A_M_E' requested, but the deployment is not present
      10:26:31,047 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) Starting deployment of "A_P_P_N_A_M_E.war"
      10:26:54,141 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry asm-3.1.jar in "/C:/jboss-as-web-7.0.0.Final/bin/content/A_P_P_N_A_M_E.war/WEB-INF/lib/asm-xml-3.1.jar"  does not point to a valid jar for a Class-Path reference.
      10:26:54,141 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry asm-util-3.1.jar in "/C:/jboss-as-web-7.0.0.Final/bin/content/A_P_P_N_A_M_E.war/WEB-INF/lib/asm-xml-3.1.jar"  does not point to a valid jar for a Class-Path reference.
      10:26:54,141 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry asm-attrs-3.1.jar in "/C:/jboss-as-web-7.0.0.Final/bin/content/A_P_P_N_A_M_E.war/WEB-INF/lib/asm-xml-3.1.jar"  does not point to a valid jar for a Class-Path reference.
      10:26:54,141 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jaxb-api.jar in "/C:/jboss-as-web-7.0.0.Final/bin/content/A_P_P_N_A_M_E.war/WEB-INF/lib/jaxb-impl-2.0.3.jar"  does not point to a valid jar for a Class-Path reference.
      10:26:54,141 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry activation.jar in "/C:/jboss-as-web-7.0.0.Final/bin/content/A_P_P_N_A_M_E.war/WEB-INF/lib/jaxb-impl-2.0.3.jar"  does not point to a valid jar for a Class-Path reference.
      10:26:54,141 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jsr173_1.0_api.jar in "/C:/jboss-as-web-7.0.0.Final/bin/content/A_P_P_N_A_M_E.war/WEB-INF/lib/jaxb-impl-2.0.3.jar"  does not point to a valid jar for a Class-Path reference.
      10:26:54,141 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry jaxb1-impl.jar in "/C:/jboss-as-web-7.0.0.Final/bin/content/A_P_P_N_A_M_E.war/WEB-INF/lib/jaxb-impl-2.0.3.jar"  does not point to a valid jar for a Class-Path reference.
      10:26:54,157 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry xercesImpl.jar in "/C:/jboss-as-web-7.0.0.Final/bin/content/A_P_P_N_A_M_E.war/WEB-INF/lib/xalan-2.7.1-1.jbossorg.jar"  does not point to a valid jar for a Class-Path reference.
      10:26:54,157 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry xml-apis.jar in "/C:/jboss-as-web-7.0.0.Final/bin/content/A_P_P_N_A_M_E.war/WEB-INF/lib/xalan-2.7.1-1.jbossorg.jar"  does not point to a valid jar for a Class-Path reference.
      10:26:54,157 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) Class Path entry serializer.jar in "/C:/jboss-as-web-7.0.0.Final/bin/content/A_P_P_N_A_M_E.war/WEB-INF/lib/xalan-2.7.1-1.jbossorg.jar"  does not point to a valid jar for a Class-Path reference.
      10:26:54,313 WARN  [org.jboss.as.server.deployment.service-loader] (MSC service thread 1-2) Encountered invalid class name "org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer" for service type "org.xmlpull.v1.XmlPullParserFactory"
      10:26:54,594 INFO  [org.jboss.jpa] (MSC service thread 1-2) read persistence.xml for webstore
      10:26:54,594 INFO  [org.jboss.jpa] (MSC service thread 1-2) read persistence.xml for roWebstore
      10:26:54,907 INFO  [org.jboss.weld] (MSC service thread 1-3) Processing CDI deployment: A_P_P_N_A_M_E.war
      10:26:55,000 ERROR [stderr] (MSC service thread 1-3) log4j:WARN No appenders could be found for logger (org.jboss.seam.persistence.HibernatePersistenceProvider).
      10:26:55,000 ERROR [stderr] (MSC service thread 1-3) log4j:WARN Please initialize the log4j system properly.
      10:26:55,000 ERROR [stderr] (MSC service thread 1-3) log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
      10:26:55,032 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named EjbSynchronizations in deployment unit deployment "A_P_P_N_A_M_E.war" are as follows:

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

      10:26:55,032 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named Server in deployment unit deployment "A_P_P_N_A_M_E.war" are as follows:

              java:global/A_P_P_N_A_M_E/Server!net.company.server.appname.service.Server
              java:app/A_P_P_N_A_M_E/Server!net.company.server.appname.service.Server
              java:module/Server!net.company.server.appname.service.Server
              java:global/A_P_P_N_A_M_E/Server
              java:app/A_P_P_N_A_M_E/Server
              java:module/Server

      10:26:55,079 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named GenericDAO in deployment unit deployment "A_P_P_N_A_M_E.war" are as follows:

              java:global/A_P_P_N_A_M_E/GenericDAO!com.company.appname.util.DatabaseAccessObject
              java:app/A_P_P_N_A_M_E/GenericDAO!com.company.appname.util.DatabaseAccessObject
              java:module/GenericDAO!com.company.appname.util.DatabaseAccessObject
              java:global/A_P_P_N_A_M_E/GenericDAO
              java:app/A_P_P_N_A_M_E/GenericDAO
              java:module/GenericDAO

      10:26:55,141 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named TimerServiceDispatcher in deployment unit deployment "A_P_P_N_A_M_E.war" are as follows:

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

      10:26:55,829 WARN  [org.jboss.modules] (MSC service thread 1-4) Failed to define class javax.faces.component.html.HtmlDoctype in Module "deployment.A_P_P_N_A_M_E.war:main" from Service Module Loader: java.lang.ClassFormatError: Absent Code attribute in method that is not native or abstract in class file javax/faces/component/html/HtmlDoctype
              at java.lang.ClassLoader.defineClass1(Native Method) [:1.7.0]
              at java.lang.ClassLoader.defineClass(ClassLoader.java:791) [:1.7.0]
              at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) [:1.7.0]
              at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:397)
              at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:261)
              at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:76)
              at org.jboss.modules.Module.loadModuleClass(Module.java:588)
              at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:183)
              at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:358)
              at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:307)
              at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:101)
              at org.jboss.as.web.deployment.ServletContainerInitializerDeploymentProcessor.loadClassInfoSet(ServletContainerInitializerDeploymentProcessor.java:228)
              at org.jboss.as.web.deployment.ServletContainerInitializerDeploymentProcessor.deploy(ServletContainerInitializerDeploymentProcessor.java:158)
              at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
              at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
              at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.7.0]
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.7.0]
              at java.lang.Thread.run(Thread.java:722) [:1.7.0]

      10:26:55,907 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.unit."A_P_P_N_A_M_E.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."A_P_P_N_A_M_E.war".INSTALL: Failed to process phase INSTALL of deployment "A_P_P_N_A_M_E.war"
              at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121)
              at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
              at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.7.0]
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.7.0]
              at java.lang.Thread.run(Thread.java:722) [:1.7.0]
      Caused by: java.lang.ClassFormatError: Absent Code attribute in method that is not native or abstract in class file javax/faces/component/html/HtmlDoctype
              at java.lang.ClassLoader.defineClass1(Native Method) [:1.7.0]
              at java.lang.ClassLoader.defineClass(ClassLoader.java:791) [:1.7.0]
              at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) [:1.7.0]
              at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:397)
              at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:261)
              at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:76)
              at org.jboss.modules.Module.loadModuleClass(Module.java:588)
              at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:183)
              at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:358)
              at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:307)
              at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:101)
              at org.jboss.as.web.deployment.ServletContainerInitializerDeploymentProcessor.loadClassInfoSet(ServletContainerInitializerDeploymentProcessor.java:228)
              at org.jboss.as.web.deployment.ServletContainerInitializerDeploymentProcessor.deploy(ServletContainerInitializerDeploymentProcessor.java:158)
              at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)
              ... 5 more

      10:26:56,422 INFO  [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployment of "A_P_P_N_A_M_E.war" was rolled back with failure message {"Failed services" => {"jboss.deployment.unit.\"A_P_P_N_A_M_E.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"A_P_P_N_A_M_E.war\".INSTALL: Failed to process phase INSTALL of deployment \"A_P_P_N_A_M_E.war\""},"Services with missing/unavailable dependencies" => ["jboss.naming.context.java.comp.A_P_P_N_A_M_E.A_P_P_N_A_M_E.A_P_P_N_A_M_E.Validator missing [ jboss.naming.context.java.module.A_P_P_N_A_M_E.A_P_P_N_A_M_E ]","jboss.naming.context.java.comp.A_P_P_N_A_M_E.A_P_P_N_A_M_E.A_P_P_N_A_M_E.ValidatorFactory missing [ jboss.naming.context.java.module.webstore_raz
      vila.A_P_P_N_A_M_E ]"]}
      10:26:57,407 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) Stopped deployment A_P_P_N_A_M_E.war in 988ms
      10:26:57,407 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 1) {"Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"Failed services" => {"jboss.deployment.unit.\"A_P_P_N_A_M_E.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"A_P_P_N_A_M_E.war\".INSTALL: Failed to process phase INSTALL of deployment \"A_P_P_N_A_M_E.war\""},"Services with missing/unavailable dependencies" => ["jboss.naming.context.java.comp.A_P_P_N_A_M_E.A_P_P_N_A_M_E.A_P_P_N_A_M_E.Validator missing [ jboss.naming.context.java.module.A_P_P_N_A_M_E.A_P_P_N_A_M_E","jboss.naming.context.java.comp.A_P_P_N_A_M_E.A_P_P_N_A_M_E.A_P_P_N_A_M_E.ValidatorFactory missing [ jboss.naming.context.java.module.A_P_P_N_A_M_E.A_P_P_N_A_M_E ]"]}}}



















































































































        • 1. Re: Seam 3 migration
          Jason Porter Master

          Looks like there are a couple things:



          • AS7 isn't supported on JDK7, you may run into problems there

          • Looks like you have some other server running as well which is stealing your JNDI binding, that could cause a problem




          I'd need to see what's in the deployed archive, could you please list out the jars that are being deployed?

          • 2. Re: Seam 3 migration
            Trevor Sweeney Newbie
            Im not concerned with the JNDI binding error, its the

            ClassFormatError: Absent Code attribute in method that is not native or abstract in class file javax/faces/component/html/HtmlDoctype

            that has me banging my head against a wall.   Here is the list of jars deployed in the war.  

            activation-1.1.jar
            annotations-4.0.0.20110227-CR1.jar
            antisamy-1.4.4.jar
            antlr-2.7.6.jar
            aopalliance-1.0.jar
            asm-3.1.jar
            asm-tree-3.1.jar
            asm-util-3.1.jar
            asm-xml-3.1.jar
            axiom-api-1.2.8.jar
            axiom-impl-1.2.8.jar
            axis2-1.5.jar
            batik-css-1.7.jar
            batik-ext-1.7.jar
            batik-util-1.7.jar
            cal10n-api-0.7.2.jar
            cdi-api-1.0-SP4.jar
            cglib-2.2.jar
            commons-beanutils-1.8.0.jar
            commons-codec-1.4.jar
            commons-collections-3.2.jar
            commons-digester-2.1.jar
            commons-httpclient-3.1.jar
            commons-io-1.4.jar
            commons-lang-2.5.jar
            commons-logging-1.1.1.jar
            cssparser-0.9.5.jar
            dom4j-1.6.1.jar
            geronimo-activation_1.1_spec-1.0.1.jar
            geronimo-javamail_1.4_spec-1.2.jar
            geronimo-stax-api_1.0_spec-1.0.1.jar
            guava-r08.jar
            hibernate-annotations-3.5.6-Final.jar
            hibernate-commons-annotations-3.1.0.GA.jar
            hibernate-core-3.3.0.SP1.jar
            hibernate-jpa-2.0-api-1.0.0.Final.jar
            hibernate-validator-3.1.0.GA.jar
            javassist-3.14.0-GA.jar
            javax.inject-1.jar
            javax.mail-api-1.4.4.jar
            jaxb-api-2.1.jar
            jaxb-impl-2.0.3.jar
            jaxen-1.1.1.jar
            jaxrpc-api-1.1.jar
            jboss-annotations-api_1.1_spec-1.0.0.Final.jar
            jboss-connector-api_1.6_spec-1.0.0.Beta1.jar
            jboss-ejb-api_3.1_spec-1.0.0.Final.jar
            jboss-el-api_2.2_spec-1.0.0.Final.jar
            jboss-interceptor-core-2.0.0.CR1.jar
            jboss-interceptor-spi-2.0.0.CR1.jar
            jboss-interceptors-api_1.1_spec-1.0.0.Beta1.jar
            jboss-jacc-api_1.4_spec-1.0.0.Final.jar
            jboss-jad-api_1.2_spec-1.0.0.Final.jar
            jboss-jaspi-api_1.0_spec-1.0.0.Final.jar
            jboss-jaxb-api_2.2_spec-1.0.2.Final.jar
            jboss-jaxr-api_1.0_spec-1.0.0.Final.jar
            jboss-jaxrpc-api_1.1_spec-1.0.0.Final.jar
            jboss-jaxrs-api_1.1_spec-1.0.0.Beta1.jar
            jboss-jaxws-api_2.2_spec-2.0.0.Alpha1.jar
            jboss-jms-api_1.1_spec-1.0.0.Final.jar
            jboss-jsf-api_2.0_spec-1.0.0.Beta2.jar
            jboss-jsp-api_2.2_spec-1.0.0.Final.jar
            jboss-jstl-api_1.2_spec-1.0.0.Final.jar
            jboss-logging-generator-1.0.0.Beta5.jar
            jboss-saaj-api_1.3_spec-1.0.0.Final.jar
            jboss-servlet-api_3.0_spec-1.0.0.Final.jar
            jboss-transaction-api_1.1_spec-1.0.0.Final.jar
            joda-time-1.6.2.jar
            jsf-api-2.1.jar
            jsr173_api-1.0.jar
            jsr181-api-1.0-MR1.jar
            jsr250-api-1.0.jar
            jta-1.1.jar
            log4j-1.2.16.jar
            mail-1.4.2.jar
            mybatis-3.0.3.jar
            nekohtml-nekohtml-1.9.12.jar
            net.sourceforge.nekohtml-nekohtml-1.9.12.jar
            ocpsoft-pretty-time-1.0.6.jar
            openid4java-0.9.5.jar
            openid4java-consumer-0.9.5.jar
            openid4java-consumer-SampleConsumer-0.9.5.jar
            openid4java-nodeps-0.9.5.jar
            openid4java-server-0.9.5.jar
            openid4java-server-JdbcServerAssociationStore-0.9.5.jar
            openid4java-server-SampleServer-0.9.5.jar
            PayPal-AdaptivePayments-client-1.0.jar
            PayPal-GMInterfaceService-client-1.0.jar
            picketlink-idm-api-1.5.0.Alpha02.jar
            picketlink-idm-common-1.5.0.Alpha02.jar
            picketlink-idm-core-1.5.0.Alpha02.jar
            picketlink-idm-spi-1.5.0.Alpha02.jar
            prettyfaces-jsf2-3.0.1.jar
            richfaces-components-api-4.0.0.Final.jar
            richfaces-components-ui-4.0.0.Final.jar
            richfaces-core-api-4.0.0.Final.jar
            richfaces-core-impl-4.0.0.Final.jar
            richfaces-selenium-1.5.3.Final.jar
            sac-1.3.jar
            seam-catch-3.0.0.Final.jar
            seam-config-xml-3.0.0.Final.jar
            seam-faces-3.0.1.Final.jar
            seam-international-3.0.0.Final.jar
            seam-persistence-3.0.0.Final.jar
            seam-security-3.0.0.Final.jar
            seam-security-external-3.0.0.Final.jar
            seam-servlet-3.0.0.Final.jar
            seam-solder-3.0.0.Final.jar
            seam-solder-api-3.0.0.Final.jar
            seam-solder-tooling-3.0.0.Final.jar
            selenium-java-client-driver-1.0.2.jar
            slf4j-api-1.5.6.jar
            slf4j-ext-1.5.10.jar
            spring-beans-2.0.6.jar
            spring-context-2.0.6.jar
            spring-core-2.0.6.jar
            spring-dao-2.0.6.jar
            spring-jdbc-2.0.6.jar
            stax-api-1.0-2.jar
            stax-api-1.0.1.jar
            testng-5.12.1.jar
            validation-api-1.0.0.GA.jar
            weld-api-1.1.Final.jar
            weld-core-1.1.1.Final.jar
            weld-spi-1.1.Final.jar
            wsdl4j-1.6.2.jar
            wstx-asl-3.2.4.jar
            xalan-2.7.1-1.jbossorg.jar
            xercesImpl-2.8.1.jar
            xml-apis-1.3.04.jar
            xml-apis-ext-1.3.04.jar
            yarfraw-0.92.jar






            • 3. Re: Seam 3 migration
              Jason Porter Master

              I have no idea how you have so many jars in your archive. That needs to be cleaned up. Right now you have the JSF 2.1 api jar in there which is probably causing your problem. I suggest you start adding only what you need instead of everything in that list. If you have problems pruning jars I highly recommend taking a look at Tattletale and seeing what a TattleTale report tells you is being used and what can be pruned.