Hibernate version:
3
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:
NA
The generated SQL (show_sql=true):
NA
Debug level Hibernate log excerpt:
NA

I am using hibernate within a web application. The requirements state that I must use the users Oracle account when creating a JDBC connection. This of course means I cannot use connection pooling right? So, this also means I must use long running sessions. When the user logs in I create a JDBC connection and assign it to a Hibernate Session. The user will use this session throughout the life of thier application session. Currently we are having problems where user A retrieves data and so this data is loaded into the first level cache. User B does the same thing but edits and saves the changes back to the database. User A then retrieves the data again but the changes user B made are not reflected in the HTML. I think I know but do not know how to solve the problem. The reason user A does not see the changes is becuase the first level cache is stale. How do I update the first level cache? I tried the following but it gave me a null pointer exception..


ret = session.get(class, id)
session.refresh(ret);

I am not sure how to proceed. Is their a better way to handle the sessioning? Or is their a way to refresh the cached entity?

thanks in advance

Reusing a session like that isn't the best idea. A better approach would be to use a user supplied connection. You can do this by defining the following property in your hibernate.cfg.xml:



Then when you go get your new Session:



You can probably package this up nicer with a utility class. But by doing this, you won't have your stale data issue.

Ryan-