I hate to post such a vague question, but I'm totally confused at this
point and could really use some direction.
I have design where I need to have multiple brokers peered with each-
other, as in the "network of brokers" paradigm. The design requires
that I use the "virtual topics" feature
On 11-Mar-08, at 10:01 AM, James Strachan wrote:
I have been confused on this list before, but here I am again. :-)
I need to configure my brokers to fault-tolerant in a two-node
cluster. I'm configuring this directly inside Spring.
I believe I need to use some form of auto-discovery, journaled
On 11-Mar-08, at 10:01 AM, James Strachan wrote:
I have been confused on this list before, but here I am again. :-)
I need to configure my brokers to fault-tolerant in a two-node
cluster. I'm configuring this directly inside Spring.
I believe I need to use some form of auto-discovery, journaled
I have been confused on this list before, but here I am again. :-)
I need to configure my brokers to fault-tolerant in a two-node
cluster. I'm configuring this directly inside Spring.
I believe I need to use some form of auto-discovery, journaled
persistence and clustering, but after readin
On Oct 12, 2007, at 13:09, Adam Sherman wrote:
On Oct 12, 2007, at 10:31, James Strachan wrote:
To get things going and to avoid you having to worry about how to use
the JMS API properly and so forth I'd recommend you experiment with
the Bean Integration in Camel...
I'm not cle
what Camel actually is though. Going to go watch
your screencast now.
A.
--
Adam Sherman
Technologist
+1 (613) 797-6819 | http://www.sherman.ca/ | sip:[EMAIL PROTECTED]
ventually
add more.) My understanding of "topics" is that you can't force only
a single subscriber to handle each message.
Any thoughts/comments/suggestions you can provide would be very helpful.
Thank you,
A.
--
Adam Sherman
Technologist
+1 (613) 797-6819 | http://www.sherman.ca/ | sip:[EMAIL PROTECTED]
