Re: Requirements for SYNCOPE-143 the GUI Installer
On 11/06/2013 17:22, Jesal wrote: Dear All, Hoping to help contribute to the project. Setting up a mail on Dev as recommended by Francesco What should be the requirements for the GUI Installer SYNCOPE-143. If we can specify the requirements, hopefully I can start investigating what needs to be done to implement the functionality with a lot of help from all you guys :) Hi Jesal, some thoughts about a GUI installer. 1. Java Swing application enabled to work on a running JEE container for: 1a. configuring JNDI Datasource 1b. deploying Syncope webapps Alternatively, one can think of two web installers instead (one for core and one for console), already deployed on a running JEE container 2. Comes with base syncope.war and syncope-console.war 3. Lets select and install ConnId connector bundles from the Internet This at first glance; any more thoughts? Regards. -- Francesco Chicchiriccò ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~ilgrosso/
Re: Question about syncope/ldap reconciliation .
Il 12/06/2013 10:45, Nik ha scritto: Cheers Fabio, I have not enabled synchronization (by using my ldap changelog) because I believed reconciliation took care of making ALL changes from the target DB (ldap) to my syncope DB. If what you say is correct. If I delete an object directly in ldap, then after a full reconciliation task executes subsequently the delete(d) object(s) is not deleted from the syncope DB, but the link to the ldap account is? Hence, all ldap modifications of type DELETE are not reflected in syncope unless you use the synchronization method with a changelog? Exactly, no changes will be reflected on syncope in case of delete operation. ... but ... this topic can suggest an improvement on syncope: maybe we can implement a full reconciliation from syncope towards a certain resource. In this case we could implement several different/configurable behaviors in case of unmatching (user found on syncope but not on the resource): * ignore; * unlink the resource (keep user on syncope and remove resource link) * create (create user on resource) * remove (remove user on syncope) I will propose this issue on jira asap. So, I can suggest to you three different options: 1. active the changelog; 2. implement your own generic task to perform what described above; 3. take care of the issue I'm going to open. I guessing the only way you can synchronize deletes at the moment, is because the changelog is the only way syncope can know about them explicitly and efficiently. Another, way you could work out what was deleted (between full recons) is the delta between the syncope entries with ldap account links (before the full recon) and those after, the full recon, which don't show these links anymore as valid and then remove these entries from the syncope db. May be but I prefer a second full recon, from syncope to the resource. Perhaps we can still have option to activate/deactivate create/update/delete triggering (like done for sync from resource to sync). Regards, F. rgds, Nik Il 11/06/2013 17:47, Nik ha scritto: Hi Guys, I have recently seen a comment on this alias that reconciliation doesn't take care of deletions. I would like to have a clear idea of what this means. Does it mean; if I delete an ldap object (e.g. user) from my ldap resource by ldap delete this deletion would not be reconciled back to syncope? Reading such comments, confuses me, because if I delete an object in syncope and this object is linked by an ldap connector resource to ldap. The deletion via the ldap resource should be propagated to the ldap backend, in such a case, reconciliation of the deletion is meaningless, since the syncope and ldap remain synchronized. Hi Nik, * reconciliation reconcile create/update/delete operation * full reconciliation reconcile create/update (it is just a exhaustive user search/read). Use full reconciliation at pre-loading time or if and only if the target resource doesn't provide changelog feature; use sync/reconciliaion otherwise. Best regards, F.
Re: Problems running CXF Tests
On 11/06/2013 12:04, Jan Bernhardt wrote: Can someone confirm these test issues, or is it just me? Can you try with the different build profiles reported above? I did as suggested and my test results are: * 2 Errors and 3 Failures for the first run * 14 Errors and 6 Failures for the second run Hi Jan, I don't have Eclipse, but I've tested whether IT can be re-run safely this way: 1. modified core/src/test/resources/persistence.properties by setting jpa.url=jdbc:h2:syncopedb;DB_CLOSE_DELAY=-1 (this will use non-volatile H2 db for tests) 2. run mvn -Pjaxrs from core directory twice, got no errors Regards. -- Francesco Chicchiriccò ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~ilgrosso/
Re: [VOTE] Apache Syncope 1.1.2
Il giorno 11/giu/2013, alle ore 16:24, Marco Di Sabatino Di Diodoro marco.disabat...@tirasa.net ha scritto: I've created a 1.1.2 release, with the following artifacts up for a vote: SVN source tag (r1491807): https://svn.apache.org/repos/asf/syncope/tags/syncope-1.1.2/ List of changes: https://svn.apache.org/repos/asf/syncope/tags/syncope-1.1.2/CHANGES Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-011/ Source release (checksums and signatures are available at the same location): https://repository.apache.org/content/repositories/orgapachesyncope-011/org/apache/syncope/syncope/1.1.2/syncope-1.1.2-source-release.zip Staging site: http://syncope.apache.org/1.1.2/ PGP release keys (signed using 293412BA): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. +1 Marco [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Dott. Marco Di Sabatino Di Diodoro Tel. +39 3939065570 Tirasa S.r.l. Viale D'Annunzio 267 - 65127 Pescara Tel +39 0859116307 / FAX +39 085973 http://www.tirasa.net Apache Syncope PMC Member http://people.apache.org/~mdisabatino -- Dott. Marco Di Sabatino Di Diodoro Tel. +39 3939065570 Tirasa S.r.l. Viale D'Annunzio 267 - 65127 Pescara Tel +39 0859116307 / FAX +39 085973 http://www.tirasa.net Apache Syncope PMC Member http://people.apache.org/~mdisabatino
Re: [VOTE] Apache Syncope 1.1.2
+1. Colm. On Wed, Jun 12, 2013 at 12:50 PM, Marco Di Sabatino Di Diodoro marco.disabat...@tirasa.net wrote: Il giorno 11/giu/2013, alle ore 16:24, Marco Di Sabatino Di Diodoro marco.disabat...@tirasa.net ha scritto: I've created a 1.1.2 release, with the following artifacts up for a vote: SVN source tag (r1491807): https://svn.apache.org/repos/asf/syncope/tags/syncope-1.1.2/ List of changes: https://svn.apache.org/repos/asf/syncope/tags/syncope-1.1.2/CHANGES Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-011/ Source release (checksums and signatures are available at the same location): https://repository.apache.org/content/repositories/orgapachesyncope-011/org/apache/syncope/syncope/1.1.2/syncope-1.1.2-source-release.zip Staging site: http://syncope.apache.org/1.1.2/ PGP release keys (signed using 293412BA): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. +1 Marco [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Dott. Marco Di Sabatino Di Diodoro Tel. +39 3939065570 Tirasa S.r.l. Viale D'Annunzio 267 - 65127 Pescara Tel +39 0859116307 / FAX +39 085973 http://www.tirasa.net Apache Syncope PMC Member http://people.apache.org/~mdisabatino -- Dott. Marco Di Sabatino Di Diodoro Tel. +39 3939065570 Tirasa S.r.l. Viale D'Annunzio 267 - 65127 Pescara Tel +39 0859116307 / FAX +39 085973 http://www.tirasa.net Apache Syncope PMC Member http://people.apache.org/~mdisabatino -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
Re: [VOTE] Apache Syncope 1.1.2
+1 Regards JB -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://wwx.talend.com - Reply message - From: Jan Bernhardt jbernha...@talend.com To: dev@syncope.apache.org dev@syncope.apache.org Subject: [VOTE] Apache Syncope 1.1.2 Date: Wed, Jun 12, 2013 7:30 am +1 Best regards. Jan -Original Message- From: Marco Di Sabatino Di Diodoro [mailto:marco.disabat...@tirasa.net] Sent: Dienstag, 11. Juni 2013 16:25 To: dev@syncope.apache.org Subject: [VOTE] Apache Syncope 1.1.2 I've created a 1.1.2 release, with the following artifacts up for a vote: SVN source tag (r1491807): https://svn.apache.org/repos/asf/syncope/tags/syncope-1.1.2/ List of changes: https://svn.apache.org/repos/asf/syncope/tags/syncope-1.1.2/CHANGES Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-011/ Source release (checksums and signatures are available at the same location): https://repository.apache.org/content/repositories/orgapachesyncope- 011/org/apache/syncope/syncope/1.1.2/syncope-1.1.2-source-release.zip Staging site: http://syncope.apache.org/1.1.2/ PGP release keys (signed using 293412BA): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Dott. Marco Di Sabatino Di Diodoro Tel. +39 3939065570 Tirasa S.r.l. Viale D'Annunzio 267 - 65127 Pescara Tel +39 0859116307 / FAX +39 085973 http://www.tirasa.net Apache Syncope PMC Member http://people.apache.org/~mdisabatino
[jira] [Resolved] (SYNCOPE-394) Scheduled tasks are execute without transaction support
[ https://issues.apache.org/jira/browse/SYNCOPE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-394. Resolution: Fixed 1_1_X: http://svn.apache.org/r1492210 http://svn.apache.org/r1492216 trunk: http://svn.apache.org/r1492217 Scheduled tasks are execute without transaction support --- Key: SYNCOPE-394 URL: https://issues.apache.org/jira/browse/SYNCOPE-394 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.2 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.3, 1.2.0 Any class extending AbstractTaskJob cannot operate with transaction support because there is no method annotated as @Transactional -- 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] [Commented] (SYNCOPE-394) Scheduled tasks are execute without transaction support
[ https://issues.apache.org/jira/browse/SYNCOPE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681275#comment-13681275 ] Hudson commented on SYNCOPE-394: Integrated in Syncope-1_1_X #67 (See [https://builds.apache.org/job/Syncope-1_1_X/67/]) [SYNCOPE-394] Adding new AbstractTransactionalTaskJob class for jobs needing to execute in transaction (Revision 1492210) Result = SUCCESS ilgrosso : Files : * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/init/ImplementationClassNamesLoader.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/init/JobInstanceLoader.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/quartz/AbstractTaskJob.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/quartz/AbstractTransactionalTaskJob.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/quartz/SampleJob.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/quartz/TaskJob.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/rest/controller/TaskController.java Scheduled tasks are execute without transaction support --- Key: SYNCOPE-394 URL: https://issues.apache.org/jira/browse/SYNCOPE-394 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.2 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.3, 1.2.0 Any class extending AbstractTaskJob cannot operate with transaction support because there is no method annotated as @Transactional -- 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] [Commented] (SYNCOPE-394) Scheduled tasks are execute without transaction support
[ https://issues.apache.org/jira/browse/SYNCOPE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681326#comment-13681326 ] Hudson commented on SYNCOPE-394: Integrated in Syncope-trunk #237 (See [https://builds.apache.org/job/Syncope-trunk/237/]) [SYNCOPE-394] Merge from 1_1_X (Revision 1492217) Result = SUCCESS ilgrosso : Files : * /syncope/trunk/core/src/main/java/org/apache/syncope/core/init/ImplementationClassNamesLoader.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/init/JobInstanceLoader.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/quartz/AbstractTaskJob.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/quartz/AbstractTransactionalTaskJob.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/quartz/SampleJob.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/quartz/TaskJob.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/TaskController.java Scheduled tasks are execute without transaction support --- Key: SYNCOPE-394 URL: https://issues.apache.org/jira/browse/SYNCOPE-394 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.2 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.3, 1.2.0 Any class extending AbstractTaskJob cannot operate with transaction support because there is no method annotated as @Transactional -- 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
