Hi Łukasz, I have made an enhancement to the Broker as QPID-8377 <https://issues.apache.org/jira/browse/QPID-8377> along the lines I suggested in my previous mail. I hope this will meet your requirements.
Thanks, Rob On Mon, 11 Nov 2019 at 09:33, Rob Godfrey <[email protected]> wrote: > Hi Łukasz, > > firstly let me apologise for not getting back to you sooner. > > Secondly, unfortunately I agree that there is no current way to explicitly > tell the broker to ignore unknown exchange declare arguments, and that > adding this ability is a good idea. The simplest approach is probably to > add a configurable property to the VirtualHost for > "unknownExchangeDeclareArgumentPolicy" (or something like that) with > options of FAIL, LOG and IGNORE (where the current behaviour - FAIL - would > be the default). If that seems reasonable to you we can raise a JIRA and > make a change. > > Thanks, > Rob > > On Mon, 4 Nov 2019 at 13:31, Lukasz Guzik <[email protected]> > wrote: > >> Hello, >> >> I'm working on using Qpid broker as an in-memory AMQP message broker, that >> will be used in place of RabbitMQ for integration tests of my Java >> service. >> While I managed to successfully run Qpid, I'm having issues with my >> RabbitMQ connector library using some RMQ-specific exchange declare >> arguments. Basically, Qpid refuses to create an exchange with error: >> Unsupported exchange declare arguments: x-ha-policy,ha-mode. >> Is there any option to make Qpid ignore these arguments, or to write a >> custom handler for these (that will basically do nothing)? I wasn't able >> to >> find any solution in the docs nor over the internet, unfortunately. >> >> Thank you! >> >> -- >> >> Łukasz Guzik >> >> Senior Software Engineer >> >> [email protected] >> >> Beekeeper · beekeeper.io · We are hiring >> <https://www.beekeeper.io/en/company/jobs> >> >> Beekeeper AG, Pawia 9, 31-154 Cracow, Poland >> >> https://www.beekeeper.io/en/company/jobs >> >
