Hi!
The thing is that queues ARE location dependant, that's why you have to
specify queues like queue1@router1 if you want to send messages to them.
So remote queues are defined in this manner:
- specify a JNDI alias to point to your remote queue. Specifying JNDI
aliases is a good administration praxis! :))
- in JNDI swiftlet specify a remote queue
- specify a static route in routing swiftlet
The next issue:
you can send to remote queues, but you cannot receive messages from it(I
believe you cannot browse them either). If you want to do that, you have to
connect to queue's local router.
For example: queue1 is defined on router1 and you connect with your app to
router2. Specifying queue1@router1 while you send messages will get them to
the right queue, ok? But if you want to receive or browse messages, you
have to connect to router1 to do that. If you want to create a consumer on
router2 for queue1@router1 you get an Exception saying: "Queue is not
local" or something like this.
Does this make any sense? I hope this helps you.
Best regards,
Kovi
------------------------------------------------------
SwiftMQ developers mailing list * http://www.swiftmq.com
To unsubscribe from this list, send an eMail to
[EMAIL PROTECTED] and write in the body of your message:
UNSUBSCRIBE developers <your-email-address>
Archive: http://www.mail-archive.com/developers@mail.iit.de/
