Sunday, May 6, 2007

Create/Edit operations and setCurrentRowWithKeyValue action in Oracle ADF

This post is based on my previous post - Invoking Create method programmatically. I have decided to extend it and to show how Edit form for newly created data should be opened. While Create functionality is reused, in Edit form Master-Detail relationship is implemented. Master part is implemented using ADF Faces form component, in Detail part ADF Faces table component is used. Table is created with dropdown list, according to solution described in Steve Muench screencast Nr. 7, available at JDeveloper/ADF Screencasts. In this post, I will be mainly focused on data transfer between Create and Edit forms.

Ok, let's say we have created custom Create form using a method in Application Module class. At the same time, Edit form functionality is developed based on the same View object as for Create form, but only with one difference - it is developed in declarative way, using JDeveloper wizards. Let's make a test and see what we will get. Create form:

When Creat button is pressed, Edit form is opened, but displayed data isn't correct:

Developed sample application -, handles this action correctly. Sample is based on LOCATIONS table from standard HR schema. Data from DEPARTMENTS table is used in Detail part of Master-Detailed relationship implemented in Edit form.

Value for primary key column is generated by database sequence, so for primary key column is assigned DBSequence type. So, how to open correct data in Edit form after Create operation is performed? Needed steps:
  1. From createLocation method implemented in Application Module class, you should return primary key value for newly created row - newLocation.getLocationId().getSequenceNumber();
  2. In Create form JSPX page Backing bean implemented action method binding, store returned primary key value into managed bean - JSFUtils.setManagedBeanValue("valueHolder.locationId", ((Number)result).stringValue()); Please, notice that oracle.jbo.domain.Number is converted to java.util.String, it is because setCurrentRowWithKeyValue accepts java.util.String type values
  3. In page definition file for Edit form, define setCurrentRowWithKeyValue action, in developed sample it looks similar:

  4. Don't foget to add in the same page definition file invokeAction element for defined setCurrentRowWithKeyValue:

When listed steps are passed, Edit form should be opened correctly. Let's test again, Create form:

When Create button is pressed, Edit form is opened with correct data:

When running sample application, don't forget to add adf-faces-impl.jar and jsf-impl.jar to application's WEB-INF\lib directory.


coroleu said...

Hi! And what happens the first time the edit page is rendered? The action will be invoked with a null parameter? That's correct?

Andrej Baranovskij said...

Hi Alberto,

In this sample it is assumed, that edit page will be opened only from create page. If you want to handle null value, you could add some logic into managed bean.


Koen Verhulst said...


is it also possible to pass the parameter in a the URL? eg: detailPage.jxps?id=1


Koen Verhulst