Tom Jenkinson [
https://community.jboss.org/people/tomjenkinson] created the discussion
"Re: JTA 1.2 Implementation Work"
To view the discussion, visit:
https://community.jboss.org/message/818520#818520
--------------------------------------------------------------
Paul Robinson wrote:
Mark,
> Mark Little wrote:
>
> What I said was only partially correct. We call end on suspended RMs if delist
hasn't been called. Having this happen for all RMs is easy, but we'd have to be
aware of interface changes and semantic changes, since it is not backwardly compatible
*unless* we have this as a configurable option. Worth considering though, since JTA 1.2
adoption will take a while.
Mike and I have looked over the code, and we think that we already comply to this spec
point. Take a look at the explanation I added to the "Other Spec Changes"
section.
I have taken a look at this too and agree XAResource::end(TMSUCCESS) does
seem to be called in all permutations. I wonder if TMFAIL might be more appropriate for
topLevelAbort? However, I open this as a point of discussion, rather than suggestion. In
practical terms I suspect it won't make any difference to the RM.
Also, your description in "Other Spec Changes" omits the fact that
com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple::rollback(),
endSuspendedRMs() is also invoked. Near as I can work out though, endSuspendedRMs is
almost superflous as topLevel* will end ASSOCIATION_SUSPENDED branches anyway?
--------------------------------------------------------------
Reply to this message by going to Community
[
https://community.jboss.org/message/818520#818520]
Start a new discussion in JBoss Transactions Development at Community
[
https://community.jboss.org/choose-container!input.jspa?contentType=1&...]