Great, glad to hear it. Regards Tim.
On Thu, 2008-06-19 at 14:53 -0700, wannaKnow wrote: > That was helpful. I've been able to get it going with C++ clients talking to > JAVA clients. > Thanks. > > > tabish121 wrote: > > > > Topics and Queues are created dynamically on the ActiveMQ broker, > > there's no need to create them ahead of time like you would with > > Websphere for instance. There should be no problem in sending messages > > from CMS to a JMS client. Just create a JMS client with a consumer > > listening on the Queue in question and a CMS client that produces to the > > same Queue and it should work. > > > > Regards > > Tim. > > > >> -----Original Message----- > >> From: wannaKnow [mailto:[EMAIL PROTECTED] > >> Sent: Thursday, June 19, 2008 2:04 PM > >> To: [email protected] > >> Subject: sending msg via CMS to JMS > >> > >> > >> I'd like to use CMS to create messages and put them on an Apache > > ActiveMQ > >> destination which has been configured as a JMS queue and then have a > >> MessageDrivenBean extract the messages. Sending and receiving > > messages > >> between CMS producer/consumer destinations is working for me. > >> I've started with the default BrokerURI and also updated it to use my > >> specific IP and I also updated the queue name. Both worked. > >> std::string brokerURI = > >> "tcp://127.0.0.1:61616" > >> "?wireFormat=openwire" > >> "&transport.useAsyncSend=true"; > >> std::string destinationName="jms/TestQueue"; > >> > >> So my questions: > >> Is it necessary for me to install JBOSS or WebSphere to do this or can > >> ActiveMQ handle it by itself? > >> Are there special values needed in the BrokerURI or the Topic/Queue > > name ? > >> > >> I'm hoping someone can point me to documentation or samples or other > >> helpful > >> information about how to configure the JMS queue using ActiveMQ. > >> > >> Thx. > >> -- > >> View this message in context: > > http://www.nabble.com/sending-msg-via-CMS- > >> to-JMS-tp18014709p18014709.html > >> Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > > > > > >
