Hi,
It is not intended to limit to rabbitmq. Patches are welcome to make it
to work with other providers :-) It just shouldn't be too extensive to
add another MQ binding or implementation in mono repo either as sources
or submodule. Hard-coded, run-time resolution to assemblies that don't
exist in mono itself would be fine (as long as it works, when those
assemblies can be resolved).
Thanks,
Atsushi Eno
On 2015年01月25日 06:40, Philip Garrett wrote:
Mono.Messaging allows you to specify a custom messaging provider in the
MONO_MESSAGING_PROVIDER appsetting. But it appears only to work with the
RabbitMQ provider that’s packaged with Mono. Any value other than the
pre-approved provider class name (or its alias) makes MessagingProviderLocator
throw an exception in the static constructor. (1)
Is this intentional or is it a bug/missing feature? Would a patch to allow any
custom IMessagingProvider be welcomed?
Thanks,
Philip
(1)
https://github.com/mono/mono/blob/effa4c07ba850bedbe1ff54b2a5df281c058ebcb/mcs/class/Mono.Messaging/Mono.Messaging/MessagingProviderLocator.cs#L90
_______________________________________________
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
_______________________________________________
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
