Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-7984

Unable to locate resource [./cxfws-cdi-xml.xml] for import! using camel-cdi

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Done
    • fuse-7.0
    • fuse-7.2
    • Fuse EAP
    • None
    • % %
    • Hide
      • The example is an Apache ANT Based application. This is the same reproducer as the quickstart, camel-cxf-jaxws-cdi-xml.
      • Navigate to the path, /home/vgohel/Downloads/reproducer/RH-example-camel-cxf-jaxws-cdi-xml-redhat.ear.
      • Set JBOSS_HOME path to point to the home folder of EAP. For example, export JBOSS_HOME=/home/vgohel/vigs-data/fuse-eap-servers/jboss-eap-7.1.1-full-build/jboss-eap-7.1/
      • Execute 'ant deploy' to deploy the application.

      Also, you can deploy the packaged EAR and WAR files which are build and available under,

      • RH-example-camel-cxf-jaxws-cdi-xml-redhat.ear/dist/RH-example-camel-cxf-jaxws-cdi-xml-redhat.ear
      • RH-example-camel-cxf-jaxws-cdi-xml-redhat.ear/example-camel-cxf-jaxws-cdi-xml.war/dist/example-camel-cxf-jaxws-cdi-xml.war
      Show
      The example is an Apache ANT Based application. This is the same reproducer as the quickstart, camel-cxf-jaxws-cdi-xml. Navigate to the path, /home/vgohel/Downloads/reproducer/RH-example-camel-cxf-jaxws-cdi-xml-redhat.ear. Set JBOSS_HOME path to point to the home folder of EAP. For example, export JBOSS_HOME=/home/vgohel/vigs-data/fuse-eap-servers/jboss-eap-7.1.1-full-build/jboss-eap-7.1/ Execute 'ant deploy' to deploy the application. Also, you can deploy the packaged EAR and WAR files which are build and available under, RH-example-camel-cxf-jaxws-cdi-xml-redhat.ear/dist/RH-example-camel-cxf-jaxws-cdi-xml-redhat.ear RH-example-camel-cxf-jaxws-cdi-xml-redhat.ear/example-camel-cxf-jaxws-cdi-xml.war/dist/example-camel-cxf-jaxws-cdi-xml.war
    • Fuse 7.2 Sprint 35

    Description

      Section 5.1.1, 'Importing XML DSL configuration' in the below doc,
      http://wildfly-extras.github.io/wildfly-camel/#_cdi

      states the below,

      It’s important to note that the location of the imported file must be present on the deployment classpath. Placing the file into locations such as WEB-INF will not work. However, WEB-INF/classes will work fine.
      

      If we package the supplied quickstart, 'camel-cxf-jaxws-cdi-xml' as an EAR, the deployment of the application fails with the below message:

      2018-04-16 08:35:49.807 |  | ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."RH-example-camel-cxf-jaxws-cdi-xml-redhat.ear".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."RH-example-camel-cxf-jaxws-cdi-xml-redhat.ear".WeldStartService: Failed to start service
      	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1978)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
      	at java.lang.Thread.run(Thread.java:748)
      Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type CamelContext with qualifiers @ContextName
        at injection point [BackedAnnotatedField] @Inject @ContextName org.wildfly.camel.examples.cxf.jaxws.Application.context
        at org.wildfly.camel.examples.cxf.jaxws.Application.context(Application.java:0)
      WELD-001475: The following beans match by type, but none have matching qualifiers:
        - Default Camel context bean with qualifiers [@javax.enterprise.inject.Any(), @javax.enterprise.inject.Default()]
      
      	at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:362)
      	at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:284)
      	at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:137)
      	at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:158)
      	at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:501)
      	at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:61)
      	at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:59)
      	at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62)
      	at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55)
      	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
      	at java.lang.Thread.run(Thread.java:748)
      	at org.jboss.threads.JBossThread.run(JBossThread.java:320)
      

      Attachments

        Activity

          People

            jnethert@redhat.com James Netherton
            rhn-support-vgohel Viral Gohel
            Jan Kasztura Jan Kasztura (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            10 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: