camunda - Camunda 任务与事件的混淆

Question

在最新的 Camunda 文档页面中，我注意到在讨论任务监听器与事件监听器的部分中存在一些令人困惑的信息:https://docs.camunda.org/manual/latest/user-guide/process-applications/process-application-event-listeners/ .

例如，本节包含以下文本(我将两个单词加粗):

The invoice process has a task named “archive invoice”. The application “invoice.war” further provides a Java Class implementing the ExecutionListener interface and is configured to be invoked whenever the END event is fired on the “archive invoice” activity.

我知道给抽象术语命名充满了困难，但看起来本文并不清楚什么是“任务”与“事件”。

Answer 1

这个问题已由 Thorben 和我在 Camunda 论坛中回答。

查看我的回答 here :

An activity is the global class on which tasks, subprocess, call activities etc. belongs to. So a Task is also an activity, but an activity is not necessarily a task. See the reference for more detailed explanation.

还有托本斯 addition :

In addition to Chris' explanation, the term task is overloaded in the Camunda and BPMN context. It refers to a task in the BPMN 2.0 context (aka a design time unit of work that is/cannot broken down further => service task, human task, send task, etc.) as well as a task in the tasklist (aka a runtime unit of work that needs to be completed by a human).

希望有帮助。