Skip to main content

ADF : Refreshing a service backed table and keeping the correct item highlighted

Make sure your table has  displayRow="selected" set.

<af:table value="#{bindings.CustomerVO.collectionModel}" var="row"
  rows="#{bindings.CustomerVO.rangeSize}"
  emptyText="#{bindings.CustomerVO.viewable ? 'No data to display.' : 'Access Denied.'}"
  fetchSize="#{bindings.CustomerVO.rangeSize}" rowBandingInterval="0"
  selectedRowKeys="#{bindings.CustomerVO.collectionModel.selectedRow}"
  rowSelection="single" id="table" columnStretching="last" immediate="true"
  displayRow="selected" binding="#{viewScope.customerTypesBean.table}"
  selectionListener="#{viewScope.customerBean.handleTableRowSelection}">

Invoke the following code when your table needs a refresh

//use the name of your tables result iterator here
    DCIteratorBinding iterator = BackingBeanUtils.getIteratorBinding(getResultsIteratorName());
    int rangeIdx = iterator.getCurrentRowIndexInRange();
    int rangePos = iterator.getRangeStart();
    int actualPos = rangeIdx + rangePos;
    String action = "findCustomerVO";
//execute the service here
    ADFUtils.executeOperationBinding(action, new HashMap());
    int rem = actualPos % iterator.getViewObject().getRangeSize();
    int page =
      (int) Math.floor(actualPos / iterator.getViewObject().getRangeSize());
    iterator.getViewObject().setRangeStart(page * iterator.getViewObject().getRangeSize());
    iterator.getViewObject().setCurrentRowAtRangeIndex(rem);

Comments

Popular posts from this blog

ADF sort of generic screen for tables with the same structure

We have a couple (about a hundred) of tables with the same structure (Code, Description, Create Date, Update Date). So I wanted to do something simple so that I did not have to create all these screens 1) EO   I created the EO based on one of the tables I had that had the above columns. I then Added a transient attribute called table name to my EO based on a groovy expression. (the expression needs to change as I am reading web tier stuff from the model layer but I will fix this later) I then generated a java class for my EO. And added the following overriden method to my newly created java class. protected StringBuffer buildDMLStatement(int i, AttributeDefImpl[] attributeDefImpl,   AttributeDefImpl[] attributeDefImpl2, AttributeDefImpl[] attributeDefImpl3, boolean b) {   StringBuffer statement = super.buildDMLStatement(   i, attributeDefImpl, attributeDefImpl2, attributeDefImpl3, b); return new StringBuffer(StringUtils.replace(statement.to...

Util code

public static MethodExpression getMethodExpression( String expr, Class returnType, Class[] argTypes){ FacesContext fc = FacesContext.getCurrentInstance(); ELContext elctx = fc.getELContext(); ExpressionFactory elFactory = fc.getApplication().getExpressionFactory(); return elFactory.createMethodExpression( elctx, expr, returnType, argTypes); } public static javax.faces.el.MethodBinding getMethodBinding( String expr, Class[] argTypes){ FacesContext fc = FacesContext.getCurrentInstance(); ELContext elctx = fc.getELContext(); return fc.getApplication().createMethodBinding(expr, argTypes); } SetPropertyListener listener = new SetPropertyListener( ActionEvent.class.getName()); listener.setFrom(link.getRoute()); listener.setValueExpression("to", JSFUtils.getValueExpression("#{pageFlowScope.route}", String.class)); action.addActionListener(listener); AdfFacesContext.getCurrentInstance().getPageFlowScope() .put("route", lin...

MANIFEST.MF merge JDeveloper for an executable jar

Goto your project > properties. Then click on deployment in the menu. Edit or add a jar deployment profile. Fill in the details under jar options (select Include manifest and give it a main class name) Also remember that the merge functionality only works with a BLANK line at the end of the merge file. REALLY this caught me. My merge file contents: Class-Path: commons-codec-1.3.jar [...empty line here CRLF...]