You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@syncope.apache.org by "Andrei Shakirin (JIRA)" <ji...@apache.org> on 2013/01/31 17:17:13 UTC

[jira] [Created] (SYNCOPE-303) Mapping to SyncopeClientCompositeException on client side

Andrei Shakirin created SYNCOPE-303:
---------------------------------------

             Summary: Mapping to SyncopeClientCompositeException on client side
                 Key: SYNCOPE-303
                 URL: https://issues.apache.org/jira/browse/SYNCOPE-303
             Project: Syncope
          Issue Type: Improvement
          Components: common, core
            Reporter: Andrei Shakirin
             Fix For: 1.2.0


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

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira