Bug 1004856 - jboss-ejb3.xml deployment descriptor is not parsed correct for the clustering element
Summary: jboss-ejb3.xml deployment descriptor is not parsed correct for the clustering...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: EJB
Version: 6.1.0,6.1.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: DR1
: EAP 6.4.0
Assignee: jboss-set
QA Contact: Jan Martiska
URL:
Whiteboard:
Depends On: 1124427
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-05 15:38 UTC by wfink
Modified: 2019-08-19 12:45 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-2011 0 Major Resolved jboss-ejb3.xml deployment descriptor is not parsed correct for the clustering element 2016-02-24 15:24:26 UTC

Description wfink 2013-09-05 15:38:23 UTC 
The clustering element of the jboss-ejb3.xml DD can include illegal repeating of the ejb-name element:
<assembly-descriptor>
  <c:clustering>
    <ejb-name>Bean1</ejb-name>
    <ejb-name>Bean2</ejb-name>
  <c:clustered>true</c:clustered>
  </c:clustering>
</assembly-descriptor>

In that case the behaviour of different components is inconsistent, see WFLY-2011.

The parser should log the problem and the application should not deployable.
Comment 4 Dimitris Andreadis 2013-10-24 18:28:16 UTC 
Assigning jpai EJB issues to david.lloyd. Please re-assign to Cheng or others as needed.
Comment 5 JBoss JIRA Server 2013-10-31 16:17:18 UTC 
Stuart Douglas <stuart.w.douglas> made a comment on jira WFLY-2011

I have pushed a fix for this into the metadata repository, this will be resolved by the next metadata release.
Comment 6 JBoss JIRA Server 2013-11-01 08:44:18 UTC 
Stuart Douglas <stuart.w.douglas> updated the status of jira WFLY-2011 to Resolved
Comment 8 Dominik Pospisil 2014-07-29 11:56:13 UTC 
The fix is already present in metadata 7.1.1, only thing left is to do EAP component upgrade.
Comment 10 Jan Martiska 2014-09-18 09:36:52 UTC 
Verified in EAP 6.4.0.DR1.1
Note You need to log in before you can comment on or make changes to this bug.