Uploaded image for project: '[Read Only] - Hippo Repository'
  1. [Read Only] - Hippo Repository
  2. REPO-874

Provide a wrapper for SCXMLExecutor to handle possible execution exceptions and errors

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: High
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.26.00-alpha-1, 2.26.00
    • Component/s: None
    • Labels:
    • Similar issues:

      Description

      SCXMLExecutor currently doesn't handle runtime exceptions which might be thrown during the execution of specific SCXML tasks, actions or otherwise.
      Exception to this is the handling of SCXMLExpressionException but any other exception during execution simply falls out of the SCXMLExecutor.

      In addition, if any error (or catched SCXMLExpressionException) is encountered, this is logged through the ErrorReporter, however there is no (provided) way to detect such errors afterwards.
      To be sure the SCXML execution ran through without errors, some kind of extended/intercepted handling of the ErrorReporter must be provided, which records such errors so that afterwards they (or at least the first) can be accessed and further processing be done on.

      The proposed SCXMLExecutor wrapper should catch any exception from the underlying SCXMLExecutor, and at least mark its state to something like invalidState which can be 'queried' afterwards.
      In addition, for all the #go, #reset, #triggerEvent and #triggerEvents methods, convenient boolean #tryGo, #tryReset, etc. methods should be provided which do not throw any exception but return true if no Exception AND no Error occurred.
      In case these #try methods return false, a #getExecutionException() and #getExecutionError() (first error) method can be used to retrieve them.

      Note: the wrapper does not / should not extend SCXMLExecutor itself, but merely provide a wrapper as well as still provide access to the underlying SCXMLExecutor (#getSCXMLExecutor) so its other methods like #getCurrentStatus() etc. still can be accessed without duplicating these on the wrapper class.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              adouma Ate Douma
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: