[jira] [Commented] (SYNCOPE-259) Create transitional Service interfaces and switch tests and console to use them
[ https://issues.apache.org/jira/browse/SYNCOPE-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13553611#comment-13553611 ] Hudson commented on SYNCOPE-259: Integrated in Syncope-trunk #431 (See [https://builds.apache.org/job/Syncope-trunk/431/]) [SYNCOPE-259] Replacing ClassT method parameters with matching Enum types. (Revision 1433313) Result = SUCCESS jbernhardt : Files : * /syncope/trunk/client/src/main/java/org/apache/syncope/services/PolicyService.java * /syncope/trunk/client/src/main/java/org/apache/syncope/services/ResourceService.java * /syncope/trunk/client/src/main/java/org/apache/syncope/services/RoleService.java * /syncope/trunk/client/src/main/java/org/apache/syncope/services/SchemaService.java * /syncope/trunk/client/src/main/java/org/apache/syncope/services/TaskService.java * /syncope/trunk/client/src/main/java/org/apache/syncope/services/proxy/ConfigurationServiceProxy.java * /syncope/trunk/client/src/main/java/org/apache/syncope/services/proxy/ConnectorServiceProxy.java * /syncope/trunk/client/src/main/java/org/apache/syncope/services/proxy/EntitlementServiceProxy.java * /syncope/trunk/client/src/main/java/org/apache/syncope/services/proxy/LoggerServiceProxy.java * /syncope/trunk/client/src/main/java/org/apache/syncope/services/proxy/NotificationServiceProxy.java * /syncope/trunk/client/src/main/java/org/apache/syncope/services/proxy/PolicyServiceProxy.java * /syncope/trunk/client/src/main/java/org/apache/syncope/services/proxy/ReportServiceProxy.java * /syncope/trunk/client/src/main/java/org/apache/syncope/services/proxy/ResourceServiceProxy.java * /syncope/trunk/client/src/main/java/org/apache/syncope/services/proxy/RoleServiceProxy.java * /syncope/trunk/client/src/main/java/org/apache/syncope/services/proxy/SchemaServiceProxy.java * /syncope/trunk/client/src/main/java/org/apache/syncope/services/proxy/SpringRestTemplate.java * /syncope/trunk/client/src/main/java/org/apache/syncope/services/proxy/SpringServiceProxy.java * /syncope/trunk/client/src/main/java/org/apache/syncope/services/proxy/TaskServiceProxy.java * /syncope/trunk/client/src/main/java/org/apache/syncope/services/proxy/UserRequestServiceProxy.java * /syncope/trunk/client/src/main/java/org/apache/syncope/services/proxy/UserServiceProxy.java * /syncope/trunk/client/src/main/java/org/apache/syncope/services/proxy/WorkflowServiceProxy.java * /syncope/trunk/client/src/main/java/org/apache/syncope/types/AttributableType.java * /syncope/trunk/client/src/main/java/org/apache/syncope/types/TaskType.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/AbstractTest.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/AuthenticationTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/DerivedSchemaTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/PolicyTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/SchemaTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/TaskTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/VirtualSchemaTestITCase.java Create transitional Service interfaces and switch tests and console to use them --- Key: SYNCOPE-259 URL: https://issues.apache.org/jira/browse/SYNCOPE-259 Project: Syncope Issue Type: Improvement Components: client, console, core Affects Versions: 1.1.0 Reporter: Christian Schneider Assignee: Jan Bernhardt Fix For: 1.1.0 Attachments: PolicyService.patch, ResourceService-1428511.patch, ResourceService.patch, SYNCOPE-259.patch As preparation of the change to use CXF instead of Spring MVC REST controllers this issue is to introduce transitional service interfaces (like as UserService). The UserService interface should later be used in the core to provide the UserController and on the console to access the service remotely. To make the transition easier the idea is to already introduce the interface upfront and change all tests and the console to use it. Before the switch the implementation of the interface will simply use the restTemplate under the covers. This to be applied similarly to all Spring MVC REST controllers. -- 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-268) Enable Rest IntegrationTests to run more than once (per build)
[
https://issues.apache.org/jira/browse/SYNCOPE-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13553640#comment-13553640
]
Hudson commented on SYNCOPE-268:
Integrated in Syncope-trunk #432 (See
[https://builds.apache.org/job/Syncope-trunk/432/])
[SYNCOPE-268] Make rest integration tests re-runnable (Revision 1433327)
Result = SUCCESS
ashakirin :
Files :
*
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/NotificationTestITCase.java
*
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/RoleTestITCase.java
*
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/SchemaTestITCase.java
*
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/UserRequestTestITCase.java
Enable Rest IntegrationTests to run more than once (per build)
--
Key: SYNCOPE-268
URL: https://issues.apache.org/jira/browse/SYNCOPE-268
Project: Syncope
Issue Type: Improvement
Components: core
Reporter: Jan Bernhardt
Assignee: Jan Bernhardt
Labels: test
Fix For: 1.1.0
Attachments: RerunnableRestIntegrationTests-1.patch,
RerunnableRestIntegrationTests-2.patch
Currently many Rest IntegrationTests can run only once. If you try to rerun
some Tests they will fail, due to the fact, that a resource with the same
same already exists, or that a resource was deleted previously and is not
available any longer. This works fine for mvn clean verify since all test
run exactly once. But for development phase this is inconvenient, because
while testing new features or other refactorings, one would like to run tests
several times (especially if they fail), without the need to
rebuild/package/deploy the whole core module.
Tasks of this JIRA ticket is to use random identifier for resources (user,
role, ...) to avoid collisions, when running tests multiple times. In some
cases it will also be preferable to use a try { } final { } statement to
cleanup previously created resources.
--
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] [Created] (SYNCOPE-274) Sync: during update with user template existing memberships break update
Marco Di Sabatino Di Diodoro created SYNCOPE-274: Summary: Sync: during update with user template existing memberships break update Key: SYNCOPE-274 URL: https://issues.apache.org/jira/browse/SYNCOPE-274 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.0.4 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.0.5, 1.1.0 Suppose user A has membership (ID=100) for role R. During synchronization from an external resource, if A is picked up for update and an user template is configured with membership for role R, the ongoing transaction breaks with error AttributableTO's id must be the same -- 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-274) Sync: during update with user template existing memberships break update
[ https://issues.apache.org/jira/browse/SYNCOPE-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13553703#comment-13553703 ] Marco Di Sabatino Di Diodoro commented on SYNCOPE-274: -- Fix for branch 1_0_X http://svn.apache.org/viewvc?rev=1433361view=rev Sync: during update with user template existing memberships break update Key: SYNCOPE-274 URL: https://issues.apache.org/jira/browse/SYNCOPE-274 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.0.4 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.0.5, 1.1.0 Suppose user A has membership (ID=100) for role R. During synchronization from an external resource, if A is picked up for update and an user template is configured with membership for role R, the ongoing transaction breaks with error AttributableTO's id must be the same -- 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-241) Move persistence and persistence impl into separate modules
[ https://issues.apache.org/jira/browse/SYNCOPE-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13553717#comment-13553717 ] Christian Schneider commented on SYNCOPE-241: - I am currently struggling with actually moving the perisistence into a separate module. The classes and test spring contexts are separated nicely now but the pom.xml changes a lot using ant and I have no idea how to move this part without duplicating a lot of the test resources. Move persistence and persistence impl into separate modules --- Key: SYNCOPE-241 URL: https://issues.apache.org/jira/browse/SYNCOPE-241 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 1.0.3-incubating Reporter: Christian Schneider Fix For: 1.1.0 Attachments: SYNCOPE-241-2.patch, SYNCOPE-241-3.patch, SYNCOPE-241-4.patch, SYNCOPE-241-5.patch, SYNCOPE-241.patch The core module currently contains many parts of syncope. This makes it bigger and more complex than necessary. A possible modularization is to move the internal model (org.apache.syncope.core.persistence*) and the persistence impl (org.apache.syncope.core.persistence.impl) out of core and into separate modules. One big advantage would be that the jpa code enhancements would then run in the model module only. Currently we run into some problems in the cxf migration when running the rest itests in core that may be caused by eclipse overwriting the enhanced classes with plain classes. If the model (peristence) classes are in a separate module we could leave it out of eclipse and so this would be no issue anymore. Another advantage would be that the persistence tests could run in the persistence impl module so when working on the core they would not have to run each time. -- 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
Change console admin password and related documentation
Hi, I was trying to update default console password. I was able to update it just modifing the adminMD5Password property value in syncope/WEB-INF/classes/security.properties file. I was looking for documentation and at the moment it'seams there is not a procedure described. I would like to open a issuse to update [1] and [2]. Following the same approach used in [3] (to setup AES encryption key), I think it should be a valid improvement letting the user to choose the initial admin console password in archetype generation as well. WDYT? Regards. Denis [1] - https://cwiki.apache.org/confluence/display/SYNCOPE/Run+Syncope+in+real+environments#RunSyncopeinrealenvironments-Testyourinstallation [2] - https://cwiki.apache.org/confluence/display/SYNCOPE/Using+administration+console [3] - https://issues.apache.org/jira/browse/SYNCOPE-269
[jira] [Commented] (SYNCOPE-274) Sync: during update with user template existing memberships break update
[ https://issues.apache.org/jira/browse/SYNCOPE-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13553733#comment-13553733 ] Hudson commented on SYNCOPE-274: Integrated in Syncope-1_0_X #104 (See [https://builds.apache.org/job/Syncope-1_0_X/104/]) SYNCOPE-274 Fix Update Sync task for memberships (Revision 1433361) Result = SUCCESS mdisabatino : Files : * /syncope/branches/1_0_X/core/src/main/java/org/apache/syncope/core/util/ConnObjectUtil.java Sync: during update with user template existing memberships break update Key: SYNCOPE-274 URL: https://issues.apache.org/jira/browse/SYNCOPE-274 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.0.4 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.0.5, 1.1.0 Suppose user A has membership (ID=100) for role R. During synchronization from an external resource, if A is picked up for update and an user template is configured with membership for role R, the ongoing transaction breaks with error AttributableTO's id must be the same -- 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-274) Sync: during update with user template existing memberships break update
[ https://issues.apache.org/jira/browse/SYNCOPE-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13553805#comment-13553805 ] Hudson commented on SYNCOPE-274: Integrated in Syncope-trunk #433 (See [https://builds.apache.org/job/Syncope-trunk/433/]) SYNCOPE-274 Merge from 1_0_X (Revision 1433381) Result = SUCCESS mdisabatino : Files : * /syncope/trunk * /syncope/trunk/core/src/main/java/org/apache/syncope/core/connid/ConnObjectUtil.java Sync: during update with user template existing memberships break update Key: SYNCOPE-274 URL: https://issues.apache.org/jira/browse/SYNCOPE-274 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.0.4 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.0.5, 1.1.0 Suppose user A has membership (ID=100) for role R. During synchronization from an external resource, if A is picked up for update and an user template is configured with membership for role R, the ongoing transaction breaks with error AttributableTO's id must be the same -- 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-259) Create transitional Service interfaces and switch tests and console to use them
[ https://issues.apache.org/jira/browse/SYNCOPE-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13553819#comment-13553819 ] Hudson commented on SYNCOPE-259: Integrated in Syncope-trunk #434 (See [https://builds.apache.org/job/Syncope-trunk/434/]) [SYNCOPE-259] Fixed policy service list method. (Revision 1433389) Result = SUCCESS ashakirin : Files : * /syncope/trunk/client/src/main/java/org/apache/syncope/services/proxy/PolicyServiceProxy.java * /syncope/trunk/client/src/main/java/org/apache/syncope/services/proxy/TaskServiceProxy.java Create transitional Service interfaces and switch tests and console to use them --- Key: SYNCOPE-259 URL: https://issues.apache.org/jira/browse/SYNCOPE-259 Project: Syncope Issue Type: Improvement Components: client, console, core Affects Versions: 1.1.0 Reporter: Christian Schneider Assignee: Jan Bernhardt Fix For: 1.1.0 Attachments: PolicyService.patch, ResourceService-1428511.patch, ResourceService.patch, SYNCOPE-259.patch As preparation of the change to use CXF instead of Spring MVC REST controllers this issue is to introduce transitional service interfaces (like as UserService). The UserService interface should later be used in the core to provide the UserController and on the console to access the service remotely. To make the transition easier the idea is to already introduce the interface upfront and change all tests and the console to use it. Before the switch the implementation of the interface will simply use the restTemplate under the covers. This to be applied similarly to all Spring MVC REST controllers. -- 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] [Updated] (SYNCOPE-241) Move persistence and persistence impl into separate modules
[ https://issues.apache.org/jira/browse/SYNCOPE-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider updated SYNCOPE-241: Attachment: SYNCOPE-241-6.patch I have given up to move the persistence tests into the persistence module for now. It is too difficult to do with our current build without creating a lot of duplicated pom content and resources. On the other hand I succeeded in moving at least the production persistence classes into a separate persistence module. There are at least two advantage compared to the current state: - It is impossible to accidently create new dependencies from persistence classes to other parts of core. So persistence is guaranteed to be a inner core of syncope that can be understood on its own - The jpa enhancement happens in persistence. So when you work at core you can leave the persistence project closed and this way eclipse will not accidently overwrite the enhanced classes with the original classes and make your tests fail Move persistence and persistence impl into separate modules --- Key: SYNCOPE-241 URL: https://issues.apache.org/jira/browse/SYNCOPE-241 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 1.0.3-incubating Reporter: Christian Schneider Fix For: 1.1.0 Attachments: SYNCOPE-241-2.patch, SYNCOPE-241-3.patch, SYNCOPE-241-4.patch, SYNCOPE-241-5.patch, SYNCOPE-241-6.patch, SYNCOPE-241.patch The core module currently contains many parts of syncope. This makes it bigger and more complex than necessary. A possible modularization is to move the internal model (org.apache.syncope.core.persistence*) and the persistence impl (org.apache.syncope.core.persistence.impl) out of core and into separate modules. One big advantage would be that the jpa code enhancements would then run in the model module only. Currently we run into some problems in the cxf migration when running the rest itests in core that may be caused by eclipse overwriting the enhanced classes with plain classes. If the model (peristence) classes are in a separate module we could leave it out of eclipse and so this would be no issue anymore. Another advantage would be that the persistence tests could run in the persistence impl module so when working on the core they would not have to run each time. -- 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
