Currently WS-AT subordinate transaction coordinators are only created when a transaction is activated from within an existing WS-AT transaction context. JTA ==> WS-AT bridging needs to be bale to pirate this functionality.
During normal operation the bridge code needs to create and register a WS-AT subordinate coordinator when the bridge is first established. It also needs to be able to obtain a Tx Context for the transaction and to obtain the transaction id so it can log it in recovery records.
At recovery time the bridge code needs to lookup a recovered subordinate transaction coordinator by transaction id. If no coordinator is found it needs to be able to determine whether this is because there is no record in the log or because the log has not been scanned yet. There is no requirement for the bridge code to be able to obtain a transaction context at recovery time.