[
https://issues.apache.org/jira/browse/SYNCOPE-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò resolved SYNCOPE-303.
--------------------------------------------
Resolution: Fixed
http://svn.apache.org/r1536304
> 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ò
> 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 was sent by Atlassian JIRA
(v6.1#6144)
