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

ASF subversion and git services commented on ARIA-163:
------------------------------------------------------

Commit b3927144616521e28145bf68521b5735c262a7da in incubator-ariatosca's branch 
refs/heads/ARIA-163-Update-node-state-for-stub-tasks from [~Mxmrlv]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-ariatosca.git;h=b392714 ]

ARIA-163 Update node state for stub tasks

Additional changes:
 * removed `for_node` and `for_relationship` from the api OperationTask.
 * api based OperationTask could also have an empty implementation.
 * each core task wields its own executor.
 * Reordered some of the helper functions for creating tasks.
 * intoduced 2 new executors: StubTaskExecutor (for stub tasks) and 
EmptyOperationExecutor (for empty tasks)


> Update node state for stub tasks
> --------------------------------
>
>                 Key: ARIA-163
>                 URL: https://issues.apache.org/jira/browse/ARIA-163
>             Project: AriaTosca
>          Issue Type: Story
>    Affects Versions: 0.1.0
>            Reporter: Maxim Orlov
>            Assignee: Maxim Orlov
>
> Currently each node that has no implementation for an operation, has its 
> operations labeled a stub tasks. Those stub tasks aren't run through the 
> normal path of the workflow engine, and thus no update to the state of the 
> node is being done. this should be fixed 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to