[SCB-1386] Support to send out SagaEnd event in other method

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: pack-0.5.0
• Fix Version/s: pack-0.5.0
• Component/s: Saga
• Assignee: Willem Jiang
• Reporter: José Cardoso
• Created: 19/Jul/19 15:24
• Updated: 22/Aug/19 03:51
• Resolved: 22/Aug/19 03:51

Description

In an async environment (ex: microservices architecture communicating via messaging systems) it is important to control when the saga ends. Therefore, I propose a new annotation - @SagaEnd - to have the possibility to explicitly end the Saga, which will also allow the triggering of the compensation methods in case of failure. 

NOTE from willem
To support the old behavior of SagaStart, we need to add an option to disable sending the Saga end event.
To avoid the aspect class conflict, I didn't introduce @SagaEnd annotation, I just introduced sendingSagaEnd attribute to SagaStart and Compensable this two annotations class to control the SagaEnd event sending.

Issue Links

• is related to: SCB-1425 Docs for @SagaEnd annotation
• links to: GitHub Pull Request #517