You'll need to use a component binding only when you need to change one of the component's attributes dynamically.For example, if an application renders a component only under certain conditions, it can set the component's Retrieving values from other implicit objects is done in a similar way to the example shown in this section.And yes, that is one way of doing it if the value does indeed go to the binded component but does not populate to the value.tag which not updating the managed bean values when attribute is readonlytrue.Using immediate causes the component Action Listener or action-method to be executed at the end of the apply-request-values phase, ie before any non-immediate value validation and before any backing bean updates (update-model phase).If the action method is of a form that returns a navigation string, then: if the normal flow is not desired.
I do not see how the approach suggested by Americo Pinto solves anything.
List; @Component @Managed Bean @Request Scoped @URLMappings(mappings=) public class Posts Controller Tim will probably correct me in the morning if I am wrong, but JSF should use the getter to get a copy of your objects that are used by the JSF components.
I couldn't actually understand the error that was stated, but Controller or not, Request Scope is almost 100% worthless in JSF.
In particular, this means that any Value Change Listener associated with the component will execute before any immediate UICommand component's Action Listener (assuming the command component occurs later in the page).
Marking an input component as immediate does NOT affect the model update; any new data is still pushed into the model at the Update Model phase (ie after any immediate command components have executed). Value Change Listener could be used to update the model directly.