On 11 Oct 00, at 13:00, Daniel Schulze wrote:

> Two possible ways to solve it:
> 1. bring the transaction stuff into the jaws code and use two
> transactions for this operation (reuse the old code)
> 
There is nothing wrong with this, in my opinion. In general, 
persistence code needs to be able to have some control over the 
transactional context in which it accesses a resouce (e.g. for 
optimistic concurrency).

-Dan


Reply via email to