Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 324471 - Do not default to VariableOneToOneMapping for interfaces unless a managed class implementing it is found
Summary: Do not default to VariableOneToOneMapping for interfaces unless a managed cla...
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P2 normal (vote)
Target Milestone: ---   Edit
Assignee: Nobody - feel free to take it CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 324308
  Show dependency tree
 
Reported: 2010-09-03 14:10 EDT by Mitesh Meswani CLA
Modified: 2022-06-09 10:36 EDT (History)
4 users (show)

See Also:

Attachments
Proposed changes (8.98 KB, patch)
2010-12-02 14:48 EST, 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 Mitesh Meswani CLA 2010-09-03 14:10:27 EDT 
EclipseLink default interfaces to VariableOneToOneMapping. It should not be done unless a managed class implementing the interface is found 

Entering the bug as asked by Tom after a discussion about GlassFish issue https://glassfish.dev.java.net/issues/show_bug.cgi?id=12954
Comment 1 Tom Ware CLA 2010-09-20 09:04:40 EDT 
Setting target and priority.  See the following page for details of the
meanings of these fields:

http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines
Comment 2 Guy Pelletier CLA 2010-12-02 14:48:49 EST 
Created attachment 184389 [details]
Proposed changes
Comment 3 Guy Pelletier CLA 2010-12-02 15:27:24 EST 
Changes have been submitted.

Reviewed by: Chris Delahunt

Tests: Model change that would cause test failures without the fix.
Comment 4 Eclipse Webmaster CLA 2022-06-09 10:36:05 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink