Your application contains a bounded task flow with four pages. The pages are all based on
different application modules and the task flow has the transaction property set to “Always Begin
New Transaction and a commit operation is defined as the return activity. The user makes some
changes on each of the pages but a commit failure occurs on the bindings in the third page.
Which of these scenarios describes the outcome of this situation?
A.
None of the changes on any of the pages is committed all are rolled back.
B.
Pages one and two and four are committed; page three is not committed.
C.
The changes on the first two pages are committed; the changes on the last two pages are not
committed.
D.
It depends on the value that has been set in the Transaction property on each application
module.
Explanation:
the answer is A
explanation:
“Always Begin New Transaction: A new transaction starts when the bounded task flow is entered, regardless of whether or not a transaction is in progress. The new transaction completes when the bounded task flow exits.”
yes, it should be A :
https://community.oracle.com/thread/2480310
”
Under 11gR1 the task flow options cause an automagical nesting of AMs (See: http://one-size-doesnt-fit-all.blogspot.com.au/2011/05/jdev-11g-task-flows-adf-bc-one-root.html) potentially explaining the behaviour you’re are using. Try using instead which turns the task flow transaction options off.
This automagical nesting behavior is an implementation detail of the framework and one that changes in 11gR2 and (the future) 12c releases.
“
A is correct answer