You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently using ISagaEventHandler, if not specified separately, the value of FailureLevels of the HandleAsync method is FailureLevels.Throw, which causes the CancelHandler corresponding to the current Handler to not be executed when an exception occurs in the Handler, but we are more accustomed to thinking that Handler After an exception occurs, the corresponding CancelHandler should be executed
.NET version
.NET 6.0
MASA Framework version
1.0.0-rc.2
The text was updated successfully, but these errors were encountered:
When using ISagaEventHandler, we are unlikely to use the function of Handler orchestration. At this time, only one Handler and one CancelHandler are needed. When the Handler is abnormal, the corresponding CancelHandler will be executed. This is a habit, but if you do not use orchestration, CancelHandler needs to be considered It will not cause data errors due to compensation (the framework itself does not know which step of the Handler execution is wrong), and choosing to use event orchestration is a better choice
Description
Currently using
ISagaEventHandler
, if not specified separately, the value of FailureLevels of theHandleAsync
method isFailureLevels.Throw
, which causes theCancelHandler
corresponding to the current Handler to not be executed when an exception occurs in theHandler
, but we are more accustomed to thinking that Handler After an exception occurs, the correspondingCancelHandler
should be executed.NET version
.NET 6.0
MASA Framework version
1.0.0-rc.2
The text was updated successfully, but these errors were encountered: