It's not very process intensive if you are using a connection pool where it just hands you an already-open connection. Hibernate can use a few different connection pools including JCS, C3P0, OSCache, etc.
Regards, David -----Original Message----- From: Riyad Kalla [mailto:[EMAIL PROTECTED] Sent: Monday, June 07, 2004 7:14 PM To: Struts Users Mailing List Subject: OT: Hibernate Session to User Session I was reading in the Hibernate forums that when you have a WebApp > DAO > Hibernate > DB design, and you open/close each Hibernate session at every single DAO method call (what I do now) its actually quite expensive, and is suggested that you attempt to maintain a Hibernate Session in conjunction with a user Session to increase performance. I had a question for anyone that has done this (without using SpringFramework). My gut-reaction to this was to add a HttpSessionListener to my webapp that created and stored a Hibernate session in the user's session, and then close it when the Session expired... will this not work? Anyone else have a good solution for this? TIA, Riyad --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
