[
https://issues.apache.org/jira/browse/SYNCOPE-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712244#comment-13712244
]
Hudson commented on SYNCOPE-402:
--------------------------------
SUCCESS: Integrated in Syncope-1_1_X #85 (See
[https://builds.apache.org/job/Syncope-1_1_X/85/])
Syncope-402 Removed PropagationException from rest service mapper (mdisabatino:
rev 1504416)
*
/syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/types/SyncopeClientExceptionType.java
*
/syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/rest/utils/RestServiceExceptionMapper.java
* /syncope/branches/1_1_X/core/src/main/webapp/syncopeClientError.jsp
*
/syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java
> Inconsistent status of user edit form after exception returned by bad
> propagation on primary resource
> -----------------------------------------------------------------------------------------------------
>
> Key: SYNCOPE-402
> URL: https://issues.apache.org/jira/browse/SYNCOPE-402
> Project: Syncope
> Issue Type: Improvement
> Components: console, core
> Affects Versions: 1.1.2, 1.1.3
> Reporter: Andrea Patricelli
> Assignee: Marco Di Sabatino Di Diodoro
> Fix For: 1.1.4, 1.2.0
>
>
> During creation (and save) of user to be propagated on a primary resource, if
> propagation fails (due to an error) it returns a propagation exception to
> console and to user edit form, which goes in an inconsistent status and
> stucks.
> A possible solution is to go directly, in case of propagation exception, to
> summary page reporting propagation status on resource(s); in particular
> propagation signaling icon of failure may be abled to show exception message
> caught from PropagationStatusTO.
--
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
