Design Specification: Support SessionBroker in JPA
|2010/10/22||Andrei Ilitchev||Initial Version|
The goal is to allow for different classes contained in a single persistence context to be mapped to different databases.
em.persist(new A(..)); em.persist(new B(..)); // insert A into db1; insert B into db2: // the two different data bases possibly from different vendors em.flush();
- Currently each persistence unit has a single ServerSession.
- Eclipselink core defines SessionBroker class that aggregates several ServerSessions.
- SessionBroker maps each class to a single ServerSession.
- This feature is to define persistence unit that has a SessionBroker instead of ServerSession.
- Let's call Container persistence unit (or SessionBroker persistence unit).
The two main use cases:
- Unify multiple persistence units (with independent from each other object models).
- Split single persistent unit.
Design / Functionality
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|
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|
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.