Well, I'm not part of the development team, but it looks like it would be 
fairly straightforward to do what you suggest. I'd recommend both A and B. 
Have the appender look first for a name generation class; if that's not 
provided then use a pattern string; if that doesn't exist default to the 
current behavior. I'd even be willing to implement such a thing if the dev 
team would like some help - I could combine it with my extension that 
recognizes compressed extensions.

Skip


"Auinger, Thomas" <[EMAIL PROTECTED]> wrote:
>Hi!
>
>I wrote this message several weeks ago, but didn't get a single
>reply..
>
>Could anybody in the developing team please comment on this request?
>
>Thanks,
>Thomas
>
>
>> -----Ursprüngliche Nachricht-----
>> Von: Auinger, Thomas
>> Gesendet: Mittwoch, 25. September 2002 11:30
>> An: 'Log4J Developers List'
>> Betreff: RFE: provide a way to specifiy the names of the
>> RollingFileAppend er's backup files
>>
>>
>> Hi!
>>
>> In the current implementation, the RollingFileAppender always
>> names backup files to "<filename>.1", "<filename>.2" etc.
>>
>> It would be great, if developers could add their own naming
>> convention.
>>
>> This could be done using different ways (I think):
>>
>> a) The developer sets a naming pattern String as a parameter
>> to the RollingFileAppender, which defines the filename (similar
>> to PatternLayout), e.g. "%f.%d.%n", where %f = filename, %d = date,
>> %n = backupIndex
>>
>>
>> b) The developer implements an interface, which provides a
>> single method to generate a filename for a backup file:
>>
>>  public interface BackupFilenameResolver {
>>
>>      public String getFilename( int backupIndex );
>>
>>  }
>>
>> An implementing class name of this interface may then be set
>> as a parameter to the RollingFileAppender (similar to how
>> ObjectRenderers are currently configured)
>>
>>
>> I would prefer soultion (b), since it is more flexible.
>>
>>
>> Greetings from Germany,
>>  Thomas
>>
>> --
>> To unsubscribe, e-mail:
>> <mailto:[EMAIL PROTECTED]>
>> For additional commands, e-mail:
>> <mailto:[EMAIL PROTECTED]>
>>
>
>--
>To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail: 
<mailto:[EMAIL PROTECTED]>
>

Reply via email to