[jira] [Updated] (SYNCOPE-931) Error in Camel route causes subsequent failures
[ https://issues.apache.org/jira/browse/SYNCOPE-931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated SYNCOPE-931: Description: 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. was: Start Syncope with a clean slate, and edit the Camel updateUser script so that it calls the "update123" propagate type instead of "update". Save + create a user, and subsequently 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. > 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 > > > 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)
[jira] [Commented] (SYNCOPE-931) Error in Camel route causes subsequent failures
[ https://issues.apache.org/jira/browse/SYNCOPE-931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15467780#comment-15467780 ] ASF subversion and git services commented on SYNCOPE-931: - Commit aa90d840817101847626fed6e1388779d51d631a in syncope's branch refs/heads/master from [~coheigea] [ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=aa90d84 ] SYNCOPE-931 - Restart Camel Context after update > 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 > > > Start Syncope with a clean slate, and edit the Camel updateUser script so > that it calls the "update123" propagate type instead of "update". Save + > create a user, and subsequently 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)
[jira] [Assigned] (SYNCOPE-931) Error in Camel route causes subsequent failures
[ https://issues.apache.org/jira/browse/SYNCOPE-931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh reassigned SYNCOPE-931: --- Assignee: Colm O hEigeartaigh > 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 > > > Start Syncope with a clean slate, and edit the Camel updateUser script so > that it calls the "update123" propagate type instead of "update". Save + > create a user, and subsequently 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)
[jira] [Created] (SYNCOPE-931) Error in Camel route causes subsequent failures
Colm O hEigeartaigh created SYNCOPE-931: --- Summary: 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 Fix For: 2.0.0 Start Syncope with a clean slate, and edit the Camel updateUser script so that it calls the "update123" propagate type instead of "update". Save + create a user, and subsequently 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)
[jira] [Resolved] (SYNCOPE-926) Syncope 2.x startup improvements
[ https://issues.apache.org/jira/browse/SYNCOPE-926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-926. Resolution: Fixed Thanks [~gonzalad] for your contribution: I have also added some specific notes to the reference guide. > Syncope 2.x startup improvements > > > Key: SYNCOPE-926 > URL: https://issues.apache.org/jira/browse/SYNCOPE-926 > Project: Syncope > Issue Type: Improvement > Components: console, core >Affects Versions: 2.0.0-M4 >Reporter: gonzalad >Assignee: Francesco Chicchiriccò > Fix For: 2.0.0 > > > Standalone syncope 2.0.0-M4 startup takes 135s on my laptop. > Most of the time is spent scanning classes in > ClassPathScanImplementationLookup (from core/logic and client/console > modules). > Could the scanning be restricted to some basePackages in order to improve > syncope startup time ? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] syncope issue #36: Startup performance tweaks : restrict startup scanning to...
Github user ilgrosso commented on the issue: https://github.com/apache/syncope/pull/36 Thanks @gonzalad ! I have changed some small details and squashed into a single commit. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] syncope pull request #36: Startup performance tweaks : restrict startup scan...
Github user asfgit closed the pull request at: https://github.com/apache/syncope/pull/36 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
