ADF Task Flow Transaction Management and ADF Libraries

I received a question from blog reader to check if ADF Task Flow transaction management still works when different Application Modules are coming from ADF libraries. Blog reader had a doubt it will not work. I did a test - it works well, so I would like to share this sample application with you as well.

Sample application - transaction_adf_libs_11g.zip is based on ADF library with Application Module - HrModule:

Reusable Application Module is packaged as ADF library and later imported into main application:

Main application contains second Application Module called HrMainModule:

At the end there are two Data Control entries available, one from local AM and another from imported one:

Both Data Control entries are registered in DataBindings.cpx file:

I have created one container wrapper task flow to launch target task flow with transaction management:

Target task flow contains one fragment (includes data from both Data Controls) and return activity (performs commit):

There will be always new transaction started on task flow entry, commit will be done on task flow level from return activity (see above):

From index page we can launch target task flow and initialise new transaction:

Here we edit data from the first Data Control in the left section:

Also data from the second Data Control in the right section:

Both changes will be saved automatically with single Save button click with ADF Task Flow transaction management. No matter if Data Controls are based on Application Modules from the same application or ADF libraries.