Hibernate version:
3.1
Mapping documents:
NA
Code between sessionFactory.openSession() and session.close():
NA
Full stack trace of any exception that occurs:
NA
Name and version of the database you are using:
Oracle 10g
The generated SQL (show_sql=true):
NA
Debug level Hibernate log excerpt:
NA

I need to retrieve a conection based on the user's Oralce id, so no connection pooling. I read the Session classes javadocs on suppling a connection and was wondering if anyone can clarify the following...

Note that the second-level cache will be disabled if you supply a JDBC connection. Hibernate will not be able to track any statements you might have executed in the same transaction. Consider implementing your own ConnectionProvider.

Does this mean hibernate will not track transactions that are creatred outside of the session (using the connection directly) or hibernate will not track transaction at all?

Thanks

I think it's saying if you've already used the connection to issue some other JDBC calls Hibernate will know nothing about them. I can say that this does work. I have a modest application written several years ago that uses user supplied connections and it works just fine.