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

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...]

OJDeploy: Documentation for the tool

Real DOCS:  http://docs.oracle.com/cd/E26098_01/user.1112/e17455/deploying_apps.htm#OJDUG645 OJDeploy Documentation if you run it from the command line - I keep looking for this so I though I would post it here so I remeber. Oracle JDeveloper Deploy 11.1.2.1.0.6081 Copyright (c) 2003, 2010, Oracle and/or its affiliates. All rights reserved. Usage:   ojdeploy -profile <name> -workspace <jws> [ -project <name> ] [ <options> ]   ojdeploy -buildfile <ojbuild.xml> [ <options> ]   ojdeploy -buildfileschema Arguments:   -profile               the name of the Profile to deploy   -workspace      full path to the JDeveloper Workspace file(.jws)   -project              name of the JDeveloper Project within the .jws where the Profile can be...

JBO-25013: TooManyObjectsException

oracle.jbo.TooManyObjectsException: JBO-25013: Too many objects match the primary key oracle.jbo.Key[Key null ]. Ok so for you it may be trying to insert a duplicate record this should explain your problem (also check trigger they could be the cause.) NOTE: You can also try to create a new duplicate EO if you have a page with two VO's using the same EO. This could sort your problems. For me I needed to add a launch listener on my LOV and clear the cache of my vo. LOV <af:inputListOfValues id="NameId" popupTitle="#{bindings.Name.hints.label}" value="#{bindings.RolName1.inputValue}" label="#{bindings.RolName1.hints.label}" model="#{bindings.RolName1.listOfValuesModel}" required="#{bindings.RolName1.hints.mandatory}" columns="#{bindings.RolName1.hints.displayWidth}" shortDesc="#{bindings.RolName1.hints.tooltip}" launchPopupListener="#{backingBeanScope.backingBean.launchPop...