Obtaining access to Logger using a different Mechanism

[Ravi Kiran Va]

Hi, we are using a Log4j to implement Logging Mecanism in our Application .

we are not using

Logger log = Logger.getLogger(Someclass.class)

to obtain access to Log4j



Instead we used an SomeLogger class taht will return the instance of the Logger as shown below .

Logger log = SomeLogger.getLogger(Someclass.class)

A code snippet of this SomeLogger is shown below :

public final class SomeLogger 
{

public static Logger getLogger(Class pClazz) {
		return Logger.getLogger(pClazz);
}

}

What is the advantage we get if we use this way ??

Thanks in advance .

[Jaikiran Pai]

I don't see a reason why that SomeLogger class is required. Does it have any javadoc or anything else which explains why it's there?

[Ravi Kiran Va]

Thanks Jai for the response .

This might be useful to provide me a better response , this is the only code
// This code is getting the log4j.properties path

public final class SomeLogger {
		
	private static void init()
	{
		
	try
			{
Properties prop = ConfigManager.getConfiguration(Constants.LOG4J_PROPERTIES_FILE_PATH);
			}
	
	static {
		init();
	}
}

[Paul Sturrock]

Isn't that class pointless? Why have you chosen to not use the out the box mechanisms for loading your log4j configuration?

[David Newton]

Yeah, unless there's other magic going on, or you really, really need to have your logging properties specified as a string constant, there are better, easier, more conventional ways of doing this.