#1 Optional transactions

[R. Lemos]

I need to run some tests in which transactions should
be started, commited and rolled back, but these should
be controlled by the test case (well, my test cases
need not only 1 but 3 transactions).

This very simple patch gives the test programmer the
ability to say whether a test case should run in a
transaction environment, using an alternative
constructor. The default behavior is, however, to begin
transactions before setUpEJB, tearDownEJB and the test
methods.

Note that now there is a dependency injection in
EJBTestCase: the associated SessionContext is injected
and is available to the tester.

[R. Lemos]

Well, the patch (cvs diff -u)