Four occasions when Jarhoo may be of help to Java developers...

When getting a ClassNotFoundException or NoClassDefFoundError

Enter the fully qualified class name of the class causing the problem into Jarhoo and perform a search. If the class name is in our database the results will display any jar files containing the class, which applications contain the jar file, and where in each application the jar file is located

When writing import statements

Enter the name of the class into Jarhoo (eg. Collection) and perform a search. The results will display any class names in our database matching this name, including the fully qualified package name of each class. This fully qualified name can be pasted into code to aid with import statements. This feature is particuarly useful for those new to Java who may need help learning the package structures

When wanting to browse the package structure of an application

Enter the name of the package to be browsed (eg. java.util) into Jarhoo and perform a search. If the package is found in our database the contents of the package will be displayed with links allowing these sub-elements to be browsed further.

When wanting to find which applications contain a particular jar file

Enter the name of the jar file into Jarhoo (eg. rt.jar) and perform a search, ensuring that you check the radio button above the search box for "Jar File Name". If the jar file is found in our database the results will display which applications contain the jar file, and where in each application the jar file is located

Please note...

All searches are case sensitive

We are only able to allow package browsing or searches for non-qualified class names within Open Source applications or applications with a publically available API. Searches can still be performed within other applications (allowing class not found exceptions to be resolved), provided the fully qualified class name is entered or a jar file search is performed

Searches for fully qualified class names or jar file names perform much quicker than generic searches (for package names or non-qualified class names) as we have to check permissions within all the possible tables in our database. Generic searches at the time of writing may take up to 10 seconds to complete.