>> 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?
No, IMHO state should be kept in the UI layer. I keep state in wicket components and they are managed beautifully. >>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. IMHO Serialization/deserialization is a bad place to inject dependencies, as this requieres the use of ServiceLocators. Sven ------------------------------------------------------- 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 Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
