Re: Struts & JSF - CommandButton Actions

2004-10-13 Thread Craig McClanahan
Sorry -- I think your confusion is my fault. You should use immediate="true" on a Cancel button, to bypass the Process Validations and Update Model Values phases. You should use immediate="false" on a Submit button that is intended to actually perform the requested transaction (i.e. save the data

Re: Struts & JSF - CommandButton Actions

2004-10-13 Thread Duncan Mills
I guess I'm confused because in a vanilla JSF page, if a command button calls an Action which updates the backing bean, then the Components referencing that updated attribute will be refreshed with the new value, even if the mode is immediate (using the current version of the RI). In this case

Re: Struts & JSF - CommandButton Actions

2004-10-13 Thread Craig McClanahan
On Wed, 13 Oct 2004 16:06:07 +0100, Duncan Mills <[EMAIL PROTECTED]> wrote: > I've been experimenting with the Struts + Faces integration library and > have hit one puzzling behavior using a .executing an > "action" in a form-bean > > If I have a page with a StrutsFaces form and > that's associat