Hi,
Peter Braswell wrote:
> Since I'm creating a test suite, one aspect of this
> testing is to test the ability for client controlled
> transactions, so while I appreciate the work around
> suggestion, what I really want is to test the former.
>
> Another thread has mentioned that the transaction
> context being available to the client has not been
> implemented yet??? Thanks Peter Jasko
>
> So can anybody out there verify this??
Don't know if it can count as verification, since I
was the one saying UserTransaction for client use
is not yet implemented in JBoss.
But since I know the JBoss transaction code well
(currently working on these issues), here goes:
The only UserTransaction currently implemented in
JBoss is a special implementation for the use of
BMT beans only.
Currently the JBoss transaction system does not have
the networking code needed for real (inter-VM)
distributed transactions implemented. Within the same
VM transactions work like they should, but if you try
to call a bean in another JBoss container in another
VM with a transactional context, you will receive a
message stating that the transaction cannot be
imported.
While implementing a client UserTransaction that
would work if the client is in the same VM as JBoss
is rather simple, most clients are in different VMs.
So inter-VM transaction context propagation _is_
needed.
But when inter-VM transaction context propagation is
implemented, these distribution aspects make it
simple to implement a light-weight UserTransaction
for client use so that the client does not need a
complete transaction management system.
Hope this clarifies.
Best Regards,
Ole Husgaard.
