masayag opened a new issue, #724:
URL: https://github.com/apache/incubator-kie-kogito-docs/issues/724

   The following 
[page](https://github.com/apache/incubator-kie-kogito-docs/blob/main/serverlessworkflow/modules/ROOT/pages/use-cases/advanced-developer-use-cases/event-orchestration/consume-producing-events-with-kafka.adoc#examples-of-smallrye-channel-mapping)
 suggests how to configure a single channel for incoming events and an outgoing 
channel for outgoing events.
   
   However, the expected configuration isn't clear from the page.
   
   Adding an example for the default channels as below will make the use of it 
clearer:
   ```
   mp.messaging.incoming.kogito_incoming_stream.connector=smallrye-kafka
   
mp.messaging.incoming.kogito_incoming_stream.value.deserializer=org.apache.kafka.common.serialization.ByteArrayDeserializer
   mp.messaging.incoming.kogito_incoming_stream.topic=incoming-events
   
   mp.messaging.outgoing.kogito_outgoing_stream.connector=smallrye-kafka
   
mp.messaging.outgoing.kogito_outgoing_stream.value.serializer=org.apache.kafka.common.serialization.StringSerializer
   mp.messaging.outgoing.kogito_outgoing_stream.topic=outgoing-events
   ```
   
   A full example of the the defaultName option can also be useful:
   ```
   kogito.addon.messaging.incoming.defaultName=incoming_channel
   kogito.addon.messaging.outgoing.defaultName=outgoing_channel
   
   mp.messaging.incoming.incoming_channel.connector=smallrye-kafka
   
mp.messaging.incoming.incoming_channel.value.deserializer=org.apache.kafka.common.serialization.ByteArrayDeserializer
   mp.messaging.incoming.incoming_channel.topic=incoming-events
   
   mp.messaging.outgoing.outgoing_channel.connector=smallrye-kafka
   
mp.messaging.outgoing.outgoing_channel.value.serializer=org.apache.kafka.common.serialization.StringSerializer
   mp.messaging.outgoing.outgoing_channel.topic=outgoing-events
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to