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"
< EclipseLink | DesignDocs
(→Requirements) |
(→Concepts) |
||
| Line 21: | Line 21: | ||
== Concepts == | == Concepts == | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Requirements == | == Requirements == | ||
Revision as of 12:52, 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 different classes contained in a single persistence unit to be mapped to different databases.
Concepts
Requirements
The two main use cases:
- Unify multiple persistence units (with independent from each other object models).
- Split single persistent unit.
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.