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/DesignDocs/328404"
(→Project overview) |
|||
| Line 18: | Line 18: | ||
== Project overview == | == Project overview == | ||
| − | + | The goal is to allow for an object model contained in a single persistence unit to be mapped to more than one database. | |
| − | + | That could be achieved by exposing SessionBroker through JPA. | |
| − | + | ||
| − | + | ||
| − | + | ||
== Concepts == | == Concepts == | ||
Revision as of 10:09, 22 October 2010
Contents
Design Specification: Support SessionBroker in JPA
Document History
| 2010/10/22 | Andrei Ilitchev | Initial Version |
Project overview
The goal is to allow for an object model contained in a single persistence unit to be mapped to more than one database. That could be achieved by exposing SessionBroker through JPA.
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.