MCL1 is a child of the system class loader, and MCL2 is a child of MCL1.
mcl1是系统类装入器的孩子，mcl2是mcl1的孩子。
In Listing 6, the UnsatisfiedLinkErrorTest class is loaded by the system class loader.
在清单6中，unsatisfiedlinkerrortest类是由系统类装入器装入的。
This is because B is not in the classpath of the system class loader or its parent or ancestor class loaders.
这是因为B不在系统类装入器或者它的双亲或祖先类装入器的类路径中。
Here, we use reflection because we have loaded the application using a class loader that is not the system class loader.
这里，我们使用反射的原因是因为我们已经使用非系统类加载器加载了应用程序。
Instead, it has a set of class loaders that are unrelated except that they have the same parent (usually the system class loader).
相反，它有一组类装入器，彼此互不相关，但是有共同的双亲(通常是系统类装入器)。
If these classes are available in the classpath, the parent of the URLClassLoader instance, which is the system class loader, will load them.
如果这些类在类路径中可用，URLClassLoader实例的父加载器(即系统类加载器)将加载它们。
The problem with this approach is that the LogManager instance uses the system class loader to instantiate classes from the configuration file.
这种方法的问题是LogManager实例使用了系统类的装载程序从配置文件中对类进行实例化。
For instance, classes in the system class loader class space should not refer to classes in the class space of a child or a descendant class loader.
例如，在系统类别载入器类别空间中的类别，不应当指向孩子或子孙类别载入器的类别空间中的类别。
Class a is on the classpath of the system class loader, and a's superclass, B, is on the classpath of a user-defined class loader, which is a child of the system class loader.
类a在系统类装入器的类路径中，而A的超类b，在用户自定义的类装入器的类路径中，这个类装入器是系统类装入器的孩子。
To avoid this problem, any classes that are to be serialized should be loaded by a class loader that does not need to be garbage collected — by the system class loader, for example.
为了避免这个问题，凡是要进行序列化的类，都应当由不需要被垃圾收集的类装入器装入——例如由系统类装入器装入。
The system class loader (also known as the application class loader) is the class loader responsible for loading code from the path specified by the CLASSPATH environment variable.
系统(system)类装入器(也称作应用程序类装入器)负责从CLASSPATH环境变量指定的路径装入代码。
While the simplest way to avoid class loader constraint violations is to only have one copy of a class in the system, it is sometimes necessary to have multiple versions.
虽然避免类装入器约束违反的最简单方法是在系统中只有类的一个副本，但有时拥有多个版本也是有必要的。
The easiest way to resolve this problem is to ensure that there is only one copy of a class in the system — that is, that the class only appears in the classpath of one loader.
解决这个问题的最简单方法是确保在系统中只有类的一个副本——也就是说，类只出现在一个类装入器的类路径中。
I like things that don't take up very much code, so Maypole currently uses a model class system based on Class::DBI::Loader.
我喜欢不用很多代码就能实现的东西，因此Mayple当前使用了一个基于Class::DBI::Loader 的模型类系统。
So whilst in a traditional application, classes from a logging library, a client and server JAR may be loaded by the same class loader, in an OSGi module system, each would be loaded by their own.
因此，尽管在传统应用中，来自logging类库、client和serverJAR中的类都是由同一个类加载器加载的，但在OSGi模块系统中，他们都是由自己的类加载器加载的。
This class loader loads the core system classes from the boot classpath, which is normally the JAR files located in the jre/lib directory.
这个类装入器可以从启动的类路径装入核心系统类，通常是位于jre/lib目录的JAR文件。
The Classloader summaries section provides details about each class loader in the system, including the type of the class loader.
Classloader汇总部分提供了系统中每个类装入器的细节。
The Classloader summaries section provides details about each class loader in the system, including the type of the class loader.
Classloader汇总部分提供了系统中每个类装入器的细节。
应用推荐