Hi, > Unfortunately having both activate (overriden by internal appenders) > and activateOptions (overriden by existing custom appenders) can make > it extremely complicated to have a complex appender that performs the > exact same actions for both activate() and activateOptions(). I have > no problem with AppenderSkeleton.activate being a final method that > invokes AppenderSkeleton.activateOptions.
Yup, that's fine too. Yoav --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
