When we have a form with only one submit button, the default Form's onSubmit() method will be called. If the Form has more than one submit button, then the mechanism works differently.
It might be a good idea to use
input instead of
button elements in your form hierarchy. IE tends to send all button values, making it difficult to establish the one used to submit.
To have more than one submit buttons in a Form, we need to create custom Button by subclassing from wicket.markup.html.form.Button. We define the custom Button behaviour by overiding the onSubmit() method and add the buttons to the Form. When the user click on any of the buttons, the specific behaviour of the button is executed by calling the button's onSubmit() method followed by execution of form's onSubmit() method.
We have a simple Form that contains two submit buttons. The class contructor looks something like this:
Note: without setDefaultFormProcessing(false), the "cancel" button is subject to validation like the "Ok" button.
The we have two custom Button classes with the override onSubmit() that looks something like below:
Alternatively, this can also be done with anonymous inner classes, e.g.
with the HTML being
Alternatively, you could use the form's onSubmit() method for the submit triggered by the OK button, and the Cancel button's onSubmit() method for the submit triggered by the Cancel button.