Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 238447 - PrivateOwned on a manyToMany, confusing as to whether it is supported
Summary: PrivateOwned on a manyToMany, confusing as to whether it is supported
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Nobody - feel free to take it CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 238441
  Show dependency tree
 
Reported: 2008-06-25 14:01 EDT by Karen Butzke CLA
Modified: 2022-06-09 10:25 EDT (History)
3 users (show)

See Also:

Attachments
Code changes (874 bytes, patch)
2008-08-01 10:31 EDT, Guy Pelletier CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Karen Butzke CLA 2008-06-25 14:01:05 EDT 
In ManyToManyAccessor.isPrivateOwned() a warning is logged that @PrivateOwned is not a supported annotation.  The eclipselink-orm schema also does not support the private-owned element on many-to-many.  But in the XmlEntityMappingsProject.buildManyToManyDescriptor() it appears that private-owned is supported because it is mapped.  Which is correct?
Comment 1 Guy Pelletier CLA 2008-08-01 10:17:19 EDT 
It is not supported. The mapping from XmlEntityMappingsProject is redundant and should be removed.
Comment 2 Guy Pelletier CLA 2008-08-01 10:31:41 EDT 
Created attachment 108954 [details]
Code changes
Comment 3 Guy Pelletier CLA 2008-08-01 10:45:37 EDT 
Changes have been submitted.

Reviewed by: Tom Ware

No test added. Redundant code removed from the mapping project.
Comment 4 Eclipse Webmaster CLA 2022-06-09 10:25:32 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink