Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1057835 - JBoss EAP6 is not able to parse ejb-jar.xml of version 2.0
Summary: JBoss EAP6 is not able to parse ejb-jar.xml of version 2.0
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: EJB
Version: 6.2.0
Hardware: All
OS: All
Target Milestone: DR13
: EAP 6.4.0
Assignee: Ivo Studensky
QA Contact: Jan Martiska
Whiteboard: block_CR
Depends On: 1171105
TreeView+ depends on / blocked
Reported: 2014-01-25 05:23 UTC by Jay SenSharma
Modified: 2019-02-15 13:37 UTC (History)
13 users (show)

Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed:
Type: Bug

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 960203 None None None Never
JBoss Issue Tracker JBMETA-354 Major Resolved Support EJB 2.0 dtd descriptors 2018-07-24 13:12:58 UTC
JBoss Issue Tracker WFLY-4156 Major Closed WildFly is not able to parse ejb-jar.xml of version 2.0 2018-07-24 13:12:58 UTC
Red Hat Bugzilla 1188965 None None None Never
Red Hat Bugzilla 1188966 None None None Never
Red Hat Bugzilla 1188967 None None None Never

Internal Links: 1188965 1188966 1188967

Description Jay SenSharma 2014-01-25 05:23:22 UTC
Description of problem:
- While using "ejb-jar.xml" of version 2.0 as following the EAP6.2 throws the parsing error:

<?xml version="1.0"?>
<!DOCTYPE ejb-jar
   PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN"

- The following error is encountered at the time of deployment:

17:40:04,405 ERROR [] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."TestEJB.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."TestEJB.jar".PARSE: JBAS018733: Failed to process phase PARSE of deployment "TestEJB.jar"
    at [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService( [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
    at org.jboss.msc.service.ServiceControllerImpl$ [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask( [rt.jar:1.6.0_45]
    at java.util.concurrent.ThreadPoolExecutor$ [rt.jar:1.6.0_45]
    at [rt.jar:1.6.0_45]
Caused by: JBAS014185: Exception while parsing ejb-jar.xml: /content/TestEJB.jar/META-INF/ejb-jar.xml
    at [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]
    ... 5 more
Caused by: ParseError at [row,col]:[14,10]
Message: Unexpected element 'message-driven-destination' encountered
    at org.jboss.metadata.parser.util.MetaDataElementParser.unexpectedElement(
    at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElement(
    at org.jboss.metadata.ejb.parser.spec.AbstractNamedMetaDataWithDescriptionGroupParser.processElement(
    at org.jboss.metadata.ejb.parser.spec.AbstractEnterpriseBeanMetaDataParser.processElement(
    at org.jboss.metadata.ejb.parser.spec.AbstractMessageDrivenBeanParser.processElement(
    at org.jboss.metadata.ejb.parser.spec.MessageDrivenBean31Parser.processElement(
    at org.jboss.metadata.ejb.parser.spec.MessageDrivenBean31Parser.processElement(
    at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElements(
    at org.jboss.metadata.ejb.parser.spec.MessageDrivenBean31Parser.parse(
    at org.jboss.metadata.ejb.parser.spec.EnterpriseBeansMetaDataParser.processElement(
    at org.jboss.metadata.ejb.parser.spec.EnterpriseBeansMetaDataParser.processElement(
    at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElements(
    at org.jboss.metadata.ejb.parser.spec.EnterpriseBeansMetaDataParser.parse(
    at org.jboss.metadata.ejb.parser.spec.EnterpriseBeansMetaDataParser.parse(
    at org.jboss.metadata.ejb.parser.spec.AbstractEjbJarMetaDataParser.processElement(
    at org.jboss.metadata.ejb.parser.spec.AbstractEjbJarMetaDataParser.processElement(
    at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElements(
    at org.jboss.metadata.ejb.parser.spec.EjbJarMetaDataParser.parseDocument(
    at org.jboss.metadata.ejb.parser.spec.EjbJarMetaDataParser.parse(
    ... 7 more

17:40:04,422 ERROR [] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "TestEJB.jar" was rolled back with the following failure message: 
{"JBAS014671: Failed services" => {"jboss.deployment.unit.\"TestEJB.jar\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"TestEJB.jar\".PARSE: JBAS018733: Failed to process phase PARSE of deployment \"TestEJB.jar\"
    Caused by: JBAS014185: Exception while parsing ejb-jar.xml: /content/TestEJB.jar/META-INF/ejb-jar.xml
    Caused by: ParseError at [row,col]:[14,10]
Message: Unexpected element 'message-driven-destination' encountered"}}

**NOTE:** According to the link [1] EJB2.0 is supported with EAP6 so ideally JBoss should be able to parse the "ejb-jar.xml" of version 2.0 DTDs.

**NOTE:** there is a feature request seen for JBossAS7 for requesting support for ejb-jar.xml 2.0 DTDs  [2]


Version-Release number of selected component (if applicable):
How reproducible:

Steps to Reproduce:
1. Deploy an MDB based EJB jar in EAP6 and use the ejb-jar.xml as mentioned in the issue description.

Actual results:
- EAP6 should be able to parse the ejb-jar.xml properly and should deploy the MDB properly.

Expected results:
- Deployment should be successful.

Additional info:

Comment 1 wfink 2014-06-27 18:19:19 UTC
This is against the JavaEE specification
JSR220(ejb3.0) and JSR318(ejb3.1)
 chapter 19.Deployment Desriptor
         19.4. Container Providers Responsibility

All EJB 3.0 implementations must support EJB 2.1, EJB 2.0, and EJB 1.1 as well as EJB 3.0 deploy-
ment descriptors. The definitions of the EJB 2.1, EJB 2.0, and EJB 1.1 deployment descriptors can be
found in the Enterprise JavaBeans 2.1 specification [3].

Comment 5 Jason T. Greene 2014-11-20 16:16:51 UTC
We believe we can do this fix in a CP and that it should not block the release.

Comment 11 Ivo Studensky 2014-12-04 14:25:27 UTC

Comment 12 JBoss JIRA Server 2014-12-05 09:42:38 UTC
Ivo Studensky <> updated the status of jira JBMETA-354 to Resolved

Comment 14 Jan Martiska 2014-12-12 12:02:25 UTC
Verified in EAP 6.4.0.DR13.

Note You need to log in before you can comment on or make changes to this bug.