Hi Jim, Thanks for the reply. I've pretty much gotten that far. The trick I'm not able to sort out on my own is actually configuring STOMPConnect to bridge to JBM. The documentation is a little patchy, I'm not sure which configs to touch, would I run STOMPConnect as a stand-alone product, or can I use the "Injection Dependency" mentioned in the docs? I'm comfortable that I'll sort the client out, it's the server and bridge config that I'm not too sure of.
TIA, j/ -----Original Message----- From: Jim Gomes [mailto:[EMAIL PROTECTED] Sent: 25 February 2008 23:50 To: users@activemq.apache.org Subject: Re: JBoss Messaging Stomp Configuration Hi Johann, To get the NMS client to talk the stomp protocol, you will need to set your connection string in one of the following formats. Either is acceptable, so it's up to you which one you prefer. activemq:tcp://jbosssrvr:61613?transport.wireformat=stomp OR activemq:stomp://jbosssrvr:61613 The port 61613 is the port that ActiveMQ listens on for STOMP protocol messages. You will need to set the correct port entry for the JBOSS Messaging broker. If JBOSS Messaging does not support STOMP natively, you may need to use the STOMPConnect product to bridge between your client and JBOSS Messaging. Good Luck, Jim On Mon, Feb 25, 2008 at 1:06 PM, Johann Ungerer <[EMAIL PROTECTED]> wrote: > Hi All, > > I'm totally new to the entire JMS environment, but am trying to connect a > .NET Client to a JBOSS Messaging implementation. Thus far I've tried with > the NMS client, using an OpenWire connector, but I figure this will never > work. > > It's been recommended that I use a STOMP connector, but can't quite get > either my JBOSS Server configured to listen on STOMP, or get STOMP to talk > to the JBOSS. > > Has anyone tried to make a C# client talk to JBOSS and if so, please > provide some guidance on what I need to do in order to achieve this. > > TIA, > j/ > >
