How to implement concurrent nested Dialogs with BC4J and JClient

Question

Hello,
we are evaluating BC4J/JClient. In our application we have a navigation tree
in a Java client from which we can call nested dialogs to set attributes,
call business logic etc.
Is it possible to open more than one sub-dialog from our starting navigation tree
at the same time? Each sub-dialog should have its own transaction context.
To our knowledge we need a new application module for each sub-dialog in order
to start a new transaction. But how is the navigation tree updated if data
from the sub-dialogs is commited? The dialogs and the navigation tree don't share
the same model, do they? The navigation tree might have to show lots of data
retrieved over a slow connection, so simply updating the entire model is not a solution.
This could work if an intelligent caching fetches only the changed data.
So: What is the best way to implement sub-dialogs with their own transaction plus an
update mechanism?
Thanks for any help!

Answer 1

Hello,
we are evaluating BC4J/JClient. In our application we have a navigation tree
in a Java client from which we can call nested dialogs to set attributes,
call business logic etc.
Is it possible to open more than one sub-dialog from our starting navigation tree
at the same time? Each sub-dialog should have its own transaction context.
To our knowledge we need a new application module for each sub-dialog in order
to start a new transaction. But how is the navigation tree updated if data
from the sub-dialogs is commited? The dialogs and the navigation tree don't share
the same model, do they? The navigation tree might have to show lots of data
retrieved over a slow connection, so simply updating the entire model is not a solution.
This could work if an intelligent caching fetches only the changed data.
So: What is the best way to implement sub-dialogs with their own transaction plus an
update mechanism?To create a UI like this, see the sample on OTN at
http://otn.oracle.com/sample_code/products/jdev/jclient/jclient_binding_demo.html
YOu'd have to tweak this sample so that each sub-window comes up with it's own AM (as you've right suggested).
Regarding commit, yes, if you do not want to query the whole model on the navigator, you may use Transaction.commitAndSync() method to commit changes instead of simply performing a commit() call.
See javadoc on this method for details on how it works.
Thanks for any help!