Hi, Am I right in concluding that I must make my wicket session thread-safe?
That is, if I want to store an "int" value in the session, I should use a volatile or AtomicInteger?
Using a debugger I just tested and found that I could get the same instance of my MySession class in two different threads (two different Page classes that do MySession.get()), thus supporting my conclusion that I need to do the thread safety myself and it is not taken care of by Wicket.
Is there anywhere a small piece on how to deal with threading within Wicket (i.e., what is/is not synchronized in a request/response roundtrip?). I did some quick searching in the mailing list archives and google, but could not find anything related to version 1.3.
Regards, Sebastiaan
smime.p7s
Description: S/MIME Cryptographic Signature
