activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Davies <rajdav...@gmail.com>
Subject Re: How to use destination wildcards to match a common suffix
Date Sat, 11 Apr 2015 11:05:59 GMT
ooh - that's nice.

On 11 April 2015 at 11:32, Martin Lichtin <lichtin@yahoo.com.invalid> wrote:

> Hi James, yes that'd be a great extension, and I could easily adjust my
> naming convention to make use of it.
>
>
> On 11.04.2015 12:01, James Carman wrote:
>
>> Martin,
>>
>> Does this satisfy what you're looking to do:
>>
>> https://issues.apache.org/jira/browse/AMQ-5717
>>
>> There is a PR available which implements it:
>>
>> https://github.com/apache/activemq/pull/85
>>
>> Basically, instead of using ">" which to me looks like an arrow
>> meaning "anything to the right", you would use a "<" character, which
>> would mean "anything to the left."  For example, <.out would match
>> anything ending in .out.  Now, the paths match on full segments, so
>> the entire last segment would need to be "out", but I would imagine
>> you could adjust your naming conventions to match that, right?
>>
>>
>> On Thu, Apr 9, 2015 at 4:21 AM, Martin Lichtin
>> <lichtin@yahoo.com.invalid> wrote:
>>
>>> I read http://activemq.apache.org/wildcards.html but am still puzzled
>>> about
>>> how to write a pattern that matches queue names with a particular suffix.
>>>
>>> For example, for queue names such as A.B.Cout and D.E.Fout will
>>>
>>>      <redeliveryPolicy queue="*out"
>>>
>>> be enough to match the queues? Or do I need
>>>
>>>      <redeliveryPolicy queue=">*out"
>>>
>>> or something else even?
>>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message