[eclipselink-users] Eclipselink 1.0.1. transaction bug (?)

[Jan Vissers <Jan.Vissers@xxxxxxxxxx>]

See for initial case:
http://dev.eclipse.org/mhonarc/lists/eclipselink-users/msg01394.html

I've written a JUnit test that shows the following:

Using the setup below:

-begintransaction (early)
stored proc call 1 -> no records committed
stored proc call 2 -> record as initiated by call 1 committed
stored proc call 3 -> record as initiated by call 2 committed
-committransaction -> record as initiated by call 3 committed

What I'm wondering now is whether this is intended behavior, or a bug?

-J.