This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 211303 - Add serialized converter support to the EclipseLink-ORM.XML Schema
Summary: Add serialized converter support to the EclipseLink-ORM.XML Schema
Status: RESOLVED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Nobody - feel free to take it CLA
QA Contact:
URL:
Whiteboard: Fixed in 1.0M6
Keywords:
Depends on:
Blocks: 200040
  Show dependency tree
 
Reported: 2007-11-28 14:27 EST by Guy Pelletier CLA
Modified: 2022-06-09 10:30 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Guy Pelletier CLA 2007-11-28 14:27:02 EST
 
Comment 1 Doug Clarke CLA 2008-01-30 19:36:33 EST
Is this not covered by JPA inherently through the basic mapping of an attribute that holds a serialized type to a LOB field?

 Do we need anything special to represent the possible runtime support?
Comment 2 Tom Ware CLA 2008-03-10 15:44:48 EDT
As mentioned above, this case is already addressed in JPA.  It is address in 2 ways.

Objects that are not annotated as @Entity will automatically be treated as serialized in the absence metadata that says to do other things.  - This holds true for basic and for direct collections.

If a user wants to override a mapping that contains an entity to serialize, they can override the default (OneToOne, or OneToMany) as Basic and then add a SerializedConverter through @Convert().
Comment 3 Eclipse Webmaster CLA 2022-06-09 10:30:06 EDT
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink