Mailing-List: contact dev-help@syncope.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@syncope.apache.org
Date: Wed, 7 Sep 2016 09:15:21 +0000 (UTC)
From: "Colm O hEigeartaigh (JIRA)" <jira@apache.org>
To: dev@syncope.apache.org
Message-ID: <JIRA.13002888.1473162571000.506055.1473239721180@Atlassian.JIRA>
In-Reply-To: <JIRA.13002888.1473162571000@Atlassian.JIRA>
References: <JIRA.13002888.1473162571000@Atlassian.JIRA> <JIRA.13002888.1473162571546@arcas>
Subject: [jira] [Commented] (SYNCOPE-931) Error in Camel route causes
 subsequent failures
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 07 Sep 2016 09:15:23 -0000


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

Colm O hEigeartaigh commented on SYNCOPE-931:
---------------------------------------------

The change to the UI with this patch is much better, on editing the route to "update123" you instantly get a notification that it is not valid.

However, there is still another bug lurking here somewhere. With this patch applied, edit the update route to use "update123" as before + try to save. You get an error, so change it back to "update" and save successfully. Now try to create a new user "alice"...it will time out when it should succeed.

> Error in Camel route causes subsequent failures
> -----------------------------------------------
>
>                 Key: SYNCOPE-931
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-931
>             Project: Syncope
>          Issue Type: Bug
>    Affects Versions: 2.0.0.M5
>            Reporter: Colm O hEigeartaigh
>            Assignee: Colm O hEigeartaigh
>             Fix For: 2.0.0
>
>         Attachments: 0001-SYNCOPE-931-Refusing-invalid-route-definition-update.patch
>
>
> Start Syncope with a clean slate + create a new user, and then edit the Camel updateUser script so that it calls the "update123" propagate type instead of "update". Now edit the user + change some attribute. As expected, the update fails.
> Go back into the UI and change the route back to "update" + save. The route appears to have saved normally. However, if you now go back into the user + update some attribute again, it gives the same error message as before.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)