Hi Scott, What is the relationship between a finalizer being public and JMX support? As an issue in its own right, a public finalizer isn't inherently bad. In the cases I've done it, I make sure that it is capable of being called repeatedly without ill effects (I haven't looked at the AppenderSkeleton code in a while to see if this is true). This may be desirable in cases where one can't expect the JVM to call the finalizer method.
- Paul Paul Glezen Consulting IT Specialist IBM Software Services for WebSphere 818 539 3321 Scott Coleman <[EMAIL PROTECTED]> on 11/02/2001 02:40:46 AM Please respond to "Log4J Developers List" <[EMAIL PROTECTED]> To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> cc: Subject: Re: Question We have just started using log4j, an excellent logging framework. We are extending it adding some appenders, but i am confused as to why the finalize method in the AppenderSkeleton class is public. I would have thought that this should be protected as this method should not be part of the public interface of the class. Can someone explain to me why it is public? The reason i ask is that i am trying to add JMX configuration, but i have just looked through the newsgroups mail archive and found that some JMX support is already being added. -- 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]>
