[Bug 229] Registration Service recovery and failure

[bugzilla-daemon@arjuna.com]

http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=229





------- Additional Comments From mark.little@arjuna.com  2005-02-17 12:28 -------
Discussion: Tony would prefer additional operations which allow redirection
of further messages intended for each service.  A single interface at each
service; nothing new at that level to support redirection.  Recovery
Coordinator would use these messages to take over for Registration Service.
Current approach uses a separate interface (Recovery service) for the
"ChangeMe" portion of the Registration service life cycle.

Doug makes motion: Remove Recovery Coordinator and all mentions of it from
the specification.  In doing so, consolidate its current interface with
that of the Registration Service.

Martin seconds

Discussion: Doug notes that Participant recovery becomes a specific use
case for the (more general) redirection operations on the Registration
Service.  Eric does not think this breaks anything but may not fix anything
either.

Passed without objection

Above motion resolved opposite of the original issue, covers failure of a
participant.

Tony makes motion: Add Registering Service operations to support changing
the Registration Service EPRs.  The specification should contain no
requirement for the Registration Service to invoke these operations.

Martin seconds

Discussion: This new set of operations would support recovery of the
Registration Service after its failure as one use case.

Mark makes amendment adding second sentence shown above.  Passed without
objection.

Motion passed without objection



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.