Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1215196

Summary: [GSS](6.4.z) EJB2 EntityBean attribute <batch-cascade-delete> is not correct used as defined within the DTD
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: wfink
Component: EJBAssignee: wfink
Status: CLOSED CURRENTRELEASE QA Contact: Jan Martiska <jmartisk>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4.0CC: bmaxwell, cdewolf, istudens
Target Milestone: CR1Keywords: Reopened
Target Release: EAP 6.4.3   
Hardware: Unspecified   
OS: Unspecified   
URL: https://github.com/jbossas/jboss-eap/pull/2404
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-17 10:42:36 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:
Bug Depends On:    
Bug Blocks: 1231259    

Description wfink 2015-04-24 14:30:58 UTC 
Description of problem:

From jbosscmp-jdbc_4_1.dtd it seems like DTD is not allowing value true for  -----------------
<!ELEMENT batch-cascade-delete EMPTY>
-----------------

If an application is migrated the jbosscmp-jdbc.xml does not work as before.
Also if it is corrected like this 
  <batch-cascade-delete>true</batch-cascade-delete>
it work with EAP6 but the validation against the DTD will fail.
Tools like XDoclet or JBDS will validate the xml and fail in this case.

Actual results:
DTD validation failed

Expected results:
Element can be used like defined within the DTD
Comment 2 wfink 2015-04-24 15:54:04 UTC 
PR send: https://github.com/jbossas/jboss-eap/pull/2404
Comment 3 Jan Martiska 2015-07-30 12:00:31 UTC 
Verified in EAP 6.4.3.CR1.
Comment 4 Petr Penicka 2017-01-17 10:39:53 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.
Comment 5 Petr Penicka 2017-01-17 10:40:25 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.
Comment 6 Petr Penicka 2017-01-17 10:42:36 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.