msrp
  1. msrp
  2. MSRP-50

Aborting a message that's already been sent is not an error.

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: beta
    • Fix Version/s: 1.0.4
    • Component/s: None
    • Labels:
      None
    • Environment:

      Any.

      Description

      When a message has been sent and the receiver has a problem parsing, a 400 response can result.
      This leads to an abort of the outgoing message where a sanity check throws an exception when the outgoing message was already completed.

      Given the use-case, this is perfectly normal though. The exception shouldn't be thrown.

        Activity

        Hide
        uijltje added a comment -

        Refer to svn r184:

        • removed isComplete() check from OutgoingMessage.abort().
        • Some refactored code (simplification).
        Show
        uijltje added a comment - Refer to svn r184: removed isComplete() check from OutgoingMessage.abort() . Some refactored code (simplification).

          People

          • Assignee:
            uijltje
            Reporter:
            uijltje
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 2 hours
              2h
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 2 hours
              2h