Bug 914082

Summary: jboss-ejb3.xml parser should provide at least a warning when an invalid XML is used
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Josef Cacek <jcacek>
Component: EJBAssignee: David M. Lloyd <david.lloyd>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: jmartisk
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-02 11:01:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Josef Cacek 2013-02-22 09:32:55 UTC 
The jboss-ejb3.xml elements are not correctly validated. At least a warning should be provided when the invalid file is used.

Even the AS quickstarts are not unified in using this deployment descriptor.

ejb-security-interceptors/target/classes/META-INF/jboss-ejb3.xml:
<jboss xmlns="http://www.jboss.com/xml/ns/javaee"

jts/application-component-2/src/main/resources/META-INF/jboss-ejb3.xml:
<jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee"

It seems, the <ejb-jar> root element should be the correct one. There is no <jboss> element defined in the schema file:
https://github.com/jboss/metadata/blob/master/ejb/src/main/resources/schema/jboss-ejb3-2_0.xsd

Related links:
https://issues.jboss.org/browse/AS7-6452
https://github.com/jboss-jdf/jboss-as-quickstart/pull/425#discussion-diff-3025144
https://bugzilla.redhat.com/show_bug.cgi?id=911483
Comment 2 Dimitris Andreadis 2013-10-24 18:28:50 UTC 
Assigning jpai EJB issues to david.lloyd. Please re-assign to Cheng or others as needed.
Comment 3 Jan Martiska 2014-07-02 11:01:18 UTC 
https://issues.jboss.org/browse/WFLY-812 is rejected per David's last comment which sounds reasonable to me. I think that for backwards compatibility reasons this should be preserved, at least in EAP 6.x. I will close this one, but if anyone is opposed, it is still open to discussion.