ADF Table Filter Customization

This is to explain how a query listener on an af:table component is used to intercept
table queries so the developer can programmatically modify the query conditions
provided by the application user.e.g. when using the table filter.

Default query by ADF for filtering the result contains a map having parameters which are there in the table and their respective value's.

In a page you have a table filters enabled. And if you want to override the filter query through bean use the following code.

import java.util.Map;
import javax.el.ELContext;
import javax.el.ExpressionFactory;
import javax.el.MethodExpression;
import javax.faces.context.FacesContext;
import oracle.adf.view.rich.event.QueryEvent;
import oracle.adf.view.rich.model.FilterableQueryDescriptor;

public class BackingBean {
    public BackingBean() {
    }
    public void customQueryListner(QueryEvent queryEvent) {
        // Add event code here...
        try {
            FilterableQueryDescriptor fqd =(FilterableQueryDescriptor)queryEvent.getDescriptor();
            Map map = fqd.getFilterCriteria();
            String Type = (String)map.get("Type");
            if (Type.length() != 0) {
                Type = "%" + Type;
                map.remove("Type");
                map.put("Type", Type);
                fqd.setFilterCriteria(map);
            }
           
            this.invokeMethodExpression("#{bindings.ClaimsRVO1Query.processQuery}",Object.class, QueryEvent.class,queryEvent);
        } catch (Exception e) {
            // TODO: Add catch code
            e.printStackTrace();
        } }
    public Object invokeMethodExpression( String expr, Class returnType, Class[] argTypes,Object[] args){
     FacesContext fc = FacesContext.getCurrentInstance();
     ELContext elctx = fc.getELContext();
     ExpressionFactory elFactory = fc.getApplication().getExpressionFactory();
     MethodExpression methodExpr = elFactory.createMethodExpression(elctx, expr, returnType, argTypes);
     return methodExpr.invoke(elctx,args);
    
     }
    public Object invokeMethodExpression(String expr, Class returnType, Class argType, Object argument){
     return invokeMethodExpression(expr, returnType,new Class[]{argType}, new Object[]{argument});
     }
}



in your existing class you can use only three methods which will resolve your problem.

1. customQueryListner -  It is the query listner which you call from page
(queryListener="#{backingBeanScope.BackingBean.customQueryListner}")

2.invokeMethodExpression() which again calls one overrriden mwthod  invokeMethodExpression()