Understanding extension class loading — Official

http://docs.spring.io/spring-amqp/docs/1.3.6.RELEASE/reference/html/sample-apps.html#d4e1285

http://docs.spring.io/spring-amqp/reference/html/index.html

http://docs.spring.io/spring-amqp/docs/1.4.0.M1/api/

Original text: http://docs.oracle.com/javase/tutorial/ext/basics/load.html

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:

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, i18n. jar or the installed extensions.

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.

The Java Class Loading Mechanism

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.

Here are some highlights of the class-loading API:

To see a sample application that uses some of the API as it relates to JAR files,see the lesson in this tutorial.

The above is all the official contents of understanding extension class loading collected by programming house for you. I hope this article can help you solve the program development problems encountered by understanding extension class loading.