I've added example number 72 to my examples page illustrating a technique to use for search pages based on view objects with named bind variables. It shows how to keep user-entered search criteria values "sticky" across pages so that when they return to the search page, their last search criteria are still there instead of the original default named bind variable value.
The solution involves using a backing bean property to intercept the get/set for the usual attribute binding, and conditionally returning the value of a process-scope attribute where you've saved the user's search criteria value.
See section 10.5.2, "How to Work with Named View Object Bind Variables" in the ADF Developer's Guide for Forms/4GL Developers for more information on working with view object named bind variables.
11:28:30 AM 
|
