1 2 Previous Next 19 Replies Latest reply: Sep 1, 2011 4:09 AM by Richard Opalka Go to original post RSS
  • 15. Re: Can't handle @Resource for ENC name
    Richard Opalka Master

    and don't forget to delete beans.xml file - otherwise it will be detected as WELD archive (which is not true in your case).

  • 16. Re: Can't handle @Resource for ENC name
    Richard Opalka Master

    I'd say you should remove everything from your WEB-INF/lib folder

  • 17. Re: Can't handle @Resource for ENC name
    Sam W Expert

    but I need spring.

    when I removed all *cxf* from lib directory, redeployed, it thrown the following error:

     

     

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

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

     

     

      JBoss Bootstrap Environment

     

     

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

     

     

      JAVA: C:\Java\jdk1.6.0_26\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

     

     

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

     

     

    00:32:23,463 �Ϣ    [org.jboss.modules] JBoss Modules version 1.0.1.GA

    00:32:26,940 INFO  [org.jboss.msc] JBoss MSC version 1.0.0.GA

    00:32:27,743 INFO  [org.jboss.as] JBoss AS 7.0.1.Final "Zap" starting

    00:32:43,215 WARN  [org.jboss.as] No security realm defined for native management service, all access will be unrestricted.

    00:32:43,228 INFO  [org.jboss.as] creating http management service using network interface (management) port (9990)

    00:32:43,232 WARN  [org.jboss.as] No security realm defined for http management service, all access will be unrestricted.

    00:32:43,315 INFO  [org.jboss.as.logging] Removing bootstrap log handlers

    00:32:43,455 INFO  [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)

    00:32:43,537 INFO  [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread) Activating Infinispan subsystem.

    00:32:43,970 INFO  [org.jboss.as.naming] (Controller Boot Thread) Activating Naming Subsystem

    00:32:44,104 INFO  [org.jboss.as.naming] (MSC service thread 1-4) Starting Naming Service

    00:32:44,111 INFO  [org.jboss.as.osgi] (Controller Boot Thread) Activating OSGi Subsystem

    00:32:44,214 INFO  [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem

    00:32:44,221 INFO  [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 3.2.0.Beta2

    00:32:44,245 INFO  [org.xnio] (MSC service thread 1-1) XNIO Version 3.0.0.Beta3

    00:32:44,289 INFO  [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.0.0.Beta3

    00:32:45,749 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:\Java\jdk1.6.0_26\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\cygwin\usr\local\bin;C:\cygwin\bin;C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\glassfish3\jdk\bin;C:\Program Files (x86)\QuickTime\QTSystem;C:\Program Files (x86)\Windows Live\Shared;C:\apache-ant-1.8.2\bin;C:\apache-maven-3.0.3\bin;C:\Program Files\TortoiseSVN\bin;C:\Java\jdk1.6.0_26\bin;.

    00:32:45,921 INFO  [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem

    00:32:45,937 INFO  [org.jboss.as.remoting] (MSC service thread 1-1) Listening on /192.168.1.100:9999

    00:32:45,938 INFO  [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-1) Starting remote JMX connector

    00:32:47,638 INFO  [org.jboss.as.connector] (MSC service thread 1-2) Starting JCA Subsystem (JBoss IronJacamar 1.0.3.Final)

    00:32:47,853 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4) Starting Coyote HTTP/1.1 on http--192.168.1.100-8080

    00:32:48,284 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) Bound data source [java:jboss/datasources/ExampleDS]

    00:32:49,638 INFO  [org.jboss.as.deployment] (MSC service thread 1-3) Started FileSystemDeploymentService for directory C:\jboss-as-web-7.0.1.Final\standalone\deployments

    00:32:49,686 INFO  [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.1.Final "Zap" started in 26731ms - Started 93 of 148 services (55 services are passive or on-demand)

    00:33:24,781 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) Starting deployment of "order-new.war"

    00:33:24,965 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "order-new.war"

    00:33:27,160 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jaxb-api.jar in "/C:/jboss-as-web-7.0.1.Final/bin/content/order-new.war/WEB-INF/lib/jaxb-impl-2.1.13.jar"  does not point to a valid jar for a Class-Path reference.

    00:33:27,160 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry activation.jar in "/C:/jboss-as-web-7.0.1.Final/bin/content/order-new.war/WEB-INF/lib/jaxb-impl-2.1.13.jar"  does not point to a valid jar for a Class-Path reference.

    00:33:27,161 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jsr173_1.0_api.jar in "/C:/jboss-as-web-7.0.1.Final/bin/content/order-new.war/WEB-INF/lib/jaxb-impl-2.1.13.jar"  does not point to a valid jar for a Class-Path reference.

    00:33:27,161 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-4) Class Path entry jaxb1-impl.jar in "/C:/jboss-as-web-7.0.1.Final/bin/content/order-new.war/WEB-INF/lib/jaxb-impl-2.1.13.jar"  does not point to a valid jar for a Class-Path reference.

    00:33:38,028 INFO  [org.jboss.as.jpa] (MSC service thread 1-1) added javax.persistence.api dependency to order-new.war

    00:33:38,525 INFO  [org.jboss.weld] (MSC service thread 1-1) Processing CDI deployment: order-new.war

    00:33:40,093 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.unit."order-new.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."order-new.war".INSTALL: Failed to process phase INSTALL of deployment "order-new.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$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26]

            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26]

            at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]

    Caused by: java.lang.NullPointerException

            at org.jboss.as.weld.deployment.processors.WeldComponentIntegrationProcessor$1.configure(WeldComponentIntegrationProcessor.java:87)

            at org.jboss.as.ee.component.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:65)

            at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)

            ... 5 more

     

     

    00:33:40,299 INFO  [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployment of "order-new.war" was rolled back with failure message {"Failed services" => {"jboss.deployment.unit.\"order-new.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"order-new.war\".INSTALL: Failed to process phase INSTALL of deployment \"order-new.war\""},"Services with missing/unavailable dependencies" => ["jboss.naming.context.java.comp.order-new.order-new.order-new.ValidatorFactory missing [ jboss.naming.context.java.module.order-new.order-new ]","jboss.naming.context.java.comp.order-new.order-new.order-new.Validator missing [ jboss.naming.context.java.module.order-new.order-new ]"]}

    00:33:40,543 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) Stopped deployment order-new.war in 244ms

    00:33:40,547 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.\"order-new.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"order-new.war\".INSTALL: Failed to process phase INSTALL of deployment \"order-new.war\""},"Services with missing/unavailable dependencies" => ["jboss.naming.context.java.comp.order-new.order-new.order-new.ValidatorFactory missing [ jboss.naming.context.java.module.order-new.order-new ]","jboss.naming.context.java.comp.order-new.order-new.order-new.Validator missing [ jboss.naming.context.java.module.order-new.order-new ]"]}}}

    00:33:41,386 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry jaxb-api.jar in "/C:/jboss-as-web-7.0.1.Final/bin/content/order-new.war/WEB-INF/lib/jaxb-impl-2.1.13.jar"  does not point to a valid jar for a Class-Path reference.

    00:33:41,386 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry activation.jar in "/C:/jboss-as-web-7.0.1.Final/bin/content/order-new.war/WEB-INF/lib/jaxb-impl-2.1.13.jar"  does not point to a valid jar for a Class-Path reference.

    00:33:41,386 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry jsr173_1.0_api.jar in "/C:/jboss-as-web-7.0.1.Final/bin/content/order-new.war/WEB-INF/lib/jaxb-impl-2.1.13.jar"  does not point to a valid jar for a Class-Path reference.

    00:33:41,386 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry jaxb1-impl.jar in "/C:/jboss-as-web-7.0.1.Final/bin/content/order-new.war/WEB-INF/lib/jaxb-impl-2.1.13.jar"  does not point to a valid jar for a Class-Path reference.

    00:33:44,407 INFO  [org.jboss.as.jpa] (MSC service thread 1-3) added javax.persistence.api dependency to order-new.war

    00:33:45,297 INFO  [org.jboss.weld] (MSC service thread 1-2) Processing CDI deployment: order-new.war

    00:33:46,191 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."order-new.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."order-new.war".INSTALL: Failed to process phase INSTALL of deployment "order-new.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$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26]

            at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26]

            at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]

    Caused by: java.lang.NullPointerException

            at org.jboss.as.weld.deployment.processors.WeldComponentIntegrationProcessor$1.configure(WeldComponentIntegrationProcessor.java:87)

            at org.jboss.as.ee.component.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:65)

            at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115)

            ... 5 more

     

     

    00:33:46,612 INFO  [org.jboss.as.server.controller] (DeploymentScanner-threads - 1) Deployment of "order-new.war" was rolled back with failure message {"Failed services" => {"jboss.deployment.unit.\"order-new.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"order-new.war\".INSTALL: Failed to process phase INSTALL of deployment \"order-new.war\""},"Services with missing/unavailable dependencies" => ["jboss.naming.context.java.comp.order-new.order-new.order-new.Validator missing [ jboss.naming.context.java.module.order-new.order-new ]","jboss.naming.context.java.comp.order-new.order-new.order-new.ValidatorFactory missing [ jboss.naming.context.java.module.order-new.order-new ]"]}

    00:33:46,897 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) Stopped deployment order-new.war in 286ms

    00:33:46,913 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 2) {"Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"Failed services" => {"jboss.deployment.unit.\"order-new.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"order-new.war\".INSTALL: Failed to process phase INSTALL of deployment \"order-new.war\""},"Services with missing/unavailable dependencies" => ["jboss.naming.context.java.comp.order-new.order-new.order-new.Validator missing [ jboss.naming.context.java.module.order-new.order-new ]","jboss.naming.context.java.comp.order-new.order-new.order-new.ValidatorFactory missing [ jboss.naming.context.java.module.order-new.order-new ]"]}}}

     

     

     

  • 18. Re: Can't handle @Resource for ENC name
    Sam W Expert

    I have removed everything according what you suggested, but am still having errors.

    I have attached my war file here for reference:

    http://www.coderanch.com/t/551216/JBoss/Failed-start-service-jboss-deployment#2500783

     

     

    Thanks

    Sam

  • 19. Re: Can't handle @Resource for ENC name
    Richard Opalka Master

    You didn't change the servlet class name, as I suggested you here:

     

    http://community.jboss.org/message/624030#624030

     

    If I apply this change to your archive (U provided at code ranch) the endpoint deploys for me.

1 2 Previous Next