>> This seems a lot easier than dealing with phase listeners. Why? Again I am forced to write this everywhere I need to use it. Lots 'o' boilerplate instead of just looking at the component name and doing my lookup regardless of the page etc.
I see the phase listener as a very good solution. . .if it would work the way I want it to. . I suppose in the end we like what we like. . . we do what we know. Rhys -----Original Message----- From: Mike Kienenberger [mailto:[EMAIL PROTECTED] Sent: April 27, 2006 2:57 PM To: MyFaces Discussion Subject: Re: Help me understand component lifecycle please. On 4/27/06, Neuman, Ben J., A&M IRM <[EMAIL PROTECTED]> wrote: > Rhys, I think you hit the nail on the head. You can't get the component > during the initial render response phase. The workarounds seem like an awful > lot of work for my needs. Maybe I'm being naive, but I don't see the problem. <component binding="#{initManagerBean.myComponent}" /> public class InitManagerBean { private UIComponent myComponent; public UIComponent getMyComponent { return this.myComponent; } public void setMyComponent(UIComponent myComponent) { this.myComponent = myComponent; if (reason) myComponent.setRendered(false); } } This seems a lot easier than dealing with phase listeners.
