Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "EclipseLink/Development/2.1/DynamicMOXy/296967"

Line 18: Line 18:
 
== Project overview ==
 
== Project overview ==
  
Overview of the project/feature.  Why is it desired, what are its goals.
+
The goal of this feature is to enable users of EclipseLink JAXB to perform typical JAXB operations without having real .class files available for their domain objectsUsers will pass in some form of metadata (EclipseLink deployment XML or eclipselink-oxm.xml) to our JAXBContextFactory, and this metadata will be used to construct DynamicEntity objects representing the domain classes.
 +
 
 +
The ultimate purpose of this feature is to support an end-to-end JPA<->JAXB solution.  EclipseLink JPA already has some support for Dynamic Persistence and this work will provide a path from Dynamic JPA to JAXB.
  
 
Goals:
 
Goals:
* goal 1
+
* Bootstrapping of JAXB context with metadata and no class files
* goal 2
+
* Support adding arbitrary properties/mappings at run time, after initialization has been performed
  
 
== Concepts ==
 
== Concepts ==

Revision as of 17:06, 4 December 2009

Design Specification: MOXy support for Dynamic Persistence

ER 296967

Document History

Date Author Version Description & Notes
091204 Rick Barkhouse

Project overview

The goal of this feature is to enable users of EclipseLink JAXB to perform typical JAXB operations without having real .class files available for their domain objects. Users will pass in some form of metadata (EclipseLink deployment XML or eclipselink-oxm.xml) to our JAXBContextFactory, and this metadata will be used to construct DynamicEntity objects representing the domain classes.

The ultimate purpose of this feature is to support an end-to-end JPA<->JAXB solution. EclipseLink JPA already has some support for Dynamic Persistence and this work will provide a path from Dynamic JPA to JAXB.

Goals:

  • Bootstrapping of JAXB context with metadata and no class files
  • Support adding arbitrary properties/mappings at run time, after initialization has been performed

Concepts

Present any concepts relevant to the feature.

Requirements

The following sections will expand the goals of this project into more concrete requirements.

Design Constraints

Design / Functionality

Testing

API

GUI

Config files

Documentation

Open 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

Decisions

This section lists decisions made. These are intended to document the resolution of open issues or constraints added to the project that are important.

Issue # 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