Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "EclipseLinkConverters"

(New page: = Functional Specification: Dali Support for EclipseLink Converters = [http://bugs.eclipse.org/239163 bug 239163] - converters support == Document History == {|{{BMTableStyle}} |-{{BMTHS...)
 
(Convert)
Line 35: Line 35:
 
=== Convert ===
 
=== Convert ===
  
*  
+
* @Convert annotation supported on Basic, Id, Version, BasicMap and BasicCollection mappings
 +
*
  
[[Image: Converters.jpg]]
+
[[Image: BasicConversion.jpg]]
  
 +
[[Image: ObjectTypeConverter.jpg]]
  
 
== API ==
 
== API ==

Revision as of 11:13, 8 July 2008

Functional Specification: Dali Support for EclipseLink Converters

bug 239163 - converters support

Document History

Date Author Version Description & Notes
7-7-2008 Karen Butzke Draft

Project overview

This feature is about adding the attribute mapping converter annotations supported by the EclipseLink JPA extension.

Goals:

  • Add JPA Details view widgets for the Convert, Converter, ObjectTypeConverter, TypeConverter and StructConverter annotations
  • Add JPA Details view widgets for eclipselink-orm.xml convert, converter, object-type-converter, type-converter and struct-converter elements
  • Provide the validation for the converters

Concepts

Present any concepts relevant to the feature.

EclipseLink converters documentation

Requirements / Functionality

Convert

  • @Convert annotation supported on Basic, Id, Version, BasicMap and BasicCollection mappings

BasicConversion.jpg

ObjectTypeConverter.jpg

API

Issues

This section lists the open issues that are still pending that must be decided prior to fully implementing this project's requirements.

Issue # Owner Description / Notes Decision

Future Considerations

During the research for this project the following items were identified as out of scope but are captured here as potential future enhancements. If agreed upon during the review process these should be logged in the bug system.

Back to the top