As a final step, the service provider deploys the code in a service container (application server, SOAP server), so that it can be accessed preferably using SOAP over HTTP.
最后一步是，服务提供者将代码部署到服务容器(应用服务器、SOAP服务器)中，这样就可以首选使用HTTP上的SOAP访问代码。
The managed objects created by the provider contain similar auto-enlistment code as the JDBC wrapper added by the container-supplied connection pool manager.
提供者创建的受管对象包含与JDBC包装器（由容器提供的连接池管理器添加）相似的自动征用代码。
This declares the configuration for Ext.app.REMOTING_API, which you then use as your provider when you try to use the exposed methods in your code.
这声明了 Ext.app.REMOTING_API配置，当您在您的代码中试着使用公开的方法时，您可以将其作为您的提供者使用。
The above code will add the Sun JCE provider as the last-approved security provider in the security registry.
上面的代码将添加sunJCE提供者作为安全性注册表内最后一个被批准的安全性提供者。
In general, code that explicitly indicates a provider URL should be changed to instead get this value implicitly from the environment, as recommended by the J2EE specification.
一般说来，应该像J2EE规范中推荐的那样，明确地显示提供者url的代码应该改为隐含地从环境中获取URL的值。
As you develop your code you should work hard to avoid provider-specific dependencies.
当您开发您的代码时，应该尽量避免程序提供者所特有的依赖。
The "edit Code" generator creates the plug-in infrastructure to edit the model that is the plug-in.xml, META-INF directory, and provider classes as the ItemProvider and the EditPlugin.
“EditCode”生成器会创建插件基础，以编辑plug - in . xml的模型，META - INF目录，并提供作为ItemProvider和EditPlugin的类。
The code snippet in Listing 2 shows the createPartControl() method of a view that creates a JFace TableViewer and adds it as a selection provider to the workbench site.
清单2中的代码片段显示一个视图的createPartControl()方法，这个方法创建一个JFaceTableViewer并将它作为选择提供器添加到工作台站点。
The feature-level provider then reads in the type from the configuration file and ACTS as a factory to the feature code.
接着，功能级别的提供程序会读取来自配置文件的类型，并充当功能代码工厂。
The feature-level provider then reads in the type from the configuration file and ACTS as a factory to the feature code.
接着，功能级别的提供程序会读取来自配置文件的类型，并充当功能代码工厂。
应用推荐