Closed jkubrynski closed 5 years ago
That's not really correct: you can use any exchange with the right kind of destination. I don't know if there's much value in configuring the exchange that's used "by default". So leaving this open with a "no-decision" label.
@michaelklishin right, but this approach requires configuration changes on the application level. It'll be great to be able to override it in Rabbit
@jkubrynski I still question how valuable that is. On the other hand it's a really small change so we will consider it.
@michaelklishin So what was the decision? I think making this configurable makes sense.
No objections to making this configurable.
Nice, please make it happen :)
This is open source software. Instead of asking others to make something happen you can do it yourself.
If only rabbitmq wasn't coded in erlang... You said it that it was a really small change, for me I'd need to learn a new language, understand how the plugin works, find out what exacty needs to be changed so not exactly a small task.
Currently all STOMP messages are using amq.topic. It'll be great to be able to point them to configure STOMP plugin to use different exchange