springwolf
Units test to investigate AMQP generation
Units test to investigate AMQP generation I added some comments in the PR.
Deploy Preview for springwolf-ui canceled.
| Name | Link |
|---|---|
| Latest commit | 8c0950e89b30e232ea7b54f9832d347ebed20edd |
| Latest deploy log | https://app.netlify.com/sites/springwolf-ui/deploys/666054a762d49700098046e9 |
![netlify[bot] avatar](https://avatars.githubusercontent.com/in/13473?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hi @pdalfarr, I took this PR as a base to look into amqp and further understand how rabbitmq and the AsyncAPI amqp binding works. The result is https://github.com/springwolf/springwolf-core/pull/886
I agree with your point on the expected channel name. Assuming that is fixed, how to bind the routingKey + exchange with the queue (see my comment)?
Also, it would be great if you can verify the comments on RabbitListenerUtil as I gather them by testing, but have low confidence since I haven't used RabbitMQ in production (see https://github.com/springwolf/springwolf-core/pull/886/files#r1699142615 )
Closing this PR, as the proposed changes have been merged via other PRs.
Also, part of the issue has been addressed, while the link from exchange to queue is missing in the AsyncAPI at this point. Lets move the discussion into the original Springwolf issue https://github.com/springwolf/springwolf-core/issues/366