Hi,

> In most cases it's not necessary to include a form in panels

In most case, I agree, but sometime, there is no other choice: wizard steps
for instance.

Best regards,
Sebastien


On Fri, Nov 20, 2015 at 5:02 PM, Sven Meier <s...@meiers.net> wrote:

> > When a nested form is submitted Wicket calls the processing methods
> > only for the nested form.
> > I don't see a reason why #inputChanged() should be an exception.
>
> The outer form is not processed, because we don't want validation errors
> to appear. #inputChanged() is called, so that on a possible render of the
> whole page the input of the user is preserved.
>
> > it is very common to reuse components in Wicket
>
> I'm shocked ;)
>
> > So a Panel with a Form could appear as a nested anywhere.
> > That is the main reason to support nested forms.
>
> Yes, and it comes with a price. In most cases it's not necessary to
> include a form in panels - generally I would advice against it:
> - because "it's not supported in HTML"
> - again, it comes with a price (see above)
>
> Have fun
> Sven
>
>
>

Reply via email to