Commit on one application module also commits the other

Question

Jdev 11.1.1.4
I have a fusion ADF application where I have defined two Data Controls.
One is called AppModuleDatacontrol and the other AppModuleWSDataControl.
I do this in order to be able to commit DML made on one Data Control independently of the other.
The problem is that when a do something like:
AppModuleWSImpl am=(AppModuleWSImpl)Util.getApplicationModule("AppModuleWSDataControl");
am.getTransaction().commit();
Errors on VO of AppModuleDataControl are raised. They were not expected to be raised !
I have activated ADF logs and just after executing
AppModuleWSImpl am=(AppModuleWSImpl)Util.getApplicationModule("AppModuleWSDataControl");
and before executing the commit I get:
<BindingContext> <findDataControl> [4147] INFO: no refreshRegion, skipping cpx codebase lookup on AppModuleWSDataControl
<BindingContext> <put> [4148] BindingContext.put( AppModuleWSDataControl@edu_esade_view_DataBindings_cpx, oracle.jbo.uicli.binding.JUApplication )
<PropertyManager> <loadProperty> [4149] WARNING: Property jbo.maxpoolcookieageset to null
<PropertyManager> <loadProperty> [4150] Skipping empty Property jbo.maxpoolcookieage from null
<BindingContext> <put> [4151] BindingContext.put( AppModuleWSDataControl@edu_esade_view_DataBindings_cpx, oracle.jbo.uicli.binding.JUApplication )
<BindingContext> <put> [4152] BindingContext.put( AppModuleWSDataControl@edu_esade_view_DataBindings_cpx, oracle.jbo.uicli.binding.JUApplication )
<DebugDiagnostic> <print> [4153] DBG: DataControl:Looking for :_adf_dc_user_params_key_
<DebugDiagnostic> <print> [4154] DBG: DataControl:Looking for :_adf_dc_user_params_key_
<ADFLogger> <begin> Create nested Application Module
I don't know if "Create nested Application Module" is important but I don't want this AppModule to be nested of the other. I want them to be completly independent in order to achieve independance of the commit actions.
Any help ?

Answer 1

"1.Defining all BTF as "No controller transaction" I can assume both AppModule will always work with different transactions "
As long as they're defined as separate root AMs and you've used the <No Controller Transaction> option they will work with different db connections, therefore different transactions too.
"and one transaction in one AppModule will persist trough pages"
Within scope of one BTF yes. In scope of chained BTFs that's dependent on the BTF data control scope option. If you set that to isolated, each instance of a BTF will spawn a new instance of the AM in question (and new connections/transactions with the database). If you use shared, 1 instance of the AM will be shared (1 connection/transaction).
"2.What impact can have this in reusing BTF ? I have a jsf page reusing the same task flow in two regions. The taskflow performs some initialization. Will the regions undesirably interact one with the other ?"
That depends on the data control scope option as specified above. If you want them to be independent, use the isolated data control scope options on the BTF.
Consider reading the ADF Task Flow Transaction Fundamentals paper on this website for more information: http://www.oracle.com/technetwork/developer-tools/adf/learnmore/adfarchitect-1639592.html
CM.