{"id":381,"date":"2007-10-21T00:00:00","date_gmt":"2007-10-21T00:00:00","guid":{"rendered":"http:\/\/www.strongd.net\/?p=381"},"modified":"2007-10-21T00:00:00","modified_gmt":"2007-10-21T00:00:00","slug":"Understanding Extension Class Loading","status":"publish","type":"post","link":"https:\/\/www.strongd.net\/?p=381","title":{"rendered":"Understanding Extension Class Loading"},"content":{"rendered":"

Understanding Extension Class Loading<\/DIV>
\n
The extension framework makes use of the class-loading delegation mechanism. When the runtime environment needs to load a new class for an application, it looks for the class in the following locations, in order:
\n

    \n
  1. Bootstrap classes<\/B>: the runtime classes in rt.jar<\/TT>, internationalization classes in i18n.jar<\/TT>, and others. <\/LI>
    \n
  2. Installed extensions<\/B>: classes in JAR files in the lib\/ext<\/TT> directory of the JRE, and in the system-wide, platform-specific extension directory (such as \/usr\/jdk\/packages\/lib\/ext<\/TT> on the SolarisTM<\/SUP><\/FONT> Operating System, but note that use of this directory applies only to JavaTM<\/SUP><\/FONT> 6 and later). <\/LI>
    \n
  3. The class path<\/B>: classes, including classes in JAR files, on paths specified by the system property java.class.path<\/TT>. If a JAR file on the class path has a manifest with the Class-Path<\/CODE> attribute, JAR files specified by the Class-Path<\/CODE> attribute will be searched also. By default, the java.class.path<\/CODE> property’s value is .<\/CODE>, the current directory. You can change the value by using the -classpath<\/TT> or -cp<\/TT> command-line options, or setting the CLASSPATH<\/CODE> environment variable. The command-line options override the setting of the CLASSPATH<\/CODE> environment variable. <\/LI><\/OL>
    \n

    The precedence list tells you, for example, that the class path is searched only if a class to be loaded hasn’t been found among the classes in rt.jar<\/TT>, i18n.jar<\/TT> or the installed extensions. <\/P>
    \n

    Unless your software instantiates its own class loaders for special purposes, you don’t really need to know much more than to keep this precedence list in mind. In particular, you should be aware of any class name conflicts that might be present. For example, if you list a class on the class path, you’ll get unexpected results if the runtime environment instead loads another class of the same name that it found in an installed extension. <\/P><\/BLOCKQUOTE>
    \n

    The Java Class Loading Mechanism<\/H3>
    \n
    The Java platform uses a delegation model for loading classes. The basic idea is that every class loader has a “parent” class loader. When loading a class, a class loader first “delegates” the search for the class to its parent class loader before attempting to find the class itself.
    \n

    Here are some highlights of the class-loading API: <\/P>
    \n