Skip to content

Conversation

@pipeosorio1
Copy link

The type of the RabbitMQ exchange, determines how messages are routed to the queue.

@nblumhardt
Copy link
Member

Thanks for sending this!

When using an exchange/fanout, it's possible that the exchange is not specifically for, nor owned by, the Seq RabbitMQ input. The assumption of the app is that if you're sending events to an exchange, you'll want to create that separately, and then bind the Seq app's input queue to the exchange.

Let me know if I'm missing something or if this causes trouble for your use case. Thanks again!

@pipeosorio1
Copy link
Author

Hello!

The idea is to avoid creating the queue externally. If the exchange is specified, it should take it and create the queue with the required exchange.

I'm looking forward to your response.

@pipeosorio1
Copy link
Author

Hello,

I conducted the test by creating my fork in a NuGet package, and if the Exchange is registered, it creates correctly. If it's not registered, it correctly creates the queue to the default Exchange.

https://www.nuget.org/packages/PipeOsorio.Seq.Input.RabbitMQ/1.0.12

I'm looking forward to your response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants