-
1. Re: FUSE Message Broker - C# client
tabish121 Jul 23, 2009 3:38 PM (in response to bwitt@emsystems.com)You are getting this error because the Apache NMS client doesn't yet have an HTTP transport. Currently the NMS client has functional TCP and Multicast Discovery Transports.
-
2. Re: FUSE Message Broker - C# client
bwitt@emsystems.com Jul 23, 2009 3:49 PM (in response to tabish121)ok. that makes sense.
so what options do i have to access ActiveMQ from a .NET client? I'm aware of the REST/HTTP support, but looking for a native .NET library like NMS.
-
3. Re: FUSE Message Broker - C# client
oisin Jul 23, 2009 3:54 PM (in response to bwitt@emsystems.com)Did you check out the example code at http://activemq.apache.org/nms/examples.html? The code in there is pretty much exactly like your example snippet above except for the protocol in the URI.
Uri connecturi = new Uri("activemq:tcp://activemqhost:61616");
-
4. Re: FUSE Message Broker - C# client
bwitt@emsystems.com Jul 23, 2009 4:27 PM (in response to oisin)I need to communicate over HTTP versus TCP. That example will use TCP right?
-
5. Re: FUSE Message Broker - C# client
oisin Jul 23, 2009 5:49 PM (in response to bwitt@emsystems.com)Yes, that will only use TCP, it's true - but as tabish121 mentioned in a previous post, there isn't HTTP support in the NMS client. I guess I wasn't aware that you had no option but to use HTTP access, in which case right now the only support I am aware of is the REST stuff, where you will need to create your own .NET client. Sorry about that!
--oh