Skip to main content

ADF: Revert only changes to one View Object (mini rollback)

JDeveloper 11.1.2.1

I really struggled to get this working so hopefully this helps someone out:
I needed to just rollback the changes on a single vo backed popup and not the parent object so this is what I did. (not the pk for this view was rowid based and normal methods to do this just refused to work)
Also I failed to mention it is a multi line editable table.

NOTE: Performance was not an issue here.

Phase 1) Parent VO Impl
  We have a parent object for all our View Objects so I implemented this method there.

 public void clearAllCache() {
  //dont ask
  ViewRowSetImpl drsi = super.getDefaultRowSetInternal();
  while(drsi.hasNext()) {
    Row item = drsi.next();
  }

  Iterator iter = super.getEntityDef(0).getAllEntityInstancesIterator(this.getDBTransaction());
  while(iter.hasNext()) {
    EntityImpl entityItem = (EntityImpl) iter.next();
    if(entityItem.getEntityState() == EntityImpl.STATUS_NEW ||
      entityItem.getEntityState() == EntityImpl.STATUS_DELETED) {
      entityItem.refresh(EntityImpl.REFRESH_REMOVE_NEW_ROWS | 
  EntityImpl.REFRESH_UNDO_CHANGES);
    }
  }
  getViewObject().clearCache();
}

Phase 2) AM (implement this method and map it as a client interface)
 public void rollbackVO(String iteratorName) {
    DCIteratorBinding iterator = ((DCBindingContainer)   
      BindingContext.getCurrent().getCurrentBindingsEntry()).
      findIteratorBinding(iteratorName);

  ViewObject vo = iterator.getViewObject();
  if(vo instanceof WesbankVOImpl) {
    ((WesbankVOImpl) vo).clearAllCache();
  }
 }

Phase 3) Backing bean method (mapped to close popup button - all our popups work the same way and the backing bean holds the current popup iterator name)
public String resetPopup() {
  Map params = new HashMap();
  params.put("iteratorName", getCurrentPopupIteratorName());
  ADFUtils.executeOperationBindingWithoutException("rollbackVO", params);
  AdfFacesContext.getCurrentInstance().returnFromDialog(null, null);
  return null;

Phase 4) Page
Bind a method action to your page for the rollbackVO method

This still needs to be cleaned up (ie the getEntityDef(0) wont work everywhere).

Comments

Popular posts from this blog

ADF Encountered deferred syntax #{ in template text.

OracleJSP error: oracle.jsp.parse.JspParseException:  Error: Encountered deferred syntax #{ in template text.  If intended as a literal, escape it or set directive  deferredSyntaxAllowedAsLiteral This normally happens when you have some tag lib dependancy problems but this was  not the case for me... My problem: For some reason my model project had web stuff in it(public html etc)  so I had to remove the public html stuff from my project and manually edit the Model.jpr project file and remove the tag lib entries at the bottom o the file. Go figure.    

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

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 found. If omitted, the Profile is assumed to be in the Workspace.   -buildfile            full path to a build file for batch deploy   -buildfileschema  print XML Schema for the build file