Microsoft SDK for Java

How the VM Searches for Classes

When a class is requested, the Microsoft VM normally searches for it in the following order.

  1. Check all explicitly specified locations (typically supplied with the jview /cp option; not applicable for applets).

  2. Check the locations specified in the HKLM\Software\Microsoft\Java VM\DevClasspath registry entry.

    Note   This registry entry is provided for development and testing and may not be supported in a future release. Microsoft does not recommend relying on it for production purposes.

  3. Search packages in the Java Package Manager (JPM) marked as system packages (see the following notes).

  4. Check the locations specified in the HKLM\Software\Microsoft\Java VM\TrustedClasspath registry entry.

  5. Check the directory specified by the HKLM\Software\Microsoft\Java VM\TrustedLibsDirectory registry entry.

  6. Check the locations specified in the HKLM\Software\Microsoft\Java VM\Classpath registry entry.

  7. Check the directory specified by the HKLM\Software\Microsoft\Java VM\LibsDirectory registry entry.

  8. Check the locations specified in the CLASSPATH environment variable.

  9. Search packages in the JPM marked as non-system packages (see the following notes). Search first for non-system classes in the specified namespace, then search for non-system classes in no namespace (global namespace).

  10. If served from a Web page, the Microsoft VM additionally searches the following locations:
  11. Search the code base of the HTML file.

Notes

A package installed into the JPM must meet the following requirements to be considered a system package:

© 1999 Microsoft Corporation. All rights reserved. Terms of use.