DMI calls and atomicity

[basis.cedric]

Hi,
I am using SmartGWT Power 3.0p and would like to know how to achieve transactional atomicity with DMI calls.
Let's say that I have the following sequence:
1) a call to RPCManager.startQueue()
2) Adding a request in the queue
3) Adding a second request in the queue
4) a call to RPCManager.sendQueue()
The two queued requests will be bind to a DMI method call.
If a problem occurs in the database, i.e. a sql call failure in one request the whole transtaction is rollbacked. But in the case of DMI calls, if an exception occurs in one of the requests, the other requests are commited normally.
How can I achieve atomicity using DMI binding? Is there a particular exception to throw?

Cheers,
Cédric.

[Isomorphic]

Try calling setPartOfTransaction(true) on the DMI DSRequests and let us know if that does the trick - that API is really intended for something else, but it may give the desired effect in your case.