[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: transaction scoping
My take is that you should write that your self. It is application
specific and I for one do not want "something" guessing that much about
what my object just tried to do. If I understand your question which I
heard to mean: "How do I implement a transaction based commit or
rollback on the object methods which modify the state of that object and
any it touched" Sounds messy.
You would have to "begin transaction" in ozone, then it would have to
log or track everything. I vote no until such time as Java runs native
most everywhere. By native I mean compiled to machine language object
code like C or C++. By big concern here is of course speed.
Tim
Rob van Oostrum wrote:
> by my understanding, you have to mark all methods that (may) change the
> state of an object. How about methods that change the state of multiple
> objects of different classes? If one of these calls fails, I want to roll
> the whole thing back. From what I gather from the documentation, this isn't
> covered by the current stuff. Has anyone given any thought about how to
> solve this?
>
> cheers
> Rob
>
>
--
Tim Brown
URL: http://www.incenter.org