Discussions
Categories
- 385.5K All Categories
- 5.1K Data
- 2.5K Big Data Appliance
- 2.5K Data Science
- 453.4K Databases
- 223.2K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 47 Multilingual Engine
- 606 MySQL Community Space
- 486 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.2K ORDS, SODA & JSON in the Database
- 585 SQLcl
- 4K SQL Developer Data Modeler
- 188K SQL & PL/SQL
- 21.5K SQL Developer
- 46 Data Integration
- 46 GoldenGate
- 298.4K Development
- 4 Application Development
- 20 Developer Projects
- 166 Programming Languages
- 295K Development Tools
- 150 DevOps
- 3.1K QA/Testing
- 646.7K Java
- 37 Java Learning Subscription
- 37.1K Database Connectivity
- 201 Java Community Process
- 108 Java 25
- 22.2K Java APIs
- 138.3K Java Development Tools
- 165.4K Java EE (Java Enterprise Edition)
- 22 Java Essentials
- 176 Java 8 Questions
- 86K Java Programming
- 82 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 208 Java User Groups
- 25 JavaScript - Nashorn
- Programs
- 667 LiveLabs
- 41 Workshops
- 10.3K Software
- 6.7K Berkeley DB Family
- 3.6K JHeadstart
- 6K Other Languages
- 2.3K Chinese
- 207 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 474 Portuguese
Closing a task flow with transactions, but no changes

Hi there
When using bounded task flow that use shared transactions I would like to know what is best practice when closing the task flow if no changes need to be persisted to the database.
We would like to have three buttons on our pages/fragments: Save, Cancel, Close. The Save button flows to a TaskFlowReturn which has an End Transaction set as commit. The Cancel button has an End Transaction set to rollback.
We intend the Close button to simply return to the calling flow, without calling a commit or rollback.
We can enable/disable the buttons depending on the "dirty" state.
We cannot, however, put a TaskFlowReturn on the flow without setting the End Transaction setting.
My question is: would setting a rollback End Transaction on the close button result in an unnecessary call to the database?
How should this be implemented should we want the Save, Cancel and Close buttons?
Thanks in advance
Answers
-
You should use commit. The commit is only executed in the task flow which holds the transaction which is the parent task flow. If a sub task flow commits nothing happens and the changes are be committed when the parent commits. If nothing has changes nothing happens.
If you use a rollback the parent has to rollback his changes too, which is not what you want to do.
Timo
-
When using bounded task flow that use shared transactions ...
Which settings has your taskflow, perhaps:
Shared Data Control Scope + Use Existing Transaction if possible ?
Regards,
Zlatko