Resolution: Won't Fix
Affects Version/s: 1.1
Fix Version/s: None
Thanks to Stelios for bringing up this issue via the discussion thread at google group.
In XAResource implementations for JTA, the methods like "start", "end" can declare to throw an XAException (standard class from JTA) only. But, the XAException class does not provide a constructor which accepts the underlying "casue" for the exception.
Due to that, the underlying root cause gets lost and makes the debugging difficult, as realized in the discussion thread at:
We can workaround this problem by adding logging in our XAResource implementation whenever such XAExceptions are to be thrown; so that the underlying cause for that XAException gets recorded somewhere for diagnosis.