Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-24179

Unable to parse jboss-ejb3.xml using using jboss-ejb3-4_0.xsd

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 8.0.0.GA-CR1, 8.0.0.GA
    • 8.0.0.Beta-CR1, 8.0.0.Beta
    • EE, EJB
    • None
    • False
    • None
    • False
    • Known Issue
    • Hide

      A simple workaround exists which consists in using the old xsd and just updating the properties names to jakarta, e.g.:

      <?xml version="1.0" encoding="UTF-8"?>
<jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee"
	xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xmlns:c="urn:clustering:1.0"
	xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd"
	version="3.1" impl-version="2.0">
	<enterprise-beans>
		<message-driven>
			<ejb-name>BMTQueueMDB</ejb-name>
			<ejb-class>org.jboss.xpaas.broker.mdb.BMTQueueMDB</ejb-class>
			<activation-config>
				<activation-config-property>
					<activation-config-property-name>destinationType</activation-config-property-name>
					<activation-config-property-value>jakarta.jms.Queue</activation-config-property-value>
				</activation-config-property>
...
      Show
      A simple workaround exists which consists in using the old xsd and just updating the properties names to jakarta, e.g.: <?xml version="1.0" encoding="UTF-8"?> <jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:c="urn:clustering:1.0" xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd" version="3.1" impl-version="2.0"> <enterprise-beans> <message-driven> <ejb-name>BMTQueueMDB</ejb-name> <ejb-class>org.jboss.xpaas.broker.mdb.BMTQueueMDB</ejb-class> <activation-config> <activation-config-property> <activation-config-property-name>destinationType</activation-config-property-name> <activation-config-property-value>jakarta.jms.Queue</activation-config-property-value> </activation-config-property> ...
    • Hide

      you can just "export EAP_JMS_ID_ME=foo", run EAP and drop the attached ROOT.war into jboss-eap-8.0/standalone/deployments/

      OR you can use the application used to assemble the war file:

      git clone git@github.com:tommaso-borgato/broker-amq7.git

cd broker-amq7

mvn -e -Popenshift -DskipTests -Dcom.redhat.xpaas.repo.redhatga -Dfabric8.skip=true -Djkube.skip=true --batch-mode -Djava.net.preferIPv4Stack=true clean package \
    -Dserver-feature-pack.location=org.jboss.eap:wildfly-ee-galleon-pack:8.0.0.Beta-redhat-00003 \
    -Dcloud-feature-pack.location=org.jboss.eap.cloud:eap-cloud-galleon-pack:1.0.0.Alpha10-redhat-00001 \
    -Ddatasources-feature-pack.location=org.jboss.eap:eap-datasources-galleon-pack:8.0.0.Beta-redhat-00003 

export EAP_JMS_ID_ME=foo

./target/server/bin/standalone.sh
      Show
      you can just " export EAP_JMS_ID_ME=foo ", run EAP and drop the attached ROOT.war into jboss-eap-8.0/standalone/deployments/ OR you can use the application used to assemble the war file: git clone git@github.com:tommaso-borgato/broker-amq7.git cd broker-amq7 mvn -e -Popenshift -DskipTests -Dcom.redhat.xpaas.repo.redhatga -Dfabric8.skip=true -Djkube.skip=true --batch-mode -Djava.net.preferIPv4Stack=true clean package \ -Dserver-feature-pack.location=org.jboss.eap:wildfly-ee-galleon-pack:8.0.0.Beta-redhat-00003 \ -Dcloud-feature-pack.location=org.jboss.eap.cloud:eap-cloud-galleon-pack:1.0.0.Alpha10-redhat-00001 \ -Ddatasources-feature-pack.location=org.jboss.eap:eap-datasources-galleon-pack:8.0.0.Beta-redhat-00003 export EAP_JMS_ID_ME=foo ./target/server/bin/standalone.sh

      A POD build with the new EAP8 images and feature-packs is unable to parse a jboss-ejb3.xml file which is using the new jakarta https://www.jboss.org/schema/jbossas/jboss-ejb3-4_0.xsd;

      The issue has been spotted on a POD but it can be easily reproduced locally without packing the server into an image (see " Steps to Reproduce");

        1. ROOT.war
          30 kB

              thofman Tomas Hofman
              tborgato@redhat.com Tommaso Borgato
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: