In that case - that would revert the functionality which caused the
issue to arrive in the first place.
The original bug had a problem because they had the same listener class
declared multiple times and it was only being fired once. The fix was to
log a duplicate listener message on the user config error.
It turns out that WebRuleSet was also adding the same item twice.
(accidently) and so the duplicate message was being.
So if the digester rules are changed to ignore dups - the original bug
fix would then be invalid and the user would again silently wonder why
only one instance is being used.
-Tim
jean-frederic clere wrote:
Tim Funk wrote:
Not sure if I understand the question, the problem is our use of
digester. We had 2 listener rules being created and each called
addListener. So when an a <listener> was found - it was being
processed twice.
Yes. My idea was to prevent add twice the same rule in Digester
additionally to the actual fix.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
