As long as you are not holding references on your own it will be
collected after a replaceWith.
On deleting pages: You could use DefaultPageStore.removePage but I am
not sure if that's a really good idea. Wicket is pretty good in
managing what's in the store and you should rely on its behavior as
Plz help me understand this , as the page is stateful will it keep
references to all the new MyContainer(id)?
clicking on this link creates a new container everytime, if all the
Mycontainer instances are gc collected not a problem but if the instances
are stored it will definetly increase
Hi,
all components not connected to the component tree will be garbage
collected - of course only if you don't collect them in a data structure
by yourself:
There have been people attaching a single behavior to multiple
components, the behavior holding all bound components in a collection
Thanks for your reply, I am assuming if I use component.replacewith will
the old component is replaced with the new componenet and the old is no more
in the component tree so will be gc colected , sure I am not holding any
references top it.
second if I move out of this page to some other
See org.apache.wicket.Component#replaceWith()
On Fri, Jan 11, 2013 at 3:09 AM, fachhoch fachh...@gmail.com wrote:
I have a container with two fragments these fragments are added with some
conditional logic,
if the condition is not satisfied I add empty panel
on ajax update of this
I have A Container I added it to the page constructor using
on ajaxrequest
after the above code will the oldComponent be garbage collected as its no
longer being used?
--
View this message in context:
