To me it sounds like you need dividing all your form parts into components and on a per page basis you have only one form containing 1..n of your components. I do not see the point why all your components have to be forms. The form is just enclosing/surrounding your components. That's at least the way we deal with "complex" forms.
Jens Sent from my iPhone On 17.01.2013, at 17:22, sthomps <stho...@gmail.com> wrote: > I don't have an existing public site I can point to - all my examples are > internal. > > In essence it's fairly simple - componentize a form that can act on it's own > on a page or be nested within a parent form on page. > > Again not a huge deal but something that Wicket developers would need to be > aware of. > > Wicket Nested Forms <https://cwiki.apache.org/WICKET/nested-forms.html> > > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Nested-Form-Support-tp5719332p5719362.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
