RE: Persistence id generation strategy: TABLE vs AUTO

I have digged into the NotificationTestITCase problem a little bit more and discovered the following: Initial load (context.xml) creates two notifications with id= 100 and 101. It seems that AUTO generation strategy, used in Notification now, starts with ID=101 (not sure how to influence on

[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: (was: SYNCOPE-241-4.patch) Move persistence and persistence

Cosole REST Service Client implements Serializable ?

Hi Syncopers, I'm currently updating syncope console to use new REST Service Interface (with old Spring proxy variant). And since my Eclipse is complaining about a missing serialVersionUID I was wondering why does BaseRestClient implements Serializable? Is there any need to make the rest

Re: Cosole REST Service Client implements Serializable ?

On 14/01/2013 10:02, Jan Bernhardt wrote: Hi Syncopers, I'm currently updating syncope console to use new REST Service Interface (with old Spring proxy variant). And since my Eclipse is complaining about a missing serialVersionUID I was wondering why does BaseRestClient implements

[jira] [Commented] (SYNCOPE-272) Apache Syncope updates all attributes from an user

[ https://issues.apache.org/jira/browse/SYNCOPE-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13552520#comment-13552520 ] Marco Di Sabatino Di Diodoro commented on SYNCOPE-272: -- Fix for

[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=13552524#comment-13552524 ] Francesco Chicchiriccò commented on SYNCOPE-241: Christian, the updated

[jira] [Updated] (SYNCOPE-272) During sync null attributes from template are considered

[ https://issues.apache.org/jira/browse/SYNCOPE-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-272: --- Summary: During sync null attributes from template are considered (was:

[jira] [Updated] (SYNCOPE-272) During sync null attributes from template are considered

[ https://issues.apache.org/jira/browse/SYNCOPE-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-272: --- Description: During execution of synchronization tasks, all user attributes

[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=13552534#comment-13552534 ] Christian Schneider commented on SYNCOPE-241: - 1. I removed the commented out

[jira] [Created] (SYNCOPE-273) Role deletion inhibit existing notifications updates

Denis Signoretto created SYNCOPE-273: Summary: Role deletion inhibit existing notifications updates Key: SYNCOPE-273 URL: https://issues.apache.org/jira/browse/SYNCOPE-273 Project: Syncope

[jira] [Updated] (SYNCOPE-273) Role deletion inhibit existing notification updates

[ https://issues.apache.org/jira/browse/SYNCOPE-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Signoretto updated SYNCOPE-273: - Summary: Role deletion inhibit existing notification updates (was: Role deletion

[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=13552553#comment-13552553 ] Francesco Chicchiriccò commented on SYNCOPE-241: About (1), commented

R: Little console usability refactoring proposal

-Messaggio originale- Da: Fabio Martelli [mailto:fabio.marte...@gmail.com] Inviato: giovedì 10 gennaio 2013 18:34 A: dev@syncope.apache.org Oggetto: Re: Little console usability refactoring proposal Il giorno 10/gen/2013, alle ore 17.42, Denis Signoretto ha scritto: Hi

[jira] [Resolved] (SYNCOPE-272) During sync null attributes from template are considered

[ https://issues.apache.org/jira/browse/SYNCOPE-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-272. -- Resolution: Fixed

New member

Hi all together. I'm Christian Schmuelling, working for Talend and I'll support the team for the cxf implementation. @Francesco Could you please grant me access to developers part in the wiki? With best regards Christian

[jira] [Resolved] (SYNCOPE-172) Role propagation / synchronization

[ https://issues.apache.org/jira/browse/SYNCOPE-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-172. Resolution: Fixed http://svn.apache.org/viewvc?rev=1432990view=rev

[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=13552885#comment-13552885 ] Francesco Chicchiriccò commented on SYNCOPE-241: Christian, if you are

[jira] [Updated] (SYNCOPE-273) Role deletion inhibits notification update

[ https://issues.apache.org/jira/browse/SYNCOPE-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-273: --- Summary: Role deletion inhibits notification update (was: Role deletion

[jira] [Assigned] (SYNCOPE-273) Role deletion inhibits notification update

[ https://issues.apache.org/jira/browse/SYNCOPE-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò reassigned SYNCOPE-273: -- Assignee: Francesco Chicchiriccò Role deletion inhibits