sjhyam wrote:
this exception means that you already have an
object with the same identifier loaded in a cache
of a session you are trying to use again and
which hasn't been closed.
I'm not sure what HibernateSessionFactory.getSession()
does under the context you are using it. If it
re-associates your thread to a previously opened Session
then this a logical Exception to get.
A safe way to ensure you don't have duplicate objects
in your Session cache is to either evict the object
from cache or close the session and then use
HibernateSessionFactory.openSession().
mosa