Programatically change JSF Components

Question

Hi all,
I need to change "Disable" property of all components of a UIViewRoot based on calculated information. I can put an EL on Disable property to it, but i need to change all components once, and wouldn't like to put a EL on each component. I've tried to do it on Customized ViewHandlerImpl that extends oracle.adfinternal.view.faces.application.ViewHandlerImpl, method renderView
public void renderView(FacesContext facesContext,
UIViewRoot uiViewRoot) throws IOException,
FacesException {
// Try to get Children here, and change all editables components.
super.renderView(facesContext, uiViewRoot);
So, i've attempted get Children before super.renderView call, but in this moment Children is 0 length, only after super.renderView, i can get Children components.
Has anybody any tip about this?
Thanks

Answer 1

user9546730 wrote:
1. Do we loose any of the ADF faces (including Rich Client framework, partial rendering, Expression bindings, AJAX calls etc) feature by adding the component at runtime or programatically against the typical way of dragging and dropping the component to the screen at design time.(Except the drag and drop functionality and filling the component property at property window!)?No.
user9546730 wrote:
I am worried on the features part while taking programmatic approach bcoz i heard that there is no 100% guarantee on Postback features available and Adf component state feature in my scenario, if i take the programmatic approach.Should not be an issue if done correctly.
user9546730 wrote:
The scenrio in programatic approach:
There is one static yyy.jspx, where a declarative component(might be a layout kind of declarative component) is placed and binded to a bean, from the bean i am adding the ADF controls dynamically to the declarative component by parsing an xml.
Here if multiple users are accessing the yyy.jspx the content inside the declarative component can change user to user, So here the worry is whether the JSF/ADF lifecycle will work properly(the postback, ADF component state saving mechanism etc) for all the users.I would not use a declarative component nor the binding to initialize the component, else you'll calling for state issues that you fear about. Make a fully fledged component and initialize the component subtree in the tag file (or TagHandler if using Facelets, which I doubt you are), after creating the root component (the container).
Regards,
~ Simon