首先是一个xml文件CustomBindingProvider . xml，该文件中声明了工具和运行时定位绑定器所需的全部信息。
The first is an XML file, CustomBindingProvider.xml, that declares all the necessary information for the tooling and runtime to locate the binder.
在WebSphere运行时中，它将搜索classpath以获得所有可用的自定义绑定器。
In the WebSphere runtime, it searches the classpath for the available custom binders.
应用服务器运行时使用这些绑定来确定是否向特定的用户授予了某个角色，然后决定是否可访问受保护的资源。
The application server runtime USES these bindings to determine if a specific user has a role assigned, and then decides whether or not the protected resource can be accessed.
但是通过使用REOPT绑定选项，优化器将会根据应用程序在运行时所提供的值来生成存取计划，而不是使用绑定过程中创建的一般计划。
But with the REOPT bind option, the optimizer will generate an access plan against the value provided by the application during runtime, instead of using the generic plan created during bind.
同样地，运行时也会定位到自定义绑定器并使用所需的绑定器来执行其功能。
Similarly, the runtime locates the custom binders and USES whatever binders it needs to perform its function.
在1.0发行版中，绑定编译器的尺寸是运行时的4倍(228k比54k)，复杂性则高出许多倍。
In the 1.0 release, the binding compiler is more than four times the size of the runtime (at 228k vs. 54k) and many times the complexity.
绑定编译器将JiBX 绑定代码添加到您的类文件，编译它们以在 JiBX运行时使用。
The binding compiler adds JiBX binding code to your class files, preparing them for use with the JiBX runtime.
WebSphere运行时和工具在开发时和运行时均使用自定义绑定器。
The WebSphere runtime and tooling USES of the custom binders at development time as well as runtime.
副本的绑定信息保存在配置中，并在运行时动态获得，所以添加冗余服务器只需更新配置，不用修改源码。
The binding information for replicas is kept in configuration and is dynamically acquired at runtime, so adding a redundant server requires only a configuration update, not changes in source code.
动态绑定使编译器能够在运行时决定是使用基类中定义的函数还是派生类中定义的函数。
Dynamic binding lets the compiler determine at run time whether to use a function defined in the base or derived class.
动态绑定使编译器能够在运行时决定是使用基类中定义的函数还是派生类中定义的函数。
Dynamic binding lets the compiler determine at run time whether to use a function defined in the base or derived class.
应用推荐