Conversation
…ources and resources provided by plugin developers
hhund
left a comment
hhund
left a comment
There was a problem hiding this comment.
For API v2 we should not link to Operaton pages with Java code examples.
|
|
||
| ## Execution Listeners | ||
|
|
||
| [Execution Listeners](https://docs.operaton.org/docs/documentation/user-guide/model-api/bpmn-model-api/delegation-code/#execution-listener) can be registered to various flow elements like process, events, tasks, gateways and sequence flows. They are called when the process execution arrives at the flow element they are registered to. No newline at end of file |
There was a problem hiding this comment.
Maybe add:
Java execution listeners must implement the API v2 interface dev.dsf.bpe.v2.activity.ExecutionListener.
Maybe remove the link to the Opeaton page, as the example Java code does not work with API v2.
| ### Message Intermediate Throwing Event | ||
| [Message Intermediate Throwing Events](https://docs.camunda.org/manual/7.21/reference/bpmn20/events/message-events/#message-intermediate-throwing-event) are used to send messages during process execution. | ||
| #### Message Intermediate Throwing Event | ||
| [Message Intermediate Throwing Events](https://docs.operaton.org/docs/documentation/reference/bpmn20/events/message-events#message-intermediate-throwing-event) are used to send messages during process execution. |
There was a problem hiding this comment.
Maybe add:
Message intermediate throwing events that are used to communicate with DSF instances via FHIR Task resources, should implement the API v2 interface dev.dsf.bpe.v2.activity.MessageIntermediateThrowEvent.
| ### Message End Event | ||
| The [Message End Event](https://docs.camunda.org/manual/7.21/reference/bpmn20/events/message-events/#message-end-event) will stop the execution of a BPMN process and finish by sending a message. No newline at end of file | ||
| #### Message End Event | ||
| The [Message End Event](https://docs.operaton.org/docs/documentation/reference/bpmn20/events/message-events#message-end-event) will stop the execution of a BPMN process and finish by sending a message. |
There was a problem hiding this comment.
Maybe add:
Message end events that are used to communicate with DSF instances via FHIR Task resources, should implement the API v2 interface dev.dsf.bpe.v2.activity.MessageEndEvent.
| The [Message End Event](https://docs.operaton.org/docs/documentation/reference/bpmn20/events/message-events#message-end-event) will stop the execution of a BPMN process and finish by sending a message. | ||
|
|
||
| #### Message Send Task | ||
| Same as the [Message Intermediate Throwing Event](#message-intermediate-throwing-event), the [Message Send Task](https://docs.operaton.org/docs/documentation/reference/bpmn20/tasks/send-task/) is used to send messages during process execution but is also intended to execute some kind of business logic at the same time. No newline at end of file |
There was a problem hiding this comment.
Maybe add:
Message send tasks that are used to communicate with DSF instances via FHIR Task resources, should implement the API v2 interface dev.dsf.bpe.v2.activity.MessageSendTask.
| ## Service Tasks | ||
|
|
||
| One of the most common types of BPMN Tasks used for modeling DSF processes is the [Service Task](https://docs.camunda.org/manual/7.21/reference/bpmn20/tasks/service-task/). They are different from regular BPMN Tasks in that they offer the ability to link an implementation to the [Service Task](https://docs.camunda.org/manual/7.21/reference/bpmn20/tasks/service-task/) which can be called and executed by a BPMN engine. The BPE (Business Process Engine) server of the DSF leverages this engine to execute BPMN processes. | ||
| One of the most common types of BPMN Tasks used for modeling DSF processes is the [Service Task](https://docs.operaton.org/docs/documentation/reference/bpmn20/tasks/service-task). They are different from regular BPMN Tasks in that they offer the ability to link a Java class to the [Service Task](https://docs.operaton.org/docs/documentation/reference/bpmn20/tasks/service-task) which can be called and executed by a BPMN engine. The BPE (Business Process Engine) server of the DSF leverages this engine to execute BPMN processes and their associated code. No newline at end of file |
There was a problem hiding this comment.
Maybe add
Java service tasks must implement the API v2 interface dev.dsf.bpe.v2.activity.ServiceTask.
…orial.org nor is it unresolvable
…orial.org nor is it unresolvable
schwzr
left a comment
schwzr
left a comment
There was a problem hiding this comment.
please replace my.org with an official example domain
| <dependency> | ||
| <groupId>dev.dsf</groupId> | ||
| <artifactId>dsf-bpe-process-api-v2</artifactId> | ||
| <artifactId>dsf-bpe-process-api-v2</artifactId> |
…orial.org nor is it unresolvable
3 participants
A lot of wording improvements going from direct speech to passive and added more API v2 specific information like activities and message activities which replace the message and service delegates from API v1