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 "EclipseLink/Development/DBWS/MetadataGenerationFromDDLMetaModel"
< EclipseLink | Development | DBWS
(New page: == Generating JAXB and JPA Metadata From DDL Parser Meta-model == The EclipseLink DBWS design time component (a.k.a. DBWSBuilder) generates OR and OX projects for use by the runtime compon...) |
(→Generating JAXB and JPA Metadata From DDL Parser Meta-model) |
||
| Line 1: | Line 1: | ||
== Generating JAXB and JPA Metadata From DDL Parser Meta-model == | == Generating JAXB and JPA Metadata From DDL Parser Meta-model == | ||
| − | The EclipseLink DBWS design time component (a.k.a. DBWSBuilder) generates OR and OX projects for use by the runtime component - these project instances are built using DDLParser generated meta-model objects. Since EclipseLink 2.5, DBWS generates and writes out JAXB and JPA metadata ([http://wiki.eclipse.org/EclipseLink/Development/DBWS/MetadataSupport DBWS Metadata Support]) based on the OR/OX projects. When considering JAXB/JPA metadata generation consolidation among various components, it would make sense to have the ability to generate metadata directly from the DDLParser generated metamodel, then bootstrap DBWS builder, JPA-RS, etc. from this metadata. This would allow the DDLParser and metadata generation piece proposed here to be standalone components, available for | + | The EclipseLink DBWS design time component (a.k.a. DBWSBuilder) generates OR and OX projects for use by the runtime component - these project instances are built using DDLParser generated meta-model objects. Since EclipseLink 2.5, DBWS generates and writes out JAXB and JPA metadata ([http://wiki.eclipse.org/EclipseLink/Development/DBWS/MetadataSupport DBWS Metadata Support]) based on the OR/OX projects. When considering JAXB/JPA metadata generation consolidation among various components, it would make sense to have the ability to generate metadata directly from the DDLParser generated metamodel, then bootstrap DBWS builder, JPA-RS, etc. from this metadata. This would allow the DDLParser and metadata generation piece proposed here to be standalone components, available to whomever requires this generated metadata. |
| + | |||
| + | === Issues === | ||
| + | * Default package name for generated Entities, Embeddables, etc. | ||
| + | * Query names - what would be the default name for a query generated from a stored procedure, custom SQL, etc.? | ||
| + | * For non-Oracle databases, JDBCHelper returns meta-model objects that extend the DDLParser meta-model - should this functionality be taken into consideration here as well? | ||
Revision as of 10:40, 12 July 2013
Generating JAXB and JPA Metadata From DDL Parser Meta-model
The EclipseLink DBWS design time component (a.k.a. DBWSBuilder) generates OR and OX projects for use by the runtime component - these project instances are built using DDLParser generated meta-model objects. Since EclipseLink 2.5, DBWS generates and writes out JAXB and JPA metadata (DBWS Metadata Support) based on the OR/OX projects. When considering JAXB/JPA metadata generation consolidation among various components, it would make sense to have the ability to generate metadata directly from the DDLParser generated metamodel, then bootstrap DBWS builder, JPA-RS, etc. from this metadata. This would allow the DDLParser and metadata generation piece proposed here to be standalone components, available to whomever requires this generated metadata.
Issues
- Default package name for generated Entities, Embeddables, etc.
- Query names - what would be the default name for a query generated from a stored procedure, custom SQL, etc.?
- For non-Oracle databases, JDBCHelper returns meta-model objects that extend the DDLParser meta-model - should this functionality be taken into consideration here as well?