Dive into Oracle ADF

Send me a mail
 Dive into Oracle ADF   Click to see the XML version of this web page.   (Updated: 9/30/2009; 10:06:29 AM.)
Tips and tricks from Steve Muench on Oracle ADF Framework and JDeveloper IDE

Search blog with Google:

Search BC4J JavaDoc:

September 2009
Sun Mon Tue Wed Thu Fri Sat
    1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30      
Aug   Oct

Get Firefox!

The views expressed on this blog are my own and do not necessarily reflect the views of Oracle.

Thursday, September 03, 2009

My Easier Interactive Data Entry article in Oracle Magazine explains the new Auto-PPR feature in JDeveloper 11g. This feature makes it possible for you to avoid manually setting the "partialTriggers" property on UI components in most cases. With the new Auto-PPR feature enabled, the ADF framework automatically "repaints" any UI components whose data bound attribute values have changed, regardless of how they have been changed (by the user, by a calculated attribute's dependent attribute's value changing, by programmatic business logic, etc.)

I recently noticed, however, that the JDeveloper 11g R1 ( design time incorrectly shows the "ppr" as the default setting for the ChangeEventPolicy of an iterator binding. The default of this property is still "none", even though you see "(default) ppr" in the property inspector.

In short, if you want to use the Auto-PPR feature in 11g R1, then just as you did in previous JDeveloper 11g releases, manually set the ChangeEventPolicy of the iterator binding to the value "ppr" yourself.


11:52:23 PM    

I've added example# 149 to show the correct syntax to use to reference custom view row and view object methods from the Groovy expression of a calculated view object attribute.

10:58:14 PM    

I've added example# 148 to illustrate a technique to declaratively initialize the bind variables of a view object at task flow startup time.

10:56:56 PM    

© Copyright 2009 Steve Muench.