Tim Moyle

It's there in every how-to-learn-Java book you pick up, right in the first chapter: a brief section about documenting your Java code. Like any good programmer, you probably flipped through those pages pretty quickly and said, "I'll get back to this later." But you never did, did you? No. Instead you plunged right into writing cute little applets and then bigger applications and pretty soon you were a Java guru. Documentation was never part of the deal. It's time for you to get back to thinking about Java documentation. Recent trends in the Java marketplace are making Java documentation more and more necessary. The rise in demand for application servers and third-party Enterprise JavaBeans means that there will be a lot of developers working with code that they didn't write themselves. If the primary benefit of using EJBs is a reduction in development time, then a l... (more)