-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
channel.default_exchange doesn't behave like default exchange #24
Comments
A possible solution (at least for my usage):
Another possibility:
If I get some time I'll see if I can work one of those up and see if it works for me and if so put in a pull request. If not, happy for any sort of solution. |
Sorry for reviving and old (but open) issue. Here's how I "solved" the issue:
Can I open a PR to include this functionality in BunnyMock? |
of course @arnodirlam - make a PR and we can talk about migration |
The default exchange should (as I understand - please correct if I'm wrong) route a message to a queue specified by the routing_key even if it is not explicitly bound (ala https://www.rabbitmq.com/tutorials/amqp-concepts.html under "Default Exchange")
So something like:
channel.default_exchange.publish('message', routing_key: 'test_queue', persistent: true)
should always send the message 'message' to the queue 'test_queue', even with no explicit binding, assuming that that queue exists.
This doesn't seem to happen with BunnyMock.
The text was updated successfully, but these errors were encountered: