AjaxFormSubmitCallback.javaAjaxCallback for Wicket form submission scenarios. Extends the basic callback contract with an onError(AjaxRequestTarget, Form<?>) method that fires when form validation fails. This interface separates the success path (inherited callback method) from the error path (new onError method), following the template method pattern at the interface level. Implementations receive both the Ajax target (to update error messages in the DOM) and the form instance (to inspect validation errors).The separation of success and error handling at the interface level is deliberate. Wicket forms operate in a two-phase validation cycle: first the form validates, then either the success or error handler runs. By encoding both outcomes in the interface contract, calling code in Micromata's custom Ajax behaviors can unconditionally invoke the appropriate method based on the form's validation state, without needing reflection or instanceof checks.
Like its parent AjaxCallback, this interface extends Serializable. In Wicket's page store architecture (which may serialize pages to disk or a database between requests), callback implementations must survive serialization. This is a common Wicket constraint — any object attached to a component tree must implement Serializable.
| Commit | What changed |
|---|---|
868d6abb7 through ceb63e8a1 | Six annual copyright header updates (2001-2021 → 2001-2026), spanning the full history of the file. The interface itself has never been modified beyond its initial creation — the form submit callback contract has proven sufficient for all form handling scenarios in the application. |