SLF4J is widely used. Emphasis on loose coupling. It's an abstraction layer or facade (the "F" in SLF4J) that allows for switching out the implementation behind the interface (log4j, logback, JUL, etc.).
Paul Morris, Software Developer Northwestern Memorial Physicians Group<http://www.nmpg.com> 773.469.4330 | 312.926.6674 | [email protected] [cid:938FD768-5D87-4A50-BC75-A5A656FBE489] From: Roger Whitcomb <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Monday, December 3, 2012 5:38 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: Logging Probably Roger (he has created one of biggest Pivot Applications, for the Enterprise world) could say something on this ... I thought about using Log4J (which I used some years ago for a JSF web application), but eventually decided against it just for simplicity, since I had also written a small logging facility on my own in the meantime. So, we are using the homegrown one in our application. But, I'd love to see a low-overhead solution implemented for Pivot using standard libraries (that would work both for desktop and web applications). I don't have any suggestions at the moment, however. This seems like a good 2.1 feature. Do we have a JIRA issue for this? ~Roger Whitcomb This message and any included attachments are intended only for the addressee. The information contained in this message is confidential and may constitute proprietary or non-public information under international, federal, or state laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail.
<<inline: OCP_JavaSE6Programmer_clr[2][26].png>>
