refactor publish events towards engine scope about lib-bpmn-engine HOT 3 OPEN

It's seems that we need to do the message correlation instead of publishing message event to specifiy process instance.

useful docs : https://docs.camunda.io/docs/components/concepts/messages/

from lib-bpmn-engine.

Hi,

that's an interesting thought, yes.
Message correlation is a powerful feature in Zeebe/Camunda v8.
I learned/observed, that people do struggle with it in the beginning, but once understood, it's very powerful.
Since lib-bpmn-engine offers a somewhat different execution context, I consider offering both options.
Meaning, two functions could exists in parallel:

• PublishEventForInstance()
• PublishEventWithCorrelationKey()

from lib-bpmn-engine.

Update,

adding/registering a task handler has similar concepts, when it comes to the possibilities of how to do it.
the fluent API as implemented in https://github.com/nitram509/lib-bpmn-engine/blob/main/pkg/bpmn_engine/task_handler.go
seems to be very good fitting, as it guides the usage better and also allows more minimal invasive enhancements over time.

So, we should use such an approach here as well.

from lib-bpmn-engine.