Thanks for your answer, James. I try to understand magic things. The missing peace in the puzzle was the difference between Hibernates openSession() and getCurrentSession(). More than one transaction within one session seems only to be possible with openSession() and manual flushing and closing. http://www.techfaq360.com/hibernate_interview_questions.jsp?qid=241
This is a pure Hibernate concern, but I want to post an important of the answer to my initial question. The question "What is the current thread, the Hibernate Session is bound to, in a Wicket application?" is still open. ----- Ursprüngliche Mail ---- > Von: James Carman <jcar...@carmanconsulting.com> > An: users@wicket.apache.org > Gesendet: Mittwoch, den 6. Mai 2009, 22:13:09 Uhr > Betreff: Re: Lazy Open Session In View with AOP > > If you use the @Transactional annotation (or define your transactions > in the XML), Spring will take care of the transactions for you > automagically. Thanks, Christian --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
