[EMAIL PROTECTED] wrote the following on 9/6/2005 9:39 PM:
I think we are maybe supposed to have one (most probably very lightweight) backing
bean for each page you see. Thus you have a prerender or not depnding on
what your page has to do... What do you think..?
Well you might be right, but I would think that would be a problem. I'll
often use the same JSP but have it behave in a slightly different
manner. For example, imagine an editForm.. this form might be used to
edit a "Regional manager" "Full time Employee" "part time employee"
where there might be some different fields needed on the page depending
on what employee yor were editing. (Front end logic deciding what to
show or hide). Now take it a step further, maybe for a manager, a drop
down select list needs to be present to select "US Region" but this
doesn't need to be populated for the other types of employees you are
editing. I only have one "employeeForm.jsp."
Although as I typed this I just realized I could handle the same
behavior I'm concerned about using a prerender if I wanted. In prerender
I could have..
if ( employeeType.equals("regional") { //populate List of regions }
So really the prerender probably would work just fine in this case.
I must admit though I having trouble grasping how a lot of this works in
JSF when the same page (view) is used in slightly different ways.
--
Rick
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
