Refreshing ADF Query Component after changing some property of a criteria

Question

Hi All
Use Case : Refreshing ADF Query Component after changing some property of a criteria attribute.
I have a query panel with 2 query criteria i.e. FirstName and DepartmentId where in DepartmentId is a drop down. The scenario is like when change the value of DepartmentId to 'Finance' with code value of '100' then my criteria attribute 'Firstaname' should be invisibe(queriable=false).
Approach: Have overriden the queryOperationListener of adfquery as " queryOperationListener ="#{backingBeanScope.backing_queryLstener.processQueryOperation}" "
My backing bean method goes as below :
public void processQueryOperation(QueryOperationEvent queryOperationEvent) {
// Add event code here...
if( queryOperationEvent.getOperation().equals(queryOperationEvent.getOperation().CRITERION_UPDATE) ){
DCBindingContainer bindings = (DCBindingContainer)this.getBindings();
DCIteratorBinding iter =bindings.findIteratorBinding("EmployeeView1Iterator");
ViewObjectImpl voimpl = (ViewObjectImpl)iter.getViewObject();
ViewCriteria vc = voimpl.getViewCriteriaManager().getViewCriteria("EmployeeViewCriteriaDemo");
Row currRow = vc.first();
System.out.println("Department :"+currRow.getAttribute("DepartmentId"));
if( (Integer)currRow.getAttribute("DepartmentId") ==100 ){
AttributeDef[] attrs = voimpl.getAttributeDefs();
int attrIndex = voimpl.getAttributeIndexOf("FirstName");
ViewAttributeDefImpl attrDef = (ViewAttributeDefImpl) attrs[attrIndex];
attrDef.setQueriable(false);
// AdfFacesContext.getCurrentInstance().addPartialTarget(getQryId1()); //here i need to refresh the query component which is not happening
// refreshQueryComponent(getQryId1());
Everything is happening as expected but the query panel s not get refreshed.When i refresh the whole link/page then i can see the change.
Please suggest.
Thanks in adv.
-Sanjeeb

Answer 1

Hi,
can's say anything about the first part of the question as more insight to the implementation would be required. However, have a look at http://www.oracle.com/technetwork/developer-tools/adf/learnmore/83-bidi-synchronization-tree-form-401841.pdf, which may be what you are looking for
To the second part: You can programmaticallly refresh the tree component from a managed bean. So instead of using the declarative PPR option (or ChangeEventPolicy set to PPR on the iterator binding) you can wire the submit button to the managed bean, perform your validation and if it fails don't refresh teh tree
The call is
AdfFacesContext.getCurrentInstance().addPartialTarget(the_tree_instance)
Frank