Saifuddin Merchant wrote:It's thread safe, because it has no state. Any class that has no state would be fundamentally thread safe.
On a side note, why would you want to create such a wrapper, it does not offer any benefit over the usual logging API!
Thanks for the reply...The reason for this wrapper class is,we dont want to have 3rd libraray jars(com.apache.log4j) inside all over application codes and prefer to restrict to one wrapper class..so that in future if we decide to change log4j with any async implementation then the impact is only for the wrapper calss