Interesting, the XA scenario which is
more explicit in the text does the opposite.
In the jboss connection manager, we actually create
something called a LocalXAResource
to wrap the local transaction.
This simplifies the code, because we only have to deal
with "XAResources" with suitable warnings when
an attempt is made to use it with other resource
managers in the same transaction.
The CRI is passed to either
before the connection is enlisted in the transaction.