Seems a good idea, but it's also nice if we can keep the testsuite
quick to run; would it make sense to still have the DummyTM as an
option for those tests which only need the most trivial TM?
I'm expecting the JBossTM is slower, but I really don't know.
Sanne
2011/1/24 Mircea Markus <mircea.markus(a)jboss.com>:
Hi,
Right now we are running our test suite using DummyTM.
This is mainly for suppling users with a default, lightweight TM. And avoid
a additional dependency.
Even though this worked well for us so far, this might not be such a good
idea after all: there are many not-so-obvious rules to be considered when
implementing such a transaction manager which, if not implemented might
make our XAResource implementation work badly even though it works fine(eg
[1]). Or even worse, it might make it look okay even though it doesn't.
On top of that there are grey areas in JTA spec, for which different
vendors use different approaches. By using/testing against JBossTM we can
document these usages and stick with (the recommended?) JBossTM
functionality.
Taking this one step further, wondering weather it makes sense to keep the
DummyTM as it is in our code base, given the fact that it is far away from
implementing the spec. One solution would be to enhance it (-1 IMO), another
to replace it. Perhaps with a lightweight JBossTM?
Cheers,
Mircea
[
1] http://lists.jboss.org/pipermail/infinispan-dev/2011-January/007243.html
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev