Skip to Main Content

Application Development Software

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!

JBO-35007 in Portletized ADF Faces Page and alternative scenarios

John StegemanFeb 21 2007 — edited Feb 26 2007
Hi all,

I've started a new thread to address one of the problems referred to here 475371

In short, the issue arises when portletizing an existing ADF Faces page that uses an ADF BC bound af:Table on the page. I've got a very simple ADF Faces page that has an af:Table on it bound to the employees table in the Oracle HR schema. The af:Table allows sorting and has an af:selectTableOne in it's selection facet which contains an af:commandButton. The app works fine when run as a JSF page.

However, when I use the JSF-Portlet bridge to publish the page as a portlet (following all of the steps in the Web Center Developer's guide, including changing the state_saving_method to "server"), and placing the portlet on a ADF Faces page in a different project, I can consistently create JBO-35007 errors by:

* Sorting the data in the portlet by clicking the column header
* Selecting a different row and pressing the af:commandButton

Clearly, the current row of the iterator is not being saved properly. I can (of course) "fix" this behavior by setting EnableTokenValidation to "false" in the page definition of the ADF Faces page that has been portletized, but this has obvious side effects.

Should this behavior work as I am trying to implement it? Perhaps it doesn't make sense to "select" an item in a portlet like this (what am I going to do, as the parent application doesn't have access to the selected row information).

I can, however, think of a good use case:

User is using a web-store type application to browse items and add them to his shopping cart. Off to the side, we've got a portlet that shows recently purchased items for the user. User clicks item in that portlet (or selects and hits submit - as in my non-working example, above) and then the main web store application navigates to that item in the "main" section. How could I implement something like this? Any navigation case in the portlet is not exposed to the main application. Perhaps there is a different model by which to do this.... I cannot use a PDK event-type approach (this limits my use of Faces to create portlets), so I'm in a bind.

Thoughts and discussion much appreciated,

John
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Mar 26 2007
Added on Feb 21 2007
4 comments
1,874 views