A dynamic table based on run-time created view object -- please help!

Question

Hello!
I'm trying to create a dynamic table based on an run-time created view object. All go ok, but table binding component take the first view/iterator state and don't reflect changes they have. Please, take a look:
1. At run-time the view is being replaced by new red-only one based on query in application module:
getQueryView().remove();
createViewObjectFromQueryStmt("QueryView", statement);
2. Page definition file contains an iterator (using iterator or methodIterator - doesn't matter) binding and table, which binds to the iterator, like:
<methodIterator id="distributeQuery1Iter" Binds="distributeQuery1.result"
DataControl="QueryServiceDataControl" RangeSize="10"/>
<table id="distributeQuery11" IterBinding="distributeQuery1Iter"/>
3. The page code uses <af:table>. But, if I use table binding (it's right) like this:
<af:table var="row" value="#{bindings.distributeQuery11.collectionModel}">
<af:forEach items="#{bindings.distributeQuery11.attributeDefs}" var="def">
the table will never changed (i.e. still show the first view instance).
When I tried to use iterator binding directly (it's bad and cannot provide all needed features unlike CollectionModel from table binding) I saw that table works!
(Code is somehing like:
<af:table var="row" value="#{bindings.myIterator.allRowsInRange}">
<af:forEach items="#{bindings.myIterator.attributeDefs}" var="def">
Why the table binding do not reflect changes in iterator? Or should I use different approach?
Thanks in advance!
Ilya.

Answer 1

I got it to work! I used a hybrid approach comprised of some of your code and some of Steve Muench's AcceessAppModuleInBackingBean example.
In the setBindings method, I execute an app module method that redefines the query, then I used your code to delete and recreate bindings and iterator:
public void setBindingContainer(DCBindingContainer bc) {
this.bindingContainer = bc;
rebuildVO();
The rebuildVO() method looks like the code you provided in your example:
private void rebuildVO() {
DCDataControl dc;
DispatchAppModule dApp;
DCBindingContainer bc;
DCIteratorBinding it;
OperationBinding operationBinding;
ViewObject vo;
DCControlBinding cb;
try {
bc = getBindingContainer();
dc = bc.findDataControl(DATACONTROL);
dApp = (DispatchAppModule)dc.getDataProvider();
// Execute App Module Method to rebuild VO based upon new SQL Statement.
dApp.setDispatchViewSQL();
vo = dApp.findViewObject(DYNAMIC_VIEW_NAME);
it = bc.findIteratorBinding(DYNAMIC_VO_ITER_NAME);
it.bindRowSetIterator(vo, true);
// logger.info("Remove value binding...");
cb = bc.findCtrlBinding(DYNAMIC_VIEW_NAME);
cb.getDCIteratorBinding().removeValueBinding(cb);
bc.removeControlBinding(cb);
// logger.info("Creating new value binding...");
FacesCtrlRangeBinding dynamicRangeBinding =
new FacesCtrlRangeBinding(null,
bc.findIteratorBinding(DYNAMIC_VO_ITER_NAME), null);
// logger.info("Add control binding...");
bc.addControlBinding(DYNAMIC_VIEW_NAME, dynamicRangeBinding);
} catch (Exception e) {
e.printStackTrace();
And my App Module method that redefines the view object looks like this:
public void setDispatchViewSQL() {
String SQL =
"begin ? := PK_BUsiNESS.F_GETDISPATCHVIEWSQL();end;";
CallableStatement st = null;
String ViewSQL = null;
try {
st = getDBTransaction().createCallableStatement(SQL,
DBTransaction.DEFAULT);
* Register the first bind parameter as our return value of type LONGVARCHAR
st.registerOutParameter(1, OracleTypes.LONGVARCHAR);
st.execute();
ViewSQL = ((OracleCallableStatement) st).getString(1);
findViewObject(DYNAMIC_VO_NAME).remove();
ViewObject vo = createViewObjectFromQueryStmt(DYNAMIC_VO_NAME, ViewSQL);
vo.executeQuery();
} catch (SQLException s) {
throw new JboException(s);
} finally {
try {
st.close();
} catch (SQLException s) {
s.printStackTrace();
When I run it I get my desired results. One thing I don't quite understand is why when the page is first rendered it shows the last set of records rather than the first. Now I have to figure out how to put navigation URLS in each of the table cells.
Thanks for your help; I would not have gotten this far without it,
Jeff