Thank you for your hints. I think I go for the last solution but I will have
a glance at the IFormVisitorParticipant though.
--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html
-
To unsubscribe, e-m
ember 2017 18:19
An: users@wicket.apache.org
Betreff: Nested forms in WizardStep
Currently we use the Wizard/WizardStep classes from wicket-extensions to set
required data for an object (in our case a checkout process with some user
Information, e.g. addresses etc.).
The first step contains a Login
Hi,
I never had to build such a scenario, but IFormVisitorParticipant can
help you?
Let your nested Form (or its parent) implement the interface and return
false from #processChildren().
Have fun
Sven
Am 17.11.2017 um 09:18 schrieb Dirk Forchel:
No, I was not searching for a solution how
No, I was not searching for a solution how to "disabling nested form
validation" as I was unsure whether it's a proper solution to use nested
forms in a WizardStep.
To get an impression how the checkout should look like have a look at
http://demo.designing-world.com/bigshop-aa/bigshop/checkout-1.h
Have you tried
https://stackoverflow.com/questions/26502864/disabling-nested-form-validation-in-wicket
?
Have fun
sven
Am 16.11.2017 um 18:19 schrieb Dirk Forchel:
Currently we use the Wizard/WizardStep classes from wicket-extensions to set
required data for an object (in our case a checkout
Currently we use the Wizard/WizardStep classes from wicket-extensions to set
required data for an object (in our case a checkout process with some user
Information, e.g. addresses etc.).
The first step contains a Login form with two "required" input components
for the credentials and a separate "Lo
