That's the trick: as long as you stay on one page. Then there are no problems with the pattern. My suggestion to put the application transactions in another layer however is when you don't know whether there will be more pages the session is smeared over. And at second thought... no need for session beans anyway, as the Wicket session is a good match for that too.
Eelco > > For me the Wicket pages are the perfect representations for application > transactions - as long as you stay on a page, the Hibernate session is kept > alive (although temporarily disconnected). > > 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 [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
