[Tm4j-developers] Transactions and concurrent modification

[Andy P. <an...@il...>]

Hello,

I'm working on integrating use of TM4J and TMAPI into our application.
There's a couple of possible showstoppers though.

Firstly, the Hibernate implementations classes do a commit whenever a
suitable operation has completed, such as when a new topic is created, or an
occurence is added to a topic. What we'd like to do is control the commit
overselves and do it at a higher level. Thus a single transaction may
include multiple topics, associatons, occurences, etc. being created,
updated or deleted.

The other issue is that there doesn't seem to be a way of preventing
modification by more than 1 user at the same time. Using Hibernate's
optimistic lock mechanism would be one option here.

So I guess there's a couple of questions. Firstly, has anybody has to build
workarounds for these before, and secondly, is there any plan to put these
into TM4J?


Andy.