Howdy, >One idea here. Don't use the Log4J implementation >directly. Make an adapter layer that calls Log4J >internally. Then your programs call the logging >methods of your adaptors to log. The adaptors would >compile and ship with your code. In side the adaptors >you would use reflection to access Log4J. In this way >you can choose to ship the Log4J jar or not. Also the >adaptors could access other logging systems if needed. > Since everything uses reflection there would not be >any compile errors if any jars are not present.
Make sure to test the performance of this approach if you choose to try it... Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
