4 Replies Latest reply on Jun 28, 2013 2:53 PM by emmartins

    Unable to create JMS Destinations through web.xml




      As part of JavaEE7 demo, I am trying to deploy an application(war) which contains jms connection factory/queue definitions in web.xml. When I try to deploy the application (in wildfly alpha 2 Release) , server is unable to parse the web.xml and throwing the exceptions.


      Please find the attachment for the complete web.xml. Please find the below stack trace of the exception.



      00:00:33,045 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."jms.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."jms.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "jms.war"
      at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.0.0.Alpha2.jar:8.0.0.Alpha2]
      at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1942) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
      at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1875) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_11]
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_11]
      at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_11]
      Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS017302: Failed to parse XML descriptor "/C:/Software/Servers/jboss/wildfly-8.0.0.Alpha2/bin/content/jms.war/WEB-INF/web.xml" at [9,9]
      at org.wildfly.extension.undertow.deployment.WebParsingDeploymentProcessor.deploy(WebParsingDeploymentProcessor.java:121)
      at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.0.0.Alpha2.jar:8.0.0.Alpha2]
      ... 5 more




      Note: This same demo is working in GlassFish 4.x


      Is there any documentation that can talk what are the features of EE7 the wildfly is supporting.


      Thanks and Regards

      Murali Reddy

        • 1. Re: Unable to create JMS Destinations through web.xml

          Your web.xml is incorrect.


          It contains a




          According to the schema there is no interface-name element in a jms-destination.

          • 2. Re: Unable to create JMS Destinations through web.xml

            The original exception stacktrace should have contained that exact message indicating that interface-name isn't a valid element. However it doesn't and that's a bug which should be fixed after this is merged https://github.com/wildfly/wildfly/pull/4713

            • 3. Re: Unable to create JMS Destinations through web.xml



              Verified with javaee_7.xsd which had both the elements. Please find the below snippet from the xsd.


                    <xsd:element name="interface-name"
                          Fully-qualified name of the JMS destination interface.
                          Permitted values are javax.jms.Queue and javax.jms.Topic
                    <xsd:element name="class-name"
                          Fully-qualified name of the JMS destination implementation
                          class.  Ignored if a resource adapter is used unless the
                          resource adapter defines more than one destination implementation
                          class for the specified interface.



              Back to original issue. Even after modifying the <interface-name> to <class-name>, I am unable to create jms destination and connection factory through web.xml deployment(as war). Please find the altest web.xml after modifications. can you please suggest/guide me where I am going in wrong direction with this.


              Thanks and Regards

              Murali Reddy

              • 4. Re: Unable to create JMS Destinations through web.xml

                Our schemas are not the final releases, and in this case the element interface-name did not exist. I created another issue to update the schemas and related metadata objects.