Thanks gary.. So having 2 backing beans used in 1 jsp looks less straight forward, but i guess workable..
On 7/28/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hello > > > > I imagine this is a stupid question, but I've configured all the bits > > i can see that would need configuring to have my viewcontroller > > implementing classes running their init and destory methods at the > > relevant times. > > > > I've configured the Filter, Chain listener, the viewhander.. My base > > backing bean extends AbstractViewController. And my backing beans > > where already wired into faces config before i had their superclass > > extends AbstractViewController. > > > > Any clues would be appeciated.. > > > > Shale has an assumed mapping of the faces view id and the managed bean name > that you register your view controller under within the faces config. The > rules for this mapping is pluggable but the default implementation is > DefaultViewControllerMapper. > > If your jsp is "/mypage/page.jsp", you would register your view controller > with an managed bean name of "mypage$page". The additional life cycle events > on the veiw controller are outside of the normal faces lifecycle so the > naming rule is the glue. Kind of similar to the struts form bean too. > > > > Gary > > > > > Mark > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
