DocTree was created by a small Java program that uses a predefined list of web based JavaDoc URLs which it indexes to generate an XML index file. The same program can also search a filesystem local JavaDoc sets. The XML index file details projects and the packages and classes defined in those projects. It then uses some XSL transforms to generate this web page, and all the dynamically included web page fragments to speed up page loading (and to keep Internet Explorer from falling over).

Check out the Java DocTree.

Adding search option would make it as good as Google except for the performance.

Joogle (JavaDocs + Google) ?

http://joogle.sourceforge.net

A better link to joogle
http://javadoc.dyndns.org/joogle/

Awesome tool but it seems to have a lot of little misc projects that I've never heard of while missing several very popular projects. It would be more useful to a broader range of developers if it had more apache packages (struts, lucene, axis, etc) and ALL the java and javax packages. Specifically I noticed it was missing the JDBC javadocs.

Many of the projects that you mention are there - the JDBC pacakges are java.sql and javax.sql, and struts and lucene are under org.apache.

I'm about to do an upadate that includes axis and a bunch of other requested projects. JavaDocs for some of these projects were hard to find - Axis and Ant for example, and I'm not sure that I have the best place for Eclipse/SWT yet either, but I think we now include all major projects. Shourt if you know of any missing.

Search page says type in Class or Package.

String failed.
StringBuffer failed.

java.util.StringBuffer worked.

Would be worth a whole lot more to me if all I had was a class name and it showed me the packages that contained that class.

I'll stick with the standard google query for now:
  <Usually gets the javadoc page I'm looking for on the first try.

I've been using Classfinder (http://www.roblisa.com/classfinder/) which works very well. It runs as a local webserver on your box, and you simply package up the javadoc for a project and throw it in a deploy directory. It then allows you to navigate the docs as one linked Javadoc structure, and is searchable. If you have the source code, then you can throw that in as well and it'll allow you to switch between the source and the doc.