Uploaded image for project: 'Syncope'
  1. Syncope
  2. SYNCOPE-303

Mapping to SyncopeClientCompositeException on client side

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.2.0-M1
    • Component/s: common, core
    • Labels:
      None

      Description

      Actually almost all exceptions with status BAD_REQUEST and NOT_FOUND are mapped to SyncopeClientCompositeErrorException on the client side.
      It is absolutely OK for composite exceptions containing number of sub-exceptions (like validation and propagation), however for some single exceptions it makes more sense to map not to SyncopeClientCompositeErrorException, but directly to corresponded exception type.
      Candidates are:

      Deadlock
      ExistingResource
      DataIntegrityViolation
      GenericPersistence
      UnauthorizedRole

      Proposed mapping makes exception processing more easy and effective.

      https://cwiki.apache.org/confluence/display/SYNCOPE/Remote+Exceptions

        Attachments

          Activity

            People

            • Assignee:
              ilgrosso Francesco Chicchiriccò
              Reporter:
              ashakirin Andrei Shakirin
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: