On Tue, Sep 25, 2018, 21:11 Korbinian Bachl
wrote:
> >> and you can use
> >> onRemove()
> >> to free it up as this is called when the component gets removed from the
> >> page / the page itself gets removed;
> >>
> >
> > "the page itself gets removed"
> > I think this is not correct.
> >
>
> As
Dear All,
I have the complex task to develop a webpage GUI for a java/c++ app, i.e.
the java app contains objects that wrap c++ classes of a .so library. For
example the Frame.java class wraps a corresponding c++ class frame.h (which
does the math). Therefore we call in the constructor of the
Hi,
How expensive is to "construct the pointers" ?
If it is not very expensive operation then I'd suggest you to do it in
Page#onConfigure() and to clean up in Page#onDetach().
Those two methods are called for each http request.
If it is expensive then the best I can think of is to store them in
Hi,
take a look at
https://ci.apache.org/projects/wicket/guide/8.x/single.html#_components_lifecycle
You might want to move the code from constructor to
onInitialize()
and you can use
onRemove()
to free it up as this is called when the component gets removed from the page /
the page itself
On Tue, Sep 25, 2018 at 3:35 PM Korbinian Bachl <
korbinian.ba...@whiskyworld.de> wrote:
> Hi,
>
> take a look at
> https://ci.apache.org/projects/wicket/guide/8.x/single.html#_components_lifecycle
>
> You might want to move the code from constructor to
> onInitialize()
>
The benefit of using
>> and you can use
>> onRemove()
>> to free it up as this is called when the component gets removed from the
>> page / the page itself gets removed;
>>
>
> "the page itself gets removed"
> I think this is not correct.
>
As far as I understood all pages go after creation und usage to the page
