On 10/7/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Storing the hibernate session in my wicket.Session would make it impossible > to have several parallel application transactions going on, e.g. when > operating with multiple browser windows.
What do you do as an alternative? Use stateful session beans? > > I know that you guys are very careful about what methods to expose to us > Wicket users, but perhaps the final on Session#getPage(String,String,int) > could be dropped? > I have to look closer at that. > I'm in need for this for another thing too: > My pages get their dependencies through Spring (utilizing a custom > PageFactory) and hold them in transient members. > When a session (and its pages) gets serialized/deserialized all dependencies > are lost. What I really would like to have is the opportunity to reinject > these dependencies before any code is triggered on this pages. You could do this by customize the serialization. See for instance the bottom of http://java.sun.com/developer/technicalArticles/Programming/serialization/ Eelco ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
