Custom name for Exchanges

[Jens Hofmann]

Is there some kind of registry or attribute to specify a custom name for the exchanges? MassTransit currently uses the full type name (Namespace:Class)

In a full .net system using Namespace:Class seems reasonable, but we are working on an heterogeneous system.

[Chris Patterson]

With 4.x, you can now specify custom formatters for exchange names to be used for published messages, as well as bind arbitrary exchanges to receive endpoint queues.

On Thu, Jan 4, 2018 at 12:01 AM, Jens Hofmann <jns...@gmail.com> wrote:

Is there some kind of registry or attribute to specify a custom name for the exchanges? MassTransit currently uses the full type name (Namespace:Class)

In a full .net system using Namespace:Class seems reasonable, but we are working on an heterogeneous system.

--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-discuss+unsub...@googlegroups.com.
To post to this group, send email to masstransit-discuss@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/masstransit-discuss/ae4b9f5e-919f-4e4b-89d1-4846fc2ea667%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Chris Patterson]

Custom exchange bindings:

http://masstransit-project.com/MassTransit/advanced/topology/rabbitmq/binding.html

Not much detail here yet but you can specify an exchange name for a topic: 

http://masstransit-project.com/MassTransit/advanced/topology/publish.html

On Thu, Jan 4, 2018 at 8:23 AM, Chris Patterson <ch...@phatboyg.com> wrote:

With 4.x, you can now specify custom formatters for exchange names to be used for published messages, as well as bind arbitrary exchanges to receive endpoint queues.

On Thu, Jan 4, 2018 at 12:01 AM, Jens Hofmann <jns...@gmail.com> wrote:

Is there some kind of registry or attribute to specify a custom name for the exchanges? MassTransit currently uses the full type name (Namespace:Class)

In a full .net system using Namespace:Class seems reasonable, but we are working on an heterogeneous system.

--
You received this message because you are subscribed to the Google Groups "masstransit-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to masstransit-discuss+unsubscribe...@googlegroups.com.