syncope-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francesco Chicchiriccò (JIRA) <j...@apache.org>
Subject [jira] [Comment Edited] (SYNCOPE-931) Error in Camel route causes subsequent failures
Date Wed, 07 Sep 2016 08:17:20 GMT

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

Francesco Chicchiriccò edited comment on SYNCOPE-931 at 9/7/16 8:16 AM:
------------------------------------------------------------------------

I am proposing a different fix for this issue in the attached diff.

Essentially, instead of manually starting the context if it was stopped, I have set things
so that if there is an error when restarting the context after updating a route definition,
the original definition is restored and the effective error message is reported.

As a result, now the route update mechanism should be much more robust against invalid updates.


was (Author: ilgrosso):
I am proposing a different fix for this issue in the attached diff.

Essentially, instead of manually staring the context if it was stopped, I have set things
so that if there is an error when restarting the context after updating a route definition,
the original definition is restored and the effective error message is reported.

As a result, now the route update mechanism should be much more robust against invalid updates.

> 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: SYNCOPE-931.diff
>
>
> 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)

Mime
View raw message