You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "Francesco Chicchiriccò (JIRA)" <ji...@apache.org> on 2014/06/13 16:20:02 UTC
[jira] [Resolved] (SYNCOPE-502) Allow list of PropagationActions
for Resource, SyncActions for SyncTask and PushActions for PushTask
[ https://issues.apache.org/jira/browse/SYNCOPE-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francesco Chicchiriccò resolved SYNCOPE-502.
--------------------------------------------
Resolution: Fixed
> Allow list of PropagationActions for Resource, SyncActions for SyncTask and PushActions for PushTask
> ----------------------------------------------------------------------------------------------------
>
> Key: SYNCOPE-502
> URL: https://issues.apache.org/jira/browse/SYNCOPE-502
> Project: Syncope
> Issue Type: Improvement
> Reporter: Francesco Chicchiriccò
> Assignee: Francesco Chicchiriccò
> Fix For: 1.2.0
>
>
> Currently {{Resource}} can define a single [PropagationActions|https://cwiki.apache.org/confluence/display/SYNCOPE/PropagationActionsClass] class, {{SyncTask}} can define a single [SyncActions|https://cwiki.apache.org/confluence/display/SYNCOPE/SyncActionsClass] and {{PushTask}} can define a single [PushActions|https://cwiki.apache.org/confluence/display/SYNCOPE/PushActionsClass] class.
> This is somewhat limiting: a list of actions class, to be invoked in the specified order, looks more powerful.
--
This message was sent by Atlassian JIRA
(v6.2#6252)