martin, as it is now you are not forced to implement a method as they are implemented on ajaxbutton and besides that you might just do your logic on form on submit. On 20 Jun 2015 11:47, "Martin Grigorov" <[email protected]> wrote:
> Hi Ernesto, > > I guess the reason is to make you override at least one of #onSubmit(), > #onAfterSubmit() and/or #onError(). > Not every app needs to implement all of these methods, but every > application needs at least one of them. > > This is how I explain this to me. > > Martin Grigorov > Freelancer. Available for hire! > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Sat, Jun 20, 2015 at 8:47 AM, Ernesto Reinaldo Barreiro < > [email protected]> wrote: > > > Saturday mornings.... :-( What's the reasoning behind > > > > > > > https://github.com/apache/wicket/blob/master/wicket-core/src/main/java/org/apache/wicket/ajax/markup/html/form/AjaxButton.java > > > > being abstract? It does not forces you to override any methods :-) > > > > form.add(new AjaxButton("save") { > > > > > > }) > > > > > > On Sat, Jun 20, 2015 at 7:45 AM, Ernesto Reinaldo Barreiro < > > [email protected]> wrote: > > > > > Hi, > > > > > > What the reasoning behind > > > > > > > > > -- > > > Regards - Ernesto Reinaldo Barreiro > > > > > > > > > > > -- > > Regards - Ernesto Reinaldo Barreiro > > >
