tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <>
Subject Re: svn commit: r620848 - /tomcat/tc6.0.x/trunk/STATUS.txt
Date Wed, 13 Feb 2008 20:00:10 GMT
I thought this proposal was that at digester-configuration-time,  
trying to add the same rule twice would raise an exception.   IIUC  
you are talking about digester-runtime behavior which I think  
everyone thinks is now fine.

I'm not really familiar with digester but wondered how practical is  
is to recognize duplicate rules.

david jencks

On Feb 12, 2008, at 4:42 PM, Tim Funk wrote:

> 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:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message