[ 
https://issues.apache.org/jira/browse/SYNCOPE-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474930#comment-13474930
 ] 

Francesco Chicchiriccò edited comment on SYNCOPE-218 at 10/12/12 10:36 AM:
---------------------------------------------------------------------------

Very nice text and examples, thank Bob and Jan!

I think that a single aspect is to be enhanced: the sentence "The default 
implementation is based on Activiti BPM." is not completely correct.

In fact, any Syncope project can override [1]; this will allow to choose among:
 * the Activiti-based workflow adapter (i.e. the one referenced as 'default')
 * the empty (no op) workflow adapter
 * any other custom class extending AbstractUserWorkflowAdapter [3] or 
implementing UserWorkflowAdapter [4] - this would allow the greatest flexibility

Last option would also suggest to add a child page to [5]... ;-)

[1] 
https://svn.apache.org/repos/asf/incubator/syncope/trunk/core/src/main/resources/workflow.properties
[2] 
https://svn.apache.org/repos/asf/incubator/syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/NoOpUserWorkflowAdapter.java
[3] 
https://svn.apache.org/repos/asf/incubator/syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/AbstractUserWorkflowAdapter.java
[4] 
https://svn.apache.org/repos/asf/incubator/syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/UserWorkflowAdapter.java
[5] https://cwiki.apache.org/confluence/display/SYNCOPE/Extending+Syncope
                
      was (Author: ilgrosso):
    Very nice text and examples, thank Bob and Jan!

I think that a single aspect is to be enhanced: the sentence "The default 
implementation is based on Activiti BPM." is not completely correct.

In fact, any Syncope project can override [1]; this will allow to choose among:
 * the Activiti-based workflow adapter (i.e. the one referenced as 'default')
 * the empty (no op) workflow adapter
 * any other custom class extending AbstractUserWorkflowAdapter [3] or 
implementing UserWorkflowAdapter - this would allow the greatest flexibility

Last option would also suggest to add a child page to [5]... ;-)

[1] 
https://svn.apache.org/repos/asf/incubator/syncope/trunk/core/src/main/resources/workflow.properties
[2] 
https://svn.apache.org/repos/asf/incubator/syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/NoOpUserWorkflowAdapter.java
[3] 
https://svn.apache.org/repos/asf/incubator/syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/AbstractUserWorkflowAdapter.java
[4] 
https://svn.apache.org/repos/asf/incubator/syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/UserWorkflowAdapter.java
[5] https://cwiki.apache.org/confluence/display/SYNCOPE/Extending+Syncope
                  
> User Workflow visualization
> ---------------------------
>
>                 Key: SYNCOPE-218
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-218
>             Project: Syncope
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 1.0.1-incubating
>            Reporter: Jan Bernhardt
>            Assignee: Jan Bernhardt
>            Priority: Minor
>             Fix For: 1.1.0-incubating
>
>         Attachments: userWorkflow.bpmn20.xml, Workflow2.png
>
>
> I attached a picture of the current workflow structure in syncope. This could 
> be helpful at the Wiki-Page to visualize a normal User process in syncope.

--
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

Reply via email to