[CAY-2638] Cayennne sends commit

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 4.1.RC2
• Component/s: Core Library
• Assignee: Unassigned
• Reporter: Tomas Jura
• Created: 04/Nov/19 22:39
• Updated: 05/Nov/19 05:48
• Resolved: 05/Nov/19 02:21

Description

The cayenne sends the commits to the database ( after a lazy fetch, ... ). The transaction boundaries are defined by a superior business logic and ORM must not corrupt this logic and boundaries. Imagine for example that the Cayenne is part of an XA transaction, where the commit is controled by a transaction manager and the commit guided by two phase commit protocol. I'm afraid that any attempt to control transaction boundaries from ORM sooner or later clash with required boundaries.

This design feature, automaticaly reject using cayenne as an ORM for any bit complex project which want to use savepoint/rollback/commit commands. As far as I remember Cayenne 3 did not touched the transaction state. Why Cayenne 4 touching the transaction?