Oh, I must have missed that part... I did see the part with the ThreadLocal Session... Yes, creating a new Session for each DAO call is a BAD idea. One session per request is the way to go.
> -----Original Message----- > From: James Cook [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 17, 2003 8:42 AM > To: [EMAIL PROTECTED] > Subject: RE: [OS-webwork] hibernate/webwork2 best practices > > > I was replying to his statement that he: > > > currently in my daos i create a session object for every > > dao operation like dao.save dao.load, etc > > I was assuming that he was also doing a flush after each of > these operations. > > -----Original Message----- > From: Jason Carreira > > > This is not how Freeroller was doing things. The problem > > Roller was having was that they were porting from a DAO > > model and every time they wanted to look up anything from > > the database or store anything they would dip into the DAO > > layer, which, with Hibernate, would create a new Session > > and flush it at the end of the DAO call > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
