syncope-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SYNCOPE-303) Mapping to SyncopeClientCompositeException on client side
Date Mon, 23 Apr 2018 10:04:00 GMT

    [ https://issues.apache.org/jira/browse/SYNCOPE-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16447882#comment-16447882
] 

ASF GitHub Bot commented on SYNCOPE-303:
----------------------------------------

Github user ilgrosso commented on the issue:

    https://github.com/apache/syncope/pull/71
  
    SYNCOPE-303 was created to support this PR.


> 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
>            Assignee: Francesco Chicchiriccò
>            Priority: Major
>             Fix For: 1.2.0-M1
>
>
> 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 was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message