Guidelines - Which Exceptions to Document
Document the following exceptions with the @throws tag:
* All checked exceptions.
(These must be declared in the throws clause.)
* Those unchecked exceptions that the caller might reasonably want to catch.
(It is considered poor programming practice to include unchecked exceptions in the throws clause.)
Documenting these in the @throws tag is up to the judgment of the API designer, as described below.
We recently changed the assignment rules to explicitly forbid the use of
NIO and the other APIs you saw mentioned on JavaRanch. However, this change
is not retroactive. If your assignment HTML document does not explicitly
forbid the use of NIO, you are free to use it.
Use of Standard Elements
Use of functionality provided by the core Java classes will be preferred to your own implementation of that functionality, unless there is a specific advantage to providing your own implementation.
Restrictions on RMI
To avoid unnecessary complexity in the marking environment certain restrictions are placed on solutions that use RMI. Specifically:
# You must not require the use of an HTTP server.
# You must not require the installation of a security manager.
# You must provide all classes pre-installed so that no dynamic class downloading occurs.
# You must use RMI over JRMP (do not use IIOP)
The user interface for this assignment must satisfy the following criteria:
* It must be composed exclusively with components from the Java Foundation Classes (Swing components).