Rick Reumann <[EMAIL PROTECTED]> wrote on 08/23/2005 04:31:41 PM:
> Craig McClanahan wrote the following on 8/23/2005 4:10 PM:
>
> > The important principle is really pretty easy to articulate:
> >
> > IF you want your backing bean to implement ViewController
> > and get its event methods called, THEN the name of the
> > managed bean MUST conform to the mapping rules.
> >
> > That would mean, for a page named "/employee.jsp", then the managed
> > bean name (if you use the default mapper, which is recommended) MUST
> > be "employee", not "employeeBacking". Making that change would also
> > mean changing expressions that use "employeeBacking" now to use
> > "employee" instead, so you'd have:
> >
> > <h:dataTable value="#{employee.employees}" var="emp">
>
> Is it typical then to end up with several ManagedBean definitions for
> the same backingBean but for different mappings?
Funny, I was *just* thinking that! And then I figured it is because in the
Struts world, we are typically used to thinking of a form bean as being
shared by many jsps. But I think in the Faces world perhaps the backing
bean and the jsp are supposed to be really tightly integrated..(almost the
same (one) thing..?)
>
> In other words what if not just employee.jsp needed the "Employee"
> managed bean but also "employees.jsp", "employeeForm.jsp", "FooBar.jsp"
> all needed access to the managedBean? If all of them needed the
> prerender to fire off then I would think each of them would have to be
> created with separate managed bean definitions?
>
> --
> Rick
Geeta
