TransactionScope Class - Is there an equivalent in JAVA?

[JT]

In .NET I have been using the TransactionScope class to wrap my unit tests
into a transaction and roll back any database changes after I have completed
my unit test. Now I am dealing with some JAVA developers and looking for a
similar way for them to be able to do this from their JAVA code and not at
the database level. Is there and equivalent to this in JAVA? Thanks.

[Jon Skeet [C# MVP]]

JT <[e-mail]:

In .NET I have been using the TransactionScope class to wrap my unit tests
into a transaction and roll back any database changes after I have completed
my unit test. Now I am dealing with some JAVA developers and looking for a
similar way for them to be able to do this from their JAVA code and not at
the database level. Is there and equivalent to this in JAVA? Thanks.

There are various transaction types available in Java (only the stock
ticker is capitalized btw). It depends on which framework you're using.
For instance, Spring provides its own transaction scoping objects, as
does J2EE IIRC.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

[JT]

They want to use EJB3 which I do not know anything about. Thanks.
"Jon Skeet [C# MVP]" <sk***@pobox.comwrote in message
news:MP*********************@msnews.microsoft.com. ..

JT <[e-mail]:

>In .NET I have been using the TransactionScope class to wrap my unit
tests
into a transaction and roll back any database changes after I have
completed
my unit test. Now I am dealing with some JAVA developers and looking for
a
similar way for them to be able to do this from their JAVA code and not
at
the database level. Is there and equivalent to this in JAVA? Thanks.

There are various transaction types available in Java (only the stock
ticker is capitalized btw). It depends on which framework you're using.
For instance, Spring provides its own transaction scoping objects, as
does J2EE IIRC.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

[Jon Skeet [C# MVP]]

JT <[e-mail]:

They want to use EJB3 which I do not know anything about. Thanks.

Okay - there's certainly the concept of transaction scopes within EJB3,
although I can't remember the details. If you show them your .NET code
and explain what it does, they should be able to do a similar thing in
Java.

Personally I don't do that though - I create appropriate conditions in
the unit test database at the start of each test, but don't remove
anything at the end. Each test needs to be able to set itself up
completely. This is less efficient, but does have the advantage that if
a test fails, you can see the state of the database at the point of
failure. It also means you can test code which *does* commit
transactions :)

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too

[=?ISO-8859-1?Q?Arne_Vajh=F8j?=]

Jon Skeet [C# MVP] wrote:

JT <[e-mail]:

>They want to use EJB3 which I do not know anything about. Thanks.

Okay - there's certainly the concept of transaction scopes within EJB3,
although I can't remember the details.

EJB certainly has transactions support, but EJB transactions
stuff (except for BMT) are much more like the stuff in
System.EnterpriseServices.

Arne