-
Task
-
Resolution: Done
-
Major
-
None
-
5
-
False
-
False
-
Undefined
-
---
-
---
-
-
2020 Week 43-45 (from Okt 19)
Currently the type of the cloud event in processes is inferred from the class type of the generated message. Instead, we use the `message` type in the model. This way a process can declare the messages it emits and the messages it expects; the MessageConsumer will only accept messages of those types.
This also makes it easier to write cases where the kogito_incoming_stream and kogito_outgoing_stream actually correspond to the same channel (i.e. we are writing to a channel that will be subscribed by another process within the same application) because the names of the messages are now predictable and user-defined.
see attached pic
- blocks
-
KOGITO-3272 Consolidate CloudEvents usages (Part 1)
-
- Resolved
-
- is related to
-
KOGITO-3724 CloudEventConsumer throws upon receiving a message of an unhandled type
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
-
- Resolved
-