[JAMES-1397] Incorrect nesting level counting for matcher mbean name

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 3.0.0-beta5
• Component/s: SpoolManager & Processors
• Assignee: Eric Charles
• Reporter: TzeKai Lee
• Created: 30/Mar/12 06:44
• Updated: 02/Apr/12 10:04
• Resolved: 02/Apr/12 10:04

Description

The nesting level in the mbean name of composite matcher is incorrect if there are more than one composite matcher in the same nesting level.
Consider this:

<matcher name="composite" match="Or">
<matcher match="And">
<matcher match="SubjectIs=example"/>
</matcher>
<matcher match="And">
<matcher match="SenderIsRegex=example.*"/>
</matcher>
</matcher>

mbean name will be
SubjectIs: <parent part>subtype2=matcher,index2=0,matchername2=SubjectIs
SenderIsRegex: <parent part>subtype3=matcher,index3=0,matchername3=SenderIsRegex
first And: <parent part>subtype1=matcher,index1=0,matchername1=And
second And: <parent part>subtype1=matcher,index1=1,matchername1=And

nesting level of SenderIsRegex should be 2 instead of 3