CN Yee <yeec...@...> writes: > > I just confirmed that the problem lies with hibernate. > > The following code will persist everything in the session to database. > > Session s = sessionFactory.getCurrentSession(); > Transaction tx = s.beginTransaction(); > tx.commit(); > > That is very nasty. Anybody has any experience to share regarding this? > > Regards, > Yee > I found the following;
"With hibernate it is important to understand what exactly is going on under the covers. At every commit boundary it will attempt to flush all changes to objects in the current session regardless of whether or not the changes where made in the current transaction or any transaction at all for that matter." http://stackoverflow.com/questions/244381/hibernate-transaction-problem I think this pretty confirms that binding to domain model pattern is indeed not tenable for 3 tier architecture. Regards, Yee ------------------------------------------------------------------------------ Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
