[jira] [Updated] (SYNCOPE-403) Enrich PropagationStatusTO to report possible propagation exception message
[ https://issues.apache.org/jira/browse/SYNCOPE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-403: -- Component/s: console Enrich PropagationStatusTO to report possible propagation exception message --- Key: SYNCOPE-403 URL: https://issues.apache.org/jira/browse/SYNCOPE-403 Project: Syncope Issue Type: Improvement Components: common, 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 Attachments: SYNCOPE-403.patch PropagationStatusTO may be enriched with a field reporting possible propagation exception message, so that trace exception returned by a resource and get its specific message. -- 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
[jira] [Updated] (SYNCOPE-403) Enrich PropagationStatusTO to report possible propagation exception message
[ https://issues.apache.org/jira/browse/SYNCOPE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-403: -- Attachment: SYNCOPE-403.patch Enrich PropagationStatusTO to report possible propagation exception message --- Key: SYNCOPE-403 URL: https://issues.apache.org/jira/browse/SYNCOPE-403 Project: Syncope Issue Type: Improvement Components: common, 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 Attachments: SYNCOPE-403.patch PropagationStatusTO may be enriched with a field reporting possible propagation exception message, so that trace exception returned by a resource and get its specific message. -- 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
[jira] [Resolved] (SYNCOPE-403) Enrich PropagationStatusTO to report possible propagation exception message
[ https://issues.apache.org/jira/browse/SYNCOPE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-403. -- Resolution: Fixed http://svn.apache.org/viewvc?view=revisionrevision=r1504872 Thanks Andrea for your contribution. Enrich PropagationStatusTO to report possible propagation exception message --- Key: SYNCOPE-403 URL: https://issues.apache.org/jira/browse/SYNCOPE-403 Project: Syncope Issue Type: Improvement Components: common, 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 Attachments: SYNCOPE-403.patch PropagationStatusTO may be enriched with a field reporting possible propagation exception message, so that trace exception returned by a resource and get its specific message. -- 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
[jira] [Updated] (SYNCOPE-402) Inconsistent status of user edit form after exception returned by bad propagation on primary resource
[ https://issues.apache.org/jira/browse/SYNCOPE-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-402: -- Assignee: Marco Di Sabatino Di Diodoro (was: Andrea Patricelli) 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
