[mpretorian]

Any news on this estimation of implementations?

Also, no answer on the hibernate datasource related question.

[Isomorphic]

This estimate is still ongoing. Sorry, this is not a repeatedly requested feature and usually indicates bad practices, so estimating it as a sponsorship falls behind bugfixes needed for release.

[mpretorian]

What about the hibernate datasource related question?

[Isomorphic]

There is no specific support for Spring-based transaction demarcation in HibernateDataSource. However, there are multiple supported ways for the Configuration and SessionFactory objects to be obtained; possibly one of these would allow your transaction boundary scheme to work.

[mpretorian]

Is that estimation still ongoing?
More than half a year has passed since was started.

I hit again the problem that several existing Services/DAOs implemented either in hibernate or directly with jdbc cannot easily be executed in the same transaction with SQL datasources.

Is this not a feature worth to be implemented in the SmartGWT server framework?

[Isomorphic]

Sorry, this hasn't received any attention because it involves a deep, potentially lengthy investigation of Spring, including the need to write a bunch of test code to try out approaches, ultimately in order to deliver a sponsorship estimate requested by just one user, which might well be declined..

Feature Sponsorship is actually not the best approach to this (sorry we did not say so earlier) - we would suggest switching tactics and using our Consulting service to investigate feasibility and approaches. This may then lead to a Feature Sponsorship if/when a working approach is identified.