You are viewing a plain text version of this content. The canonical link for it is here.
Posted to agila-dev@incubator.apache.org by "Geoff Howard (JIRA)" <ag...@incubator.apache.org> on 2005/11/21 21:06:41 UTC
[jira] Created: (AGILA-23) Initial Support for Actor Functionality
Initial Support for Actor Functionality
---------------------------------------
Key: AGILA-23
URL: http://issues.apache.org/jira/browse/AGILA-23
Project: Agila
Type: New Feature
Components: BPM Engine
Reporter: Geoff Howard
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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (AGILA-23) Initial Support for Actor Functionality
Posted by "Chris Lim (JIRA)" <ag...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/AGILA-23?page=all ]
Chris Lim resolved AGILA-23:
----------------------------
Resolution: Fixed
Patch applied.
> Initial Support for Actor Functionality
> ---------------------------------------
>
> Key: AGILA-23
> URL: http://issues.apache.org/jira/browse/AGILA-23
> Project: Agila
> Type: New Feature
> Components: BPM Engine
> Reporter: Geoff Howard
> Assignee: Chris Lim
> Attachments: ActorResolverService.java, ActorResolverServiceImpl.java, actor.patch, 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (AGILA-23) Initial Support for Actor Functionality
Posted by "Geoff Howard (JIRA)" <ag...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/AGILA-23?page=all ]
Geoff Howard closed AGILA-23:
-----------------------------
Thanks for applying the patch quickly. Didn't realize I had forgotten to close the issue out.
> Initial Support for Actor Functionality
> ---------------------------------------
>
> Key: AGILA-23
> URL: http://issues.apache.org/jira/browse/AGILA-23
> Project: Agila
> Type: New Feature
> Components: BPM Engine
> Reporter: Geoff Howard
> Assignee: Chris Lim
> Attachments: ActorResolverService.java, ActorResolverServiceImpl.java, actor.patch, 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (AGILA-23) Initial Support for Actor Functionality
Posted by "Chris Lim (JIRA)" <ag...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/AGILA-23?page=all ]
Chris Lim reassigned AGILA-23:
------------------------------
Assign To: Chris Lim
> Initial Support for Actor Functionality
> ---------------------------------------
>
> Key: AGILA-23
> URL: http://issues.apache.org/jira/browse/AGILA-23
> Project: Agila
> Type: New Feature
> Components: BPM Engine
> Reporter: Geoff Howard
> Assignee: Chris Lim
> Attachments: actor.patch, 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (AGILA-23) Initial Support for Actor Functionality
Posted by "Geoff Howard (JIRA)" <ag...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/AGILA-23?page=all ]
Geoff Howard updated AGILA-23:
------------------------------
Attachment: actor.patch
> Initial Support for Actor Functionality
> ---------------------------------------
>
> Key: AGILA-23
> URL: http://issues.apache.org/jira/browse/AGILA-23
> Project: Agila
> Type: New Feature
> Components: BPM Engine
> Reporter: Geoff Howard
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (AGILA-23) Initial Support for Actor Functionality
Posted by "Geoff Howard (JIRA)" <ag...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/AGILA-23?page=all ]
Geoff Howard updated AGILA-23:
------------------------------
Attachment: ActorResolverService.java
> Initial Support for Actor Functionality
> ---------------------------------------
>
> Key: AGILA-23
> URL: http://issues.apache.org/jira/browse/AGILA-23
> Project: Agila
> Type: New Feature
> Components: BPM Engine
> Reporter: Geoff Howard
> Assignee: Chris Lim
> Attachments: ActorResolverService.java, ActorResolverServiceImpl.java, actor.patch, 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (AGILA-23) Initial Support for Actor Functionality
Posted by "Geoff Howard (JIRA)" <ag...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/AGILA-23?page=all ]
Geoff Howard updated AGILA-23:
------------------------------
Attachment: actor.patch
Updated patch with required change in servlet, additional typo fix, and removed "System.out" call. Replaces previous attachment entirely.
> Initial Support for Actor Functionality
> ---------------------------------------
>
> Key: AGILA-23
> URL: http://issues.apache.org/jira/browse/AGILA-23
> Project: Agila
> Type: New Feature
> Components: BPM Engine
> Reporter: Geoff Howard
> Attachments: actor.patch, 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (AGILA-23) Initial Support for Actor Functionality
Posted by "Geoff Howard (JIRA)" <ag...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/AGILA-23?page=all ]
Geoff Howard updated AGILA-23:
------------------------------
Attachment: ActorResolverServiceImpl.java
> Initial Support for Actor Functionality
> ---------------------------------------
>
> Key: AGILA-23
> URL: http://issues.apache.org/jira/browse/AGILA-23
> Project: Agila
> Type: New Feature
> Components: BPM Engine
> Reporter: Geoff Howard
> Assignee: Chris Lim
> Attachments: ActorResolverService.java, ActorResolverServiceImpl.java, actor.patch, 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira