Last week i have faced a weird issue where in an action event on a command component (command image component) being suppressed (Suppressed is a wrong word, i learnt it later :) ).
Following is my learning:
That component's disable property was handled via managed bean based on some condition. In one scenario, i have set the property from false to true, but failed to add partial trigger on the component. Thus component's disable property was set to true, but the component is still enabled on the UI. Now, when i pushed this command component, all i was expecting is the execution of my action event and it didnt happen.
Following are the points that i have observed:
In a request life cycle, for every phase, there can be events which are queued up. For example, Value Change Events in APPLY_REQUEST_VALUES phase, Action events in INVOKE_ACTION phase etc., While executing the each phase, all the events that are queued up will be broadcasted for listeners.
In my case, i have a listener, but the event is not broadcasted, reason being, the component is not in the UIViewRoot (It was disabled). Hence, for an event to be broad casted, corresponding component should be active. Thus, i admit that, the event is NOT suppressed, but it was never broadcasted and i take all the blame :)
No comments:
Post a Comment