Code Comments

Make sure you comment your code where it isn't clear what is happening. Don't go too far with this, however, and add trivial comments. If the reader needs more than 20 seconds to understand a piece of code, explain it in a succinct comment. Throughout your project, use a mix of inline, trailing, end-of-line, and javadoc comments. The point total for comments in the grading portion of the instructions understates how much poorly commented code can affect your overall grade.

Javadoc

Chapter 5, "Documentation and Javadoc Comments," explains how to use comments in your project so that you get high marks for the documentation portion of your grade.

You must be careful to read the javadoc comments in Sun's supplied code for requirements and hints. At least one requirement is buried in there (hint: tracking the client ID for locking and unlocking database records).