Hello My scenario demands a clear demarcation of log files for different services and these services may be provisioned at run-time. This calls for creating "loggers" and a default file appender with a defaul log level and ideally would prefer the newly created properties to be persisted back into the configuration file. So the next time the admin has a chance to modify the properties file in which case that would be taken into effect. Its mostly a convenience feature to "generate" properties from default when needed.
Another requirement was to be able to trace the method call and stick it in the log message automatically which I managed to implement using Throwable.printStackTrace and sub-classing Logger I managed to implement the first requirement as well but did it in a hurry and had to carefully loop through appenders,etc and was wondering if this has ever been investigated or already implemented?? the log4J index page states : "...strongly discourage casual users from sub-classing Logger/Category". May I ask why? and what are the implications? Is my case an exception or is there a better way to do it? thanks rajiv -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
