Bug 103977

Summary:	composite keyword ignored for two way associations
Product:	[Retired] Red Hat Web Application Framework	Reporter:	Archit Shah <archit.shah>
Component:	persistence	Assignee:	Archit Shah <archit.shah>
Status:	CLOSED WONTFIX	QA Contact:	Jon Orris <jorris>
Severity:	high	Docs Contact:
Priority:	medium
Version:	6.0
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-11-14 20:24:58 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Archit Shah 2003-09-08 18:36:48 UTC

If you specify the composite keyword on one side of a two-way association, but
don't put the component keyword on the other side, the association is not
treated as a composition (e.g., no cascading delete). The metadata also doesn't
indicate the component/compositeness of the roles.

Comment 1 Archit Shah 2003-09-08 18:38:57 UTC

fixed at 35757 on branch and 35720 on tip.