Hello,
is it possible that SmartGwt uses org.hibernat.SessionFactory::getCurrentSession() instead of org.hibernat.SessionFactory::openSession()? The reason is, that I use the org.hibernate.context.internal.ManagedSessionContext to provide a Context-Specific HibernateSession. The HibernateSession will be used in a custom DMI-Handler and in some ServletFilters before SmartGwt is invoked.
Now if you use openSession a second HibernateSession will be created, which results in some Exceptions when I use the objects of DSResponse in my own HibernateSession.
Maybe you can make it configurable to switch the desired behaviour.
(I use the evaluation enterprise version 3.1d 2012/10/11)
is it possible that SmartGwt uses org.hibernat.SessionFactory::getCurrentSession() instead of org.hibernat.SessionFactory::openSession()? The reason is, that I use the org.hibernate.context.internal.ManagedSessionContext to provide a Context-Specific HibernateSession. The HibernateSession will be used in a custom DMI-Handler and in some ServletFilters before SmartGwt is invoked.
Now if you use openSession a second HibernateSession will be created, which results in some Exceptions when I use the objects of DSResponse in my own HibernateSession.
Maybe you can make it configurable to switch the desired behaviour.
(I use the evaluation enterprise version 3.1d 2012/10/11)
Comment