That's the pattern I use too. But... it's not the pattern Sven asked for/ refered to, so I was trying to think of options that satisfy his need.
I think - when reading what an 'application transation' means in the article - using statefull session beans is the cleanest approach then, as the Wicket UI is too detached (at least it should be) from the business layer for such an approach. Eelco On 10/7/05, Gili <[EMAIL PROTECTED]> wrote: > > Hmm, excuse me... but it seems to be that you could accomplish exactly > what you are asking for by hooking beginRequest(), endRequest() methods > to open and close your Hibernate session. Hibernate conventions > discourage the use of long-term sessions so this is actually what you > should be doing. Opening a new Session is dirt cheap. > > Gili > ------------------------------------------------------- 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
