Hi, Thanks for your answer. From reading your answer and the one of KB, I have the feeling that the best place to be sure that the pointers get deleted is to follow your suggestion: creation in Page#onConfigure, deletion in Page#onDetach. BUT imagine I have a panel in my page in which I have an Ajax request. Therefore, if I am not mistaken, I would - either have to call the pointers construction again in the Panel#onConfigure, but that would lead to duplicates of the pointers (which I don't want), - either keep the pointers the same as in the Parent page, but then the parent page onDetach would kill them. And hence my Ajax request in the panel would have no access to the pointers, correct?
Following your leads I would then propose to override a LoadableDetachableModel that would generate the pointers in the onAttach and delete them in the onDetach. This would imply many re-creation of the pointers though... In your second suggestion, you provide a way to keep the pointers alive during the Http Session, but this is the case for which we don't know when to delete the pointers, correct? Thanks again -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
