Craig McClanahan wrote the following on 9/6/2005 9:57 PM:
If you use prerender() the way it's intended to be used (on the destination
page, not the origin page -- and not trying to share them across multple
pages) you'll quickly discover that you really do want it called every time.
Ok, let me try to be more clear. For example, lets have "search.jsp"
If searching for a regular employee lets have it basic - only one field
"name" (only field you can search by).
But search.jsp can also be used to search for a "regional manager"
(still just an employee), but for that kind of search we need to show
the list of 'regions' in a drop down list.
Wouldn't both scenarios be backed by the same bean? If so they would
both share the same prerender method, yet we only need the 'regions'
populating when we had the case that we were searching for a regional
manager.
How do you get around not having some kind of logic in the prerender
method to decide whether or not it needs to populate the 'regions' list
for the drop down?
--
Rick
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
