The BridgeWrapper for managing subordinate XTS transactions allows for recovery where the id of the tx is known i.e. a log exists in the parent tx. "BridgeWrapper.recreate(String id)". However, it is also necessary to be able to scan for outstanding BridgeWrappers in recovery situations where no parent log exists and the id(s) are therefore unavailable. Furthermore, multiple applications may use the BridgeWrapper and must be able to distinguish which of the recovered instances they are responsible for. As they currently have no control over the structure of the id this is not feasible.

Change BridgeWrapper API to include e.g.
create(String prefix) // each app uses its own prefix so it can filter returned instances by id at recovery time.
recreate(String id) // unchanged
recoveryScan(String prefix) // return all in-doubt instances with matching prefix.