Unless you use a more powerful language than Java that provides something like Scala's Trait I don't see how you could implement your solution without re-implementing the standard Ajax links.
Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Fri, Oct 31, 2014 at 5:33 PM, Andrea Del Bene <an.delb...@gmail.com> wrote: > You are suggesting something like we see in GlobalUpdateAjaxAttributesTest, > right? What I was thinking of was a less powerful solution suited to > decorate standard AJAX links only in few cases you might need confirmation. > > You have to refresh your knowledge about the related code. >> >> Or I should ... >> >> Martin Grigorov >> Wicket Training and Consulting >> https://twitter.com/mtgrigorov >> >> On Fri, Oct 31, 2014 at 3:54 PM, Andrea Del Bene <an.delb...@gmail.com> >> wrote: >> >> You have to add it explicitly with the usual way. This is more desirable >>> if you don't want to apply it to every Ajax behavior as you suggested. >>> >>> @Andrea: how would you share this behavior between ConfirmingAjaxLink >>>> and >>>> ConfirmingAjaxSubmitLink ? >>>> >>>> Martin Grigorov >>>> Wicket Training and Consulting >>>> https://twitter.com/mtgrigorov >>>> >>>> On Fri, Oct 31, 2014 at 2:56 PM, Andrea Del Bene <an.delb...@gmail.com> >>>> wrote: >>>> >>>> you can also use behavior AbstractDefaultAjaxBehavior which has >>>> >>>>> updateAjaxAttributes(AjaxRequestAttributes attributes), so you can >>>>> share >>>>> confirmation code among different components. >>>>> >>>>> Hi, >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>> For additional commands, e-mail: users-h...@wicket.apache.org >>> >>> >>> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >