we're just quibbling over what "stored in the session" means. if we mean (as it seems obvious i did) "is it reachable through the wicket session on the web node and does it take up memory on that node" then yes it is in some sense it is "stored in the (wicket) session" (it's there in the debugger and taking up session-associated resources). if on the other hand we mean (as it's obvious you did) "is it is part of the (container) replicated session, as reconstructed from disk or on other web nodes via serialization" then it's obviously not "stored in the (container) session" because nothing transient can ever be serialized by definition. we were just talking past each other.
Kent Tong wrote: > > > Jonathan Locke wrote: >> >> Your QueryDetachableModel will break under clustering. The transient >> "instance" Object will become null when the container deserializes it and >> your load method will be unable to reload the object. >> >> If you're using these QueryDetachableModels, yes, the object instance is >> being stored in your session. But no, it will not be replicated >> correctly. >> > > Are you sure about that? If the default item reuse strategy is used, new > models and new items will > be created just before the page is rendered. > > In addition, as the object instance is marked as transient, it shouldn't > be stored in the session. > -- View this message in context: http://www.nabble.com/Question-With-Detachable-Models-tf4446686.html#a12697727 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
