Re: Virtual Topic and remote Client consumers

2009-08-11 Thread Mick Knutson
I tried what you suggested with this Broker: http://activemq.apache.org/schema/core";> ** ** And then I was sending mess

Re: Virtual Topic and remote Client consumers

2009-08-05 Thread Mick Knutson
Here is what I have on my server: *...@endpointinject(uri="activemq:**VirtualTopic.TABLE.1") ProducerTemplate producer; public boolean sendStatusUpdate(String body) { log.info("//--**--** //"); log.info("send

Re: Virtual Topic and remote Client consumers

2009-08-04 Thread Mick Knutson
In theory, the Virtual topics seems to be able to suit my use case. The only issue is trying to test for it. I am working with Camel routing as well. So let me try a bit more to get a working test to send a testMessage into my Virtual topic, then consume it. I think I might be close. I will post

Re: Virtual Topic and remote Client consumers

2009-08-04 Thread Willem Jiang
Hi, activemq-camel is much high level API, we should make sure the ActiveMQ provides this kind of feature. I just checked the Unit test code, it looks like we need to create the physical queue before the producer send the message. Mick does this OK for you ? Or you may still need to try durab

Re: Virtual Topic and remote Client consumers

2009-08-04 Thread Mick Knutson
Where can I find import org.apache.activemq.spring.ConsumerBean; I have looked at the activemq-camel and activemq-core jars and they are not there. It appears to be just for testing? --- Thank You… Mick Knutson, President BASE Logic, Inc. Enterprise Architecture, Design, Mentoring & Agile Con

Re: Virtual Topic and remote Client consumers

2009-08-04 Thread Joe Fernandez
In the AMQ source tree, check out .../activemq-core/src/test/java/org/apache/activemq/broker/virtual Joe http://www.ttmsolutions.com Mick Knutson-3 wrote: > > I am fine with the default, I guess I just an not clear how to start > writing > a test to verify each piece. > > 1. Testing that my

Re: Virtual Topic and remote Client consumers

2009-08-04 Thread Mick Knutson
I am fine with the default, I guess I just an not clear how to start writing a test to verify each piece. 1. Testing that my publisher can create messages going to: VirtualTopic.*table123 (*) 2. Writing a test that 2 different consumers can consume messages on Consumer..Virtual

Re: Virtual Topic and remote Client consumers

2009-08-04 Thread Joe Fernandez
I believe that by default, the corresponding queue names must follow this syntax Consumer..VirtualTopic. You can override the default naming convention via the element. You might also want to look into using Camel to implement a similar messaging pattern (i.e., recipient list). http://www