This content has been marked as final.
Show 4 replies
-
1. Re: Wild Card routing and security
timfox Sep 11, 2008 6:44 AM (in response to ataylor)"ataylor" wrote:
Currently when a message is routed an ADDRESS_DOES_NOT_EXIST exception is thrown if security is enabled and the destination doesn't exist. With wild card routing this doesn't make sense, so the possible solutions are:
Why doesn't this make sense? Can you elaborate? -
2. Re: Wild Card routing and security
ataylor Sep 11, 2008 9:40 AM (in response to ataylor)I'm referring to the following code:
if (checkAllowable) { if (!destinations.contains(address)) { throw new MessagingException(MessagingException.ADDRESS_DOES_NOT_EXIST, "Cannot route to address " + address); } }
If we route to address a.b.* this obviously doesn't exist as an added address, how do we handle this.#
btw 3 should be ' make the check only if the address doesn't contain a wildcard.' -
3. Re: Wild Card routing and security
timfox Sep 11, 2008 10:22 AM (in response to ataylor)"ataylor" wrote:
I'm referring to the following code:if (checkAllowable) { if (!destinations.contains(address)) { throw new MessagingException(MessagingException.ADDRESS_DOES_NOT_EXIST, "Cannot route to address " + address); } }
If we route to address a.b.* this obviously doesn't exist as an added address, how do we handle this.#
I think you're misunderstanding how it's supposed to work.
You never route a message with a wildcard address, you *subscribe* with a wildcard address.
I.e. you create a subscription to com.reuters.newsfeeds.*
But messages always get routed to absolute addresses e.g. com.reuters.newsfeeds.uk.sport. -
4. Re: Wild Card routing and security
clebert.suconic Sep 11, 2008 3:30 PM (in response to ataylor)"timfox" wrote:
You never route a message with a wildcard address, you *subscribe* with a wildcard address.
Pfew!
I was wondering how wildcard routing would affect paging and routing.