Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 359823 - In ORMetadata hierarchy some .equals methods not fully implemented
Summary: In ORMetadata hierarchy some .equals methods not fully implemented
Status: NEW
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: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-04 07:44 EDT by Karen Butzke CLA
Modified: 2022-06-09 10:08 EDT (History)
1 user (show)

See Also:

Attachments
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 2011-10-04 07:44:08 EDT 
In the ORMetadata hierarchy some of the .equals methods are missing fields defined on the class. For example, NamedQueryMetadata is missing the newer m_lockMode. This could lead to a false positive when comparing 2 queries for equality. Thus no exception would be thrown saying that 2 queries have the same name and it could be confusing to the user when it is not clear which query actually gets used in the project.

I have not searched the entire hierarchy, but noticed this particular field as missing.
Comment 1 Tom Ware CLA 2011-10-31 13:27:21 EDT 
Setting target and priority.  See the following page for the meanings of these fields:

http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines

Community: Please vote for this bug if it is important to you.  Votes are one of the main criteria we use to determine which bugs to fix next.
Comment 2 Eclipse Webmaster CLA 2022-06-09 10:08:04 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink