Mark,
Can you provide a more concrete example of the problem?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kito D. Mann - Author, JavaServer Faces in Action
http://www.virtua.com - JSF/Java EE consulting, training, and mentoring
http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info
phone: +1 203-653-2989
fax: +1 203-653-2988
> -----Original Message-----
> From: Mark Collette [mailto:mark.collette_at_icesoft.com]
> Sent: Friday, May 16, 2008 5:38 PM
> To: dev_at_javaserverfaces.dev.java.net
> Subject: ValueChangeEvent phases
>
> Right now, you can use the immediate attribute on
> UIInput/EditableValueHolder to determine if the ValueChangeEvent will
> be
> broadcast in ApplyRequestValuesPhase or ProcessValidationsPhase. But,
> a
> lot of the time, if one is using that to control the value of some
> other
> UIInput component, one would re-queue the event to be broadcast after
> UpdateModelPhase or InvokeApplicationPhase, so that this other
> UIInput's
> value, being updated in UpdateModelPhase, won't stomp over the
> programmatically set value from the ValueChangeListener.
>
> Is there anything in the JSF 2.0 specification for an attribute to make
> it use UpdateModelPhase or InvokeApplicationPhase, so that developers
> won't have to write the bean re-queuing code? Something that would
> simplify things, and keep it more declarative.
>
> Mark Collette
> ICEsoft Technologies, Inc.
> http://mark-icefaces-reflections.blogspot.com/
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_javaserverfaces.dev.java.net
> For additional commands, e-mail: dev-help_at_javaserverfaces.dev.java.net