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.
Difference between revisions of "Dali/Juno/XmlMappingFileGeneration"
(New page: == XML Mapping File Generation == === Overview === [https://bugs.eclipse.org/bugs/show_bug.cgi?id=367367 Bug 367367] Dali currently provided JPA entity generation from tables, where the...) |
m (→XML Mapping File Generation) |
||
Line 24: | Line 24: | ||
===== Issues ===== | ===== Issues ===== | ||
+ | |||
+ | === Implementation notes === | ||
+ | |||
+ | * Delimiting will need to be addressed with a similar concept to the existing DatabaseAnnotationNameBuilder. Columns and tables will need to use the " escaping in XML when applicable |
Latest revision as of 11:49, 6 January 2012
Contents
XML Mapping File Generation
Overview
Dali currently provided JPA entity generation from tables, where the generated entities are Java classes that are annotated with mapping metadata. In addition to this functionality, it is desirable to offer this entity generation in the form of XML Mapping File (orm.xml) based metadata.
Requirements
- Support generation of Java classes and XML Mapping File from tables, where the mapping metadata is contained solely in the XML Mapping File
- Support generation of Java classes and EclipseLink XML Mapping File from tables, where the mapping metadata is contained solely in the EclipseLink XML Mapping File
- Dynamic Persistence: Support generation of EclipseLink XML Mapping File from tables, where the mapping metadata is contained solely in the EclipseLink XML Mapping File
Phases
Phase 1
- Support the Dynamic Persistence case of generating a self contain EclipseLink XML Mapping File from tables.
Issues
Phase 2
Issues
Implementation notes
- Delimiting will need to be addressed with a similar concept to the existing DatabaseAnnotationNameBuilder. Columns and tables will need to use the " escaping in XML when applicable