Setting Component rendered property On Page-Load

Question

I am using Jdeveloper 11g - fusion- web application.
What I am trying to do is, onpageload, I am trying to over-ride some default properties of my uiComponents like rendered or read-only programatically.. I was referring to Steve Muench's Example no 60 -
[http://radio.weblogs.com/0118231/stories/2004/09/23/notYetDocumentedAdfSampleApplications.html] to do this. That is to say, I have a controller for my page-def file which implements the PagePhaseListener. It looks something like
{color:#ff0000}
public void beforePhase(PagePhaseEvent pagePhaseEvent) {
if (pagePhaseEvent.getPhaseId() == Lifecycle.PREPARE_MODEL_ID) {
if (!isPostback()) {
new AttributeAuthorization().initializeAuth();
}{color}
{color:#000000}
And inside the initializeAuth() method, I get a handle to the current instance of FacesContext, get the context.getViewRoot()
component tree, iterate on the component tree and call uiComponenet.setRendered(false/true)
for some components. My problem is, when the page is rendered, the values I have set is not reflecting. But on the next request, ie, if I simply press the commit button on my page, all the components are rendered the way I expect them to...
I tried doing this in different phases of the life-cycle like PREPARE_RENDER_ID, PREPARE_MODEL etc, in before and after methods, but my page renderes the way I expect it to only on the next request/page submission!!
{color}
Edited by: Julian Stephen on Dec 7, 2008 9:05 PM
Edited by: Julian Stephen on Dec 7, 2008 9:14 PM

Answer 1

The reason why I do-not want to use a managed bean is that, I want to do this for all the components in my page(It is reasonably big too). So doing this by a managed bean would mean, I need an interface which has as many getter methods as the no of components in the page. Also, we are still in developement which means everytime some-one adds a new component in the page they need to add a new getter method in the interface. Well not just the interface, but also in all the implementing classes...
The business use-case is that, I have one page in the application which has different levels of visibility(Some components read-only, some not rendered, some editable) based not just on who is logged in but also on other business conditions decided on the page prior to this. So based on these different conditions I build different schemes or themes(I have like 3/4 themes) which decides which components are read-only, which all are editable etc etc... Now I have to apply this 'theme' on to my page :). The way I am trying to do it now, everytime a new component is added, its visibility just need to be set in the property files of different themes.
Thanks,
Julian