> 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?
Yes. We try our best to make pages/ components as thread safe as possible, but making the session thread safe would impose a too large performance penalty. > 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. Pages are synced on pagemaps, which basically relates to browser windows. RequestCycles are separate instances which are not reused, so no sync needed there. Sessions are not synced so you need to sync manually. Though in practice this wouldn't give much trouble to start with. Applications are shared an not synced. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
