Skip to Main Content

Java Development Tools

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Bindings, ChangeEventPolicy, partialTriggers, af:table and rowSelection

547042Sep 10 2009 — edited Sep 11 2009
Hi,


consider the following situation in JDeveloper 11.1.1.1.0 in an ADF Faces application using ADF Bindings.

Setup:
1. Given an af:table with row selection enabled, e.g. rowSelection="single".
2. The table uses ADF Bindings (data controls over ADF BC, a POJO or anything else).
3.A. PPR is automatic, i.e. the underlying iterators all have the ChangeEventPolicy property set to "ppr" (so no partialTriggers settings are required in the pages).
3.B. OR PPR is manually configured, i.e. the underlying iterators all have the ChangeEventPolicy property set to "none" and partialTriggers are mutually configured for the table and another component (e.g. the table causes a button outside the table to refresh and vice versa; no playing with the rendered property).

Symptoms:
1. Actions in the table do not fire on first click, only on second one. The first click only changes the current row selection.
2. If a row is selected and you refresh (re-execute) the iterator, then the first row (which will be automatically selected after refresh) will be overwritten with the previously selected row.

Workaround:
Things work with ChangeEventPolicy="none" and partialTriggers configured to contain only the necessary components in the table (e.g. for the other component, you do not specify the table as partial trigger, but only some components in the table). However, this way one possibility is missing: declaratively refreshing the other component on row selection (it does work programmatically).

Test case:
[TablePPRTest.zip|http://www4.zippyshare.com/v/69055920/file.html] showing:
<li>ChangeEventPolicy="none" with mutual partialTriggers working when not using ADF Bindings (accessing beans directly) (Bean_and_partialTriggers.jspx)
<li>ChangeEventPolicy="ppr" with bindings not working (DataControl_and_ChangeEventPolicy_PPR.jspx)
<li>ChangeEventPolicy="none" with mutual partial triggers not working (DataControl_and_ChangeEventPolicy_None.jspx)
<li>ChangeEventPolicy="none" with no mutual partial triggers working (DataControl_and_ChangeEventPolicy_None_Fixed.jspx)

My questions:
Is it a known limitation that mutually configured partialTriggers don't work as expected?
What exactly can cause these symptoms?


Thanks for reading,
Patrik

Comments

Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Oct 9 2009
Added on Sep 10 2009
2 comments
666 views