Skip to main content

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.

Jump to: navigation, search

Talk:EclipseLink/DesignDocs/328404

Revision as of 09:54, 25 October 2010 by James.sutherland.oracle.com (Talk | contribs) (New page: ==Session Type== The property to set the Session type, such as using a DatabaseSession should not be, "eclipselink.jdbc.single-connection", but "eclipselink.session.type". For SessionBrok...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Session Type

The property to set the Session type, such as using a DatabaseSession should not be, "eclipselink.jdbc.single-connection", but "eclipselink.session.type". For SessionBroker, this should be of type "SessionBroker", "DatabaseSession" could also be supported, the default would be "ServerSession", but other types could be supported, including a user defined class "<package>.<class>".

James.sutherland.oracle.com 13:54, 25 October 2010 (UTC)

Configuration

We should not have two (or 5??) different ways to configure this. Only a single logical way. The user should define a persistence unit for each ServerSession and another for the SessionBroker that lists the dependent persistence units.

James.sutherland.oracle.com 13:54, 25 October 2010 (UTC)

The property names should make sense, not be "eclipselink.define.my-set-property.value1". Should be "eclipselink.session.dependents"="pu1, pu2".

James.sutherland.oracle.com 13:54, 25 October 2010 (UTC)

This feature should be developed in 2 stages. Stage 1: Update JPA to use DatabaseSessionImpl, define SessionBroker from two independent persistence units. Stage 2: Support cross persistence unit relationships.

James.sutherland.oracle.com 13:54, 25 October 2010 (UTC)

Copyright © Eclipse Foundation, Inc. All Rights Reserved.