Steve Luke wrote:
A few things to consider:
1) Are you sure the List is serialized and deserialized? How do you know?
2) What does 'launch a new instance of the Wicket application' mean? Is it a new process (if so, then the problem can't be solved in Java, it must be solved with a cross-process resource such as a database).
Hey Steve, thanks for your response.
2) It mean if I have the application running in one tab, and open it under the same session in a new tab.
1) In the documentation it states there is a pageMap class that stores all the current pages for the user in their session. When new tab is opened it basically serializes all the stored pages in the pageMap and then deserializes (Not sure 100% why, but it does).
Wicket has a class (Application class) that allows you to store and share data to all users who access the application. What I was thinking after reading your response is to store my runnable class into a Hashmap or a List of some sort so I can get back in contact with the original runnable object during serialization/deserialization per each user.