Discussions
Categories
- 196.7K All Categories
- 2.2K Data
- 235 Big Data Appliance
- 1.9K Data Science
- 449.9K Databases
- 221.6K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 549 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 532 SQLcl
- 4K SQL Developer Data Modeler
- 186.9K SQL & PL/SQL
- 21.3K SQL Developer
- 295.4K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.1K Development Tools
- 104 DevOps
- 3.1K QA/Testing
- 645.9K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 153 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 17 Java Essentials
- 158 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 203 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 398 LiveLabs
- 37 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.6K Other Languages
- 2.3K Chinese
- 170 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 230 Portuguese
rollback between multiple regions

Hi everyone,
I use jdev 11.1.1.7.0
In my case I have to add multiple TaskFlows as a region into main page and all this regions use a same application module(root App Module) and in each region I have a commit and rollback button.
when I click rollback in a region, only components inside this region are reset but I also need to reset components in other regions. I've found this : https://blogs.oracle.com/vijaymohan/entry/rollback_button_with_the_property_immediate_set_to_true_doesnt_rollback_values_from_a_task_flow
but it isn't exactly my case and I can't use this way in my application, I'm wondering if anybody has any suggestion for this case (also I don't want to set 'immediate' property to 'false' for rollback button and transaction behavior of all taskflows are default).
the main page is something like below:
<f:view> <af:document id="d1"> <af:form id="f1"> <af:panelGroupLayout id="pgl1" layout="scroll"> <af:region value="#{bindings.departmentflow1.regionModel}" id="r1" partialTriggers="::r2"/> <af:region value="#{bindings.employeeflow1.regionModel}" id="r2" partialTriggers="::r1"/> </af:panelGroupLayout> </af:form> </af:document> </f:view>
Regards,
Habib
Answers
-
Timo Hahn Senior Principal Technical Consultant - Oracle ACE Director Member, Moderator Posts: 38,299 Red Diamond
Habib, you should watch https://youtu.be/mvH-VWEQQks and the other videos available at ADF Design & Architecture: http://www.youtube.com/playlist?list=PLJz3HAsCPVaSemIjFk4lfokNynzp5Euet which show you the difference between task flow transaction and application module transaction. As you are using task flows you should use task flow transaction.
If all your regions share the same transaction your use case is implemented.
Timo