A couple of questions

trefork · **Joined:** Tue Aug 26, 2003 6:57 pm **Posts:** 3

1. The JavaDocs on SessionFactory.openSession() state that it "Create[s] database connection and open a Session on it. " Does it actually _create_ a connection, or does it use/reuse one from the pool?

2. In a servlet environment, would it be advisable to store a Session in the HttpSession, reconnecting and disconnecting the Connection when needed, instead of close()ing the Session? If not, why not?

3. Any plan to support ConnectionPoolDataSource, like Driver, without using JNDI? This would make connection pooling possible without relying on third party pool implementations.

Thanks,
Nils

christian · **Posted:** Fri Aug 29, 2003 8:20 am

Quote:

1. The JavaDocs on SessionFactory.openSession() state that it "Create[s] database connection and open a Session on it. " Does it actually _create_ a connection, or does it use/reuse one from the pool?

openSession() gets a connection from a configured pool, openSession(connection) re-uses the given connection.

Quote:

2. In a servlet environment, would it be advisable to store a Session in the HttpSession, reconnecting and disconnecting the Connection when needed, instead of close()ing the Session? If not, why not?

This is possible, but not advisable. The acts also as a cache of objects and you may see stale data. It is ok to disconnect/reconnect the Session for a couple of HttpRequest/Response cycles as long as you are aware of the caching issues.