Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 277367 - Release Note - SDO Behaviour Change wrt Instance Class Name
Summary: Release Note - SDO Behaviour Change wrt Instance Class Name
Status: CLOSED 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: http://wiki.eclipse.org/EclipseLink/R...
Whiteboard:
Keywords:
Depends on: 268209
Blocks:
  Show dependency tree
 
Reported: 2009-05-21 14:25 EDT by Blaise Doughan CLA
Modified: 2022-06-09 10:31 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 Blaise Doughan CLA 2009-05-21 14:25:53 EDT 
There is a change in behaviour in EclipseLink SDO between versions 1.1 and 2.0.

EclipseLink 1.1 SDO Behaviour:
When an SDO Type was defined if a class could not be found corresponding to the instance class name (name of the corresponding static SDO class) then one was automatically created using ASM.

EclipseLink 2.0 SDO Behaviour
When an SDO Type is defined if a class can not be found corresponding to the instance class name (name of the corresponding static SDO class) then one is not created.

Rationale:
1.  This was done as a performance improvement.
2.  This was done to support static SDO DataObjects without generating an impl class.  This particular work was required to implement the JAXB/SDO bridge.
Comment 1 Doug Clarke CLA 2009-11-30 08:50:56 EST 
What was the behaviour in 1.2.0?
Comment 2 Doug Clarke CLA 2009-11-30 08:56:27 EST 
Added note @ http://wiki.eclipse.org/EclipseLink/Release/2.0.0#Resolved_Issues

Please also link to bug(s) that were involved in changing the behaviour.
Comment 3 Blaise Doughan CLA 2009-11-30 09:14:15 EST 
(In reply to comment #1)
> What was the behaviour in 1.2.0?

The behavior in 1.2 is the same as 2.0.
Comment 4 Blaise Doughan CLA 2009-11-30 09:21:00 EST 
(In reply to comment #2)
> Added note @ http://wiki.eclipse.org/EclipseLink/Release/2.0.0#Resolved_Issues
> Please also link to bug(s) that were involved in changing the behaviour.

Added a link on the release notes page to the code bug 268209.
Comment 5 Eclipse Webmaster CLA 2022-06-09 10:31:00 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink