Hi Ernesto,
(sorry for the delay in my reply)
No, I don't think so (if I understood your question correctly). The ajax
request is called from the page once loaded, i.e. really after the page's
request cycle.
I can trick by passing a non-detachable-chaining-model to page components
and let the
@Sebastian,
Would a model that only detaches itself if there is no request target
scheduled after current work for your use case?
On Fri, Nov 25, 2016 at 4:00 PM, Sebastien wrote:
> Hi Martin
>
> On Fri, Nov 25, 2016 at 3:52 PM, Martin Grigorov
> wrote:
Hi Martin
On Fri, Nov 25, 2016 at 3:52 PM, Martin Grigorov
wrote:
> Hi Sebastien,
>
> Seems to work as designed! :-)
>
Yes definitely! sorry to have had a doubt! :D
> The Ajax request is in a second request cycle so it loads it again.
> I guess you can create some kind
Hi Sebastien,
Seems to work as designed! :-)
The Ajax request is in a second request cycle so it loads it again.
I guess you can create some kind of ConversationModel (CDI conversations)
but this is totally different model impl.
Martin Grigorov
Wicket Training and Consulting
Hi all,
Following a recent discussion about LDM being reloaded several times [1],
I've prepared a quickstart [2].
My concern was the following: I was thinking that a LDM relying on another
LDM, and reused on several components may have been reloaded several times
(because of the component's