>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
IMHO state is best kept inside the GUI layer. This is exactly what the Spring guys are recommending. Wicket is a stateful component framework, so it is absolutely reasonable to keep the current state of the 'application transaction' (or UnitOfWork, or Conversation as JBoss-Seams calls it) associated with Wicket components. 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 Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
