incubator-agila-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lim (JIRA)" <>
Subject [jira] Resolved: (AGILA-23) Initial Support for Actor Functionality
Date Sun, 27 Nov 2005 12:12:57 GMT
     [ ]
Chris Lim resolved AGILA-23:

    Resolution: Fixed

Patch applied.

> Initial Support for Actor Functionality
> ---------------------------------------
>          Key: AGILA-23
>          URL:
>      Project: Agila
>         Type: New Feature
>   Components: BPM Engine
>     Reporter: Geoff Howard
>     Assignee: Chris Lim
>  Attachments:,, actor.patch,
> Inital working draft of support for "actor" assignments from business process definitions.
 All current code hard-codes task assignments in the Task code and ignores the /process-model/graph/nodes/node/actors/actor
element.  This code provides one working approach to supporting this originally intended but
unimplemented functionality.  
> The basic approach here can be summarized as follows: 
> - Define a new service: ActorResolverService responsible for interpreting the simple
Actor name declared in the process.  An instance implementing this interface is given to the
TaskService as part of its configuration.
> - Modify the TaskService interface to add a method assignTaskToActors which accepts an
Actor[] and recursively resolves all references to either a UserID or GroupID and creates
tasks for each resolved entity.
> An alternative to modifying the TaskService would be to force each concrete Task to handle
the resolution and assignment itself.  I have initially rejected this approach because it
seems out of the scope of concern of the task to handle this resolution, especially when the
time comes to implement instance-level fields as actors (such as "self" or "initiator"). 

> Note that this patch removes the special actor "Self" from the Leave Application sample
which is not yet implemented (and apparently not supported by the engine yet)

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message