Recovery

[Jesper Pedersen]

Hi,

I have merged support for outbound recovery in commit https://github.com/ironjacamar/ironjacamar/commit/88502139fd37d195343e799eba412735a4025ecd

The recovery implementation follows the IronJacamar 1.x implementation with one exception. Support to use user name and password as part of the configuration has been removed, and must now be supplied through a SubjectFactory instance. This makes the specification requirement in this area more clear, and deployments like data sources can just use DefaultSubjectFactory to convert its user name and password fields to a SubjectFactory instance.

The commit also changes the signature of the deployment repository components to return a boolean for their lifecycle method. This change will allow components such as recovery to be activated and deactivated in a loop during run-time.

In order to implement a test case for recovery the NoopTS implementation has been enhanced to do a single recovery pass during startup.

I'll continue with looking at our new inflow architecture, and include inflow recovery as part of that work.

Feedback, comments, ... is most welcome.

Best regards,
 Jesper

[Jesper Pedersen]

The commit https://github.com/ironjacamar/ironjacamar/commit/1e51fb6f1b79a7c59f074c936bdeab0097de7771 adds support for inflow recovery.

It follows the outbound recovery architecture, just with MessageEndpointFactory and ActivationSpec instead.

This should conclude our XATransaction support :)