That worked like a charm, thank you very much!
On Sun, Apr 5, 2020 at 9:20 PM Sven Meier <s...@meiers.net> wrote:
> Hi,
>
> actually it's not that common, in wicket-core and -extensions this
> pattern is used 9 times only.
>
> When the RequestCycle API emerged, we decided against a specific method
> and chose a generic one with parameter instead.
>
> Have fun
> Sven
>
>
> On 05.04.20 08:47, Vit Rozkovec wrote:
> > Hi, this seems to be a frequent use case, wouldn't there be a good fit
> > for some shorthand method?
> >
> > Like
> >
> > /getRequestCycle().onAjax(t-> {});/
> > boolean getRequestCycle().isAjax();
> >
> > ?
> >
> > Vit
> >
> >
> > On 4/4/20 11:51 PM, Sven Meier wrote:
> >> Hi,
> >>
> >> you can test for the appropriate request handler:
> >>
> >>
> getRequestCycle().find(IPartialPageRequestHandler.class).ifPresent(target
> >> -> /* do things on partial page update */));
> >>
> >> Have fun
> >> Sven
> >>
> >>
> >> On 04.04.20 23:43, Vilius Vaivada wrote:
> >>> Hey guys,
> >>>
> >>> I'm pretty sure I'm missing something obvious here, but I can't
> >>> figure out
> >>> a simple way for a component to contribute slightly different
> >>> Javascript
> >>> based on whether it's being rendered for a full page load or a
> >>> partial Ajax
> >>> response. Any clues?
> >>>
> >>> Thanks a lot!
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> 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
>
>
