the bug was ignoring the return of "false". I thought I fixed this in all cvs versions. Is it still a problem in an up to date jboss?
With JBoss 3.0.4, I am no longer getting the exception thrown during startResource, so that part of my problem has gone away. However, it is still the case that XATxConnectionManager is not testing the return from currentTx.enlistResource(xar) [line 262 in 3.0.4].