Welcome to the Java Programming Forums

The professional, friendly Java community. 21,500 members and growing!

The Java Programming Forums are a community of Java programmers from all around the World. Our members have a wide range of skills and they all have one thing in common: A passion to learn and code Java. We invite beginner Java programmers right through to Java professionals to post here and share your knowledge. Become a part of the community, help others, expand your knowledge of Java and enjoy talking with like minded people. Registration is quick and best of all free. We look forward to meeting you.


Members have full access to the forums. Advertisements are removed for registered users.

Blog Comments

  1. JavaPF's Avatar
    Very interesting copeg. I have not seen Groovy before. I'll be sure to do some more reading up on it
  2. copeg's Avatar
    Thanks for this informative comment Json. You raise some great points that my post above doesn't address. Never used SLF4J but it looks very interesting.
  3. Json's Avatar
    Nice post. I tend to use logback for any logging implementation at the moment and if I'm just creating an artifact (jar) which is not supposed to create any log files etc I use SLF4J as the logging interface. Many of the bigger logging frameworks implement SLF4J so it gives the developer using my library the chance to pick his own implementation.

    Another think I came across the other week was Loggly|Logging as a Service which is a cloud based logging solution. It lets you log straight onto their machines and they index the logs for you and provide you with a nice interface for searching through them.

    I also think it's important to understand the impact of logging in a modern (possibly clustered/distributed) application. Logging can happen fast and with a lot of users using your application the disk space disappears quickly. You should also understand what you are logging and for who you are logging. This is where the levels can be really important and especially the difference between INFO and DEBUG. System administrators will most likely have access to INFO, WARN and ERROR when running in a live environment so take care with what you print out.

    Another thing to be careful about is logging sensitive information such as passwords and credit card details. If you REALLY need to log these things, you should consider blanking some of it out, such as only showing the last 4 digits of card numbers etc.

    Good article, I hope anyone reading this takes a moment to think about logging. It can be a really nice relief when debugging but it can also be the cause of major headaches.

    Keep up the nice blogs copeg.
  4. JavaPF's Avatar
    Very interesting blog post copeg. This was a good read
  5. JavaPF's Avatar
    Great blog post copeg. This knowledge is invaluable to beginners.