>Store youre hibernate session in youre own RequestCycle object then. >(so not in the session)
Well, I want to keep one hibernate session attached to the current thread. That's not different to other standard solutions (session-per-request). But I need to know, which Wicket page is accessed to be able to attach the according hibernate session that's kept in the HTTP session. Perhaps an example explains better what I want to do: Let's think of a wizard like booking user interface, where the customer - enters search criteria - selects an offer out of a list of offers - enters personal information and then books I'd like to use a single-page-wizard approach, described in the wicket wiki. IMHO a single Hibernate session could be associated with this use case. All I need is to be able to disconnect the hibernate session after a request (that's easy) but more importantly reconnect the *according* hibernate session before my code is triggered in one of my components (usually through a component listener). It's just the hook in Wicket that I'm missing. >for Session.getPage() i prefer a call back method to page like >page.wakeUp() Yes, this coudl be sufficient to manage the Hibernate session. But it wouldn't help me with my other problem: re-injecting the Spring dependencies. The page does not know where it can get its dependencies from (IoC). I would rather like a similar method outside the pages, perhaps IPageFactory.wakeUp(Page). Thanks 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
