cocoandgaga commented on issue #4397: URL: https://github.com/apache/eventmesh/issues/4397#issuecomment-1692188860
> Because storage-plugin takes on the role of a queue inside eventmesh, not a connector, it was designed to be used without multiple queues. Thus, the existing exchange and queue in rabbitmq-storage-plugin are both singular and fixed. > > You may create a `eventmesh.default` exchange, a `DefaultQueue` queue, and bind both of them with `#` routingkey (to redirect all msgs `eventmesh.default` received to `DefaultQueue`) in rabbitmq, then fill in the same settings in `rabbitmq-client.properties`. > > In my case, I use these configurations, and I can send messages normally, and I didn't use the `callback url`. If these configurations can't satisfy your usage scenario, can you please tell me more about your need for `callback url`? Similarly, you can also describe your need for multiple queues if necessary. > > By the way, if you have encountered any bugs in the use, you are welcome to feedback to us; if you have not encountered bugs, you are also welcome to leave a message under this PR #4394. Thank you for your answer！According to what you said, what I need is the connect plugin？In service A, if eventMesh SDK is used to send a message to eventMesh. And the connection plugin type is rabbitmq, sinkEnable is turned on. Is it possible to call the api of service B when eventMesh sending messages to the rabbitmq？ -- 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]
