Practical RichFaces, Second Edition

CHAPTER 2 GETTING STARTED
}
}
public void selectComponents (AjaxBehaviorEvent event){
renderComponents.add(selection);
}
public List getRenderComponents() {
return renderComponents;
}
public String getSelection() {
return selection;
}
public void setSelection(String selection) {
this.selection = selection;
}
public Date getClock1() {
return new Date();
}
public Date getClock2() {
return new Date();
}
public Date getClock3() {
return new Date();
}
Notice that we no longer need to add the button to the list of components to be rendered. Running
the application, everything is now updated as you would expect.
Simplicity is just one of the advantages to using and the render attribute bound to EL.
One more advantage is that evaluating the ids on the server instead of getting them client side is more
secure, as anyone could send a request with ids using . If this happens with , these
ids will simply be ignored.
Note The same functionality is available on other RichFaces tags, such as ,
, , and . We will cover this in Chapter 3. We used the listener
attribute on either or behaviors. If you have an action or an actionListener set on
the button or link, those will be invoked in a standard way.
execute Attribute Options
The same way it’s possible to bind the render attribute to EL or decide which components to render in
runtime, it’s also possible to decide which components to execute in runtime or bind the execute
attribute to EL. For example:
When using just JSF 2, execute works in similar fashion to render in regards to when the ids are
resolved. As with render, the ids in execute are resolved but then rendered to the page and only used on
the next request. When using RichFaces a4j:ajax behavior instead of f:ajax, then ids are resolved and
those components are executed in the current request.