Best match will generally get the most specific entry then?
<destinationPolicy>
<policyMap>
<policyEntries>
<policyEntry queue=">" optimizedDispatch=”true”/>
<policyEntry queue="test.>" useCache="false"/>
<policyEntry queue="test.*" useCache="false"/>
<policyEntry queue="test.*.component" useCache="false"/>
</policyEntries>
</policyMap>
</destinationPolicy>
Which entry here would match test.example, and which would match
test.example.component? I'm guessing that test.*.component matches the later,
but which of "test.>" or "test.*" matches "test.example"?
--jason
On Jan 16, 2012, at 5:18 AM, Gary Tully wrote:
> they don't aggregate. There is an best match, and the default takes
> the unmatched case.
>
> On 16 January 2012 03:28, Jason Dillon <[email protected]> wrote:
>> On Jan 15, 2012, at 6:38 PM, SuoNayi wrote:
>>> The last policy will be applied.
>>
>> Um, this doesn't really answer the question I asked...
>>
>> What does "last" mean in this context?
>>
>> :-\
>>
>> --jason
>>
>>
>>> At 2012-01-16 04:01:00,"Jason Dillon" <[email protected]> wrote:
>>>> I'm wondering if destination policy map entries aggregate configuration?
>>>>
>>>> For example:
>>>>
>>>> <destinationPolicy>
>>>> <policyMap>
>>>> <policyEntries>
>>>> <policyEntry queue=">" optimizedDispatch=”true”/>
>>>> <policyEntry queue="test.>" useCache="false"/>
>>>> </policyEntries>
>>>> </policyMap>
>>>> </destinationPolicy>
>>>>
>>>> Will a queue named "test.example" have useCase=false and
>>>> optimizedDispatch=true?
>>>>
>>>> Same for the default policy entry, will that get included to configure
>>>> destinations which have existing policy entries, or will that only apply
>>>> to destinations where there is no entry? Some initial tests indicate it
>>>> may be the later.
>>>>
>>>> --jason
>>>>
>>>>
>>>>
>>>>
>>
>
>
>
> --
> http://fusesource.com
> http://blog.garytully.com
