<snip/>
> > page1: button "next" -> populate user/name + user/email +
> user/committer
> > page2: button "next" -> populate user/works-on-other-projects
>
> Typicly my Actions have a switch statement based on the button which was
> pressed.
> Or if using Cocoon's action convention this can be achieved with an action
> set as well.
> In both cases the idea is that the Action has an idea of where you are with
> the wizard navigation and resets just these fields, which are necessary to
> correctly populate the bean in the current step. I.e.
>
> act(...)
> {
> if (request.getParameter("command").equals("page1"))
> resetCommiterField
> else if (request.getParameter("command").equals("page2"))
> resetWorksOnOtherProjectsField
> ...
> bindFormToBean
> ...
> }
ok - then we are on the same track... but please consider the population
syntax I proposed. I think resetting something is misleading and it works
fine without.
I have already implemented an abstraction for the binding. So binding a
bean is the same a having no a simple DOM as instance store instead.
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
