As a user I want to the ability to stop a flow when an error occurs during normal flow processing if the exception is of a specific type

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 3.3.0
  • Fix Version/s: 3.3 M3
  • Component/s: Core: Exception Handling
  • Labels:
    None
  • User impact:
    Medium
  • Similar Issues:
    None

Description

Use cases

Start execution by reading a file inbound endpoint, process it and send it to an HTTP endpoint. In case of a ConnectTimeoutException then stop current flow and notify

Acceptance Criteria

  • An exception strategy can be configured such that when one type of exception (tested with instanceof) matches a flow is stopped.
  • All other exception strategy functionality should be supported alongside this functionality including performing different error path processing based on exception type.

Activity

Ascending order - Click to sort in descending order
Daniel Feist made changes -
Field Original Value New Value
Description *Acceptance Criteria*
- A custom default exception strategy can be configured, it should not have a name.
- If a flow or service is configured without an explicitly defined exception strategy the custom default exception strategy is used.
- The same custom default exception strategy instance is used for all flows and services with no exception strategy explicitly configured. 		*Acceptance Criteria*
- An exception strategy can be configured such that when one type of exception (tested with instanceof) matches a flow is stopped.
- All other exception strategy functionality should be supported alongside this functionality including performing different error path processing based on exception type.
Pablo La Greca made changes -
Description *Acceptance Criteria*
- An exception strategy can be configured such that when one type of exception (tested with instanceof) matches a flow is stopped.
- All other exception strategy functionality should be supported alongside this functionality including performing different error path processing based on exception type. 		*Use cases*

Start execution by reading a file inbound endpoint, process it and send it to an HTTP endpoint. In case of a ConnectTimeoutException then stop current flow and notify

*Acceptance Criteria*
- An exception strategy can be configured such that when one type of exception (tested with instanceof) matches a flow is stopped.
- All other exception strategy functionality should be supported alongside this functionality including performing different error path processing based on exception type.
Ramiro Rinaudo made changes -
Fix Version/s New Backlog [ 11111 ]
Fix Version/s 3.3 M2 [ 11119 ]
Ramiro Rinaudo made changes -
Fix Version/s 3.3 M2 [ 11119 ]
Fix Version/s New Backlog [ 11111 ]
Ramiro Rinaudo made changes -
Fix Version/s New Backlog [ 11111 ]
Fix Version/s 3.3 M3 [ 11124 ]
Alejandro Sequeira made changes -
Priority To be reviewed [ 6 ] Critical [ 2 ]
Affects Version/s 3.3.0 [ 11110 ]
Assignee Pablo La Greca [ pablo.lagreca.ce ]
Alejandro Sequeira made changes -
Resolution Fixed [ 1 ]
Status Open [ 1 ] Closed [ 6 ]

People

  • Assignee:
    Pablo La Greca
    Reporter:
    Daniel Feist
Vote (1)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: