I'm curious to know how Hibernate's 'current_session_context_class' declaration will disable the Spring's HibernateTransactionManager?
I found that the above two can not exist together for same SessionFactory.
Kindly ley me know what is the role of Spring's HibernateTransactionManager in defining scope for Hibernate's Session context?
What Spring does is it creates an instance of SpringSessionContext which allows you to retrieve the spring managed session for the current thread if it exists. If you want your session factory to be transaction aware this is required. By providing your own value for this property you are overriding this behavior.