[ https://issues.apache.org/jira/browse/SYNCOPE-931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francesco Chicchiriccò updated SYNCOPE-931: ------------------------------------------- Attachment: SYNCOPE-931.diff 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)