HornetQ will self register the Recovery Registry on the Transaction Manager, hence we won't support that method.
Once on inFlow the server will register HornetQXAResourceRecovery and that will control recovery...
Maybe we shouldn't throw an Exception there... but we certainly support it. If that's not happening we will take it as a bug.
Clebert is correct, recovery is done via the transaction manager recovery manager, we auto register with it so incoming and outgoing are recovered.
We should either return an empty set of xa resources or if auto recovery is disabled, use one of the incoming sessions to get the ewsources to recover.
Jeff, can you raise a jira and reference this post?
Either empty array - or 'null' as the JCA spec states.