Huh? What problem are you trying to solve?
If I use default scoped components then when I submit the form and validation fails, it loses all values on the object (presumably because the object itself falls out of scope)
If I use page scoped components then the above is solved (since validation occurs on the same page), and I can add an object. However, I then find that going to my edit page, and calling .update on the object returns the "updated" string, but does not update the DB
If I use session scoped components, it all works, except that the object doesn't go away, so I can add an object, edit it, but then when I go to add another one, I've still got the previous objects values on the form.
Does that make sense?
Ah, I see. You want a long running conversation
For anyone else, this is the simplest solution I ended up with:
<page view-id="*"> <navigation> <rule if-outcome="updated"> <redirect view-id="/confirm.xhtml"/> </rule> <rule if-outcome="persisted"> <redirect view-id="/confirm.xhtml"/> </rule> </navigation> </page> <page view-id="/confirm.xhmtl"> <end-conversation/> </page> <page view-id="/anaction.xhtml" > <begin-conversation/> </page>