图5.类库加载器选项对话框。
您控制了父-子、子-父委托的类加载器。
You control the classloader for parent-child child-parent delegation.
多个单例对象被不同的类加载器同时加载。
Multiple singletons simultaneously loaded by different class loaders.
在加载时，系统加载器加载相应位的内核扩展。
At load time, the system loader then loads the bit-appropriate kernel extension.
修改类加载器结构应该使应用程序能够成功迁移。
Modifying the classloader structure should allow the application to migrate successfully.
展示JIT编译、类加载器信息和垃圾收集的图形。
Graph showing JIT compilations, class loader information, and garbage collection.
类加载器的父类加载器将是当前线程上下文的类加载器。
The parent of this class loader will be the class loader of the current thread context.
目前，加载器会把代码的内部表示返回给Ruby来执行。
Currently the loader passes the internal representation of the code back to Ruby for execution.
某些引导文件必须可被BIOS或引导加载器在引导时访问。
Some files must be accessible to the BIOS or boot loader at boot time.
然后加载器载入这些库，并调用相应的_ init部分。
These libraries will then be loaded by the loader, and the corresponding _init sections will be called.
类加载器实例加载的类由加载器的名称空间和类名惟一标识。
A class loaded by a class loader instance is uniquely identified by that class loaders namespace and the class name.
这里我们使用应用程序名作为类加载器的名称，以避免重复。
Each EAR application should have a unique string name for the class loader. Here, we use the application name in the class loader name to avoid repetition.
回忆一下，我们编写了3块代码：任务代码、加载器和聚合器。
As you'll recall, there were 3 pieces of code to write: task code, a loader, and an aggregator.
然后选择创建的类加载器并单击libraries链接。
Then select the created classloader and click the libraries link.
第一种方法是在出现大量类加载器时鼓励进行额外的保留区收集。
The first is to encourage additional tenure collections in the presence of large amounts of class loaders.
你需要安装RubyEncoder加载器来运行被保护的脚本。
RubyEncoder Loader needs to be installed to run protected scripts.
例如，假设您有一个名为MyClassLoader的类加载器。
For example, suppose you have a class loader called MyClassLoader.
这些任务保存在云存储上的任务队列中（加载器把任务放到这个队列中）。
These tasks are still sitting in the task queue in cloud storage where the loader put them.
它还展示了类加载器信息——再说一遍，这很简单，因为应用程序太简单了。
It also shows class loader information — again, this is simple because the application is so simple.
当应用程序重启但它们的类加载器没有清理时，将发生应用程序类加载器泄露。
An application class loader leak occurs when applications are restarted but their class loaders are not cleaned up.
如果类加载器几乎没有定义任何的类实例，那么这个类加载器很可能是空闲的。
If next to no instances of classes are defined by a classloader, then it is likely that the classloader is idle.
插件的类加载器(classloader)负责在它的库中解析对类的引用。
It is the responsibility of a plug-in's classloader to resolve references to classes within its libraries.
这里，我们使用反射的原因是因为我们已经使用非系统类加载器加载了应用程序。
Here, we use reflection because we have loaded the application using a class loader that is not the system class loader.
这一点，再加上每个应用服务器中的不同类加载器实现，会为迁移带来潜在的问题。
This, combined with the different class loader implementations in each application server, can potentially create problems when migrating.
这样做可行，是因为云存储中的队列是网格执行器和企业加载器/聚合器的通信机制。
This works because the queues in cloud storage are the communication mechanism between grid workers and the enterprise loader/aggregator.
FOCAL系统是作为用于二进制加载器格式的纸带图像而提供的(请单考清单6)。
The FOCAL system is provided as a paper-tape image used in the binary loader format (see Listing 6).
同样，不能加载这些JAR文件的多个版本，因为类都位于系统类加载器名称空间中。
Also, you will not be able load multiple versions of these JAR files as the classes will all be in the system class loaders namespace.
真正的实现可能需要其他自定义类加载器，该加载器将搜索为编译提供的某些类路径。
A real implementation may need another custom class loader that would search through some classpath provided just for the compilation.
当类加载器存在一个层次结构时，根类加载器(即引导类加载器)将首先尝试加载类。
When there is a hierarchy of class loaders, the root class loader, which is the bootstrap class loader, attempts to load the class first.
因而，虽然加载器让编写安全的程序成为 可能，但您还不得不去防范恶意的环境变量。
Thus, the loader makes it possible to write secure programs, but you still have to protect against malicious environment variables.
应用推荐