As described in the attached thread would be very efficient to combine in the same database transaction operations done by the server side SmartGWT datasource connectors (SQL/JPA,Hibernate) with operations done by an existing service implemented also in SQL/JPA/Hibernate that has its transactions managed by a transaction manager configured using String.
As I know, currently the server side SmartGWT framework has its own transaction manager that cannot be replaced with an external one.
I'll support this from a completely different organization. ;-)
I haven't managed to get my reworked code to this point, but I was going to try to wrap the relevant methods in IDACall with standard Spring transaction advice--does this not work like I hoped it will?