Wild Card routing and security

[ataylor]

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:

1. remove the check.
2. only make the check if wild card routing is disabled.
3. make the check only if the address contains a wildcard.

wdyt?

[timfox]

"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?

[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.'

[timfox]

"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.

[clebert.suconic]

"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.