Apology

We thought we did a decent job documenting LogDigger components, especially LogDigger Connector library (because the first public version was released about a year ago). Well, this is quite embarrassing but, thanks to a user asking for help, we’ve discovered that the LogDigger Connector manual and distribution available for download were not synchronized.

The problem was affecting those trying to save Java application logs on the LogDigger Server. If you’ve tried to do this and got an error in your your application:

java.lang.ClassNotFoundException: com.logdigger.connector.servlet.filter.LogDiggerClientFilter

well… it was our mistake, not yours. We sincerely apologize. The manual was listing class names available in LogDigger Connector 1.0.1 that renamed class RequestLoggerFilter to LogDiggerClientFilter. However, as we’ve discovered, download page was still pointing to v1.0. This is fixed now. (We’re aware that this kind of class renaming is not a good practice but we wanted to do it synchronized with the release of LogDigger Server because no one could use this class before anyway. We obviously failed to do this properly and, believe us, we’ve learned a lesson.)

We’re sorry about this omission and, if you experienced the above described problem, hope you’ll give the LogDigger Connector library one more chance. As always, feel free to contact us with any questions you may have.

One Response