Only implicitly create exchanges for types being published. Limit queue ...

[particular]

Only implicitly create exchanges for types being published. Limit queue ...

[SimonCropp]

Raised by @SimonCropp

@fhalim this would seem to make sense, although i am not fully across the RabbitMQ codebase. So I have a few questions

• is there any impact to people using the existing implementation
• does any doco need to be updated. for example the xmldocs for that class
• is it possible to have a failing unit or integration test that illustrates the problem? then we apply the fix and watch it go green.

CC @andreasohlund

[SimonCropp]

Raised by @fhalim

As it turns out, the test When_sending_a_message_over_rabbitmq#Should_throw_when_sending_to_a_nonexisting_queue tested this scenario, but it was set to Ignore. Modified RabbitMqUnitOfWork wraps cases where the connection gets closed due to the exchange not existing in a QueueNotFoundException.

The tests in When_sending_a_message_over_rabbitmq were failing due to the recipient exchange not being created when the queue was being created. That has been corrected.