[
https://jira.nuxeo.com/browse/NXP-8137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=107742#comment-107742
]
Thierry Delprat commented on NXP-8137:
--------------------------------------
The problem is that there may be specific listener that may react to the cancel
event and we probably don't want that.
> JBPM migrated tasks could maybe be canceled and not only suspended.
> -------------------------------------------------------------------
>
> Key: NXP-8137
> URL: https://jira.nuxeo.com/browse/NXP-8137
> Project: Nuxeo Enterprise Platform
> Issue Type: Improvement
> Components: Workflow
> Affects Versions: 5.5-SNAPSHOT
> Reporter: Antoine Taillefer
>
> In {{TaskMigrationRunner#migrateGenericTask}}, we suspend the JBPM task
> instance once it has been migrated:
> {code:java}
> ti.suspend();
> {code}
> Maybe is should even be canceled to keep it in a "cleaner" state since it is
> not supposed to be used anymore:
> {code:java}
> ti.cancel();
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
