mp.messaging.outgoing.barista-process.connector=smallrye-kafka
mp.messaging.outgoing.barista-process.value.serializer=org.apache.kafka.common.serialization.StringSerializer
mp.messaging.incoming.barista-process.connector=smallrye-kafka
mp.messaging.incoming.barista-process.value.deserializer=org.apache.kafka.common.serialization.StringSerializer
So, I attempted to skirt around this issue with:
mp.messaging.outgoing.barista-process.connector=smallrye-kafka
mp.messaging.outgoing.barista-process.topic=barista-process2
mp.messaging.outgoing.barista-process.value.serializer=org.apache.kafka.common.serialization.StringSerializer
mp.messaging.incoming.barista-process2.connector=smallrye-kafka
mp.messaging.incoming.barista-process2.topic=barista-process2
mp.messaging.incoming.barista-process2.value.deserializer=org.apache.kafka.common.serialization.StringDeserializer
But end up getting:
2022-02-28 10:29:53,428 WARN [org.kie.kog.eve.imp.CloudEventConsumer] (pool-1-thread-1) Consumer for CloudEvent type 'Barista_processMessageDataEvent_5', trigger 'barista-process2': ignoring message with type 'barista-process', source '/process/drink_order_process'
First question, is there anyway to turn off cloud events, change the type, accept a different type, create a bean?
Second question, is this simply an anti-pattern and I should be doing cross bpmn through some other means that make more sense in the Kogito world? eg. Rest calls.
Thanks!