QFS loads the default Provider as configured in qfs_config.xml.
qfs按照qfs_config . xml中的配置加载默认提供程序。
If a Settings provider is not explicitly specified, the default provider is used.
如果未明确指定设定提供者，则会使用预设提供者。
This class is used to store the default provider in the single-provider scenario.
在单一提供者案例中，这个类别用于储存预设提供者。
This default provider uses a set of properties files located under the var/security directory.
这个默认的提供程序使用一组位于var/security目录下的属性文件。
After you have configured a site for membership, you can optionally use the default provider.
为成员资格配置了站点后，可以选择使用默认的提供程序。
For now, remove "Cloudscape" from the list of providers and add datasource of Version 5.0 for the "Default DB2" provider.
现在，从提供者列表中删除“Cloudscape”，并且为“DefaultDB2”提供者添加版本5.0的数据源。
To add a default URL provider, do the following.
按如下方法添加一个默认url提供程序。
The first step is to create the WebSphere Application Server default messaging provider topic space, as shown in Figure 3.
第一步是创建WebSphereApplicationserver缺省消息传递提供程序主题空间，如图3所示。
The highlighted code in Listing 4 authenticates the user against the Geronimo container's default JAAS provider before allowing access to the Web application.
清单4中突出显示的代码可以根据geronimo容器的默认JAAS提供程序对用户进行身份验证，这一过程是在其访问Web应用程序之前完成的。
When you edit an application client EAR file, you discover that the WebSphere J2EE application client runtime environment does not supply a default URL provider as does the application Server.
当您编辑客户端应用程序的EAR文件时，您会发现WebSphereJ2EE客户端应用程序运行时环境将不像在Application Server中那样提供一个默认url提供程序。
You must create these resources under the default messaging provider within the node scope.
您必须在节点范围内，默认消息提供者下创建这些资源。
When the Event Service is configured, the Event Service MDB for the default messaging provider is installed along with all resources to receive Events asynchronously.
当配置事件服务时，缺省消息传递提供者的事件服务MDB与所有资源一起安装，并以异步方式接收事件。
You can now run the application client and access the URL resources defined for the default URL provider.
现在，您可以运行客户端应用程序并访问为默认url提供程序定义的URL资源。
The JMS binding delivers the request to a default messaging provider topic space.
JMS绑定将该请求传递到缺省消息提供程序主题空间。
If you are using MQ rather than the default messaging provider, you should of course use SSL to MQ.
如果您使用的是mq而非缺省的消息传递提供程序，则当然应该对MQ使用SSL。
For the supplied JMS application, the following JMS resources will be defined using the default messaging provider.
对于提供的JMS应用程序，将使用缺省消息传递提供者来定义下面的JMS资源。
According to the JAX-RS specification, by default, provider and resource classes are instantiated once for each JAX-RS application.
根据JAX -RS规范，默认情况下，提供者和资源类为每个JAX - RS应用程序实例化一次。
Leave the JMS provider to the Default messaging provider and specify user id and password to access it.
将JMS提供程序保留为缺省消息传递提供程序，并指定访问它的用户ID和密码。
Add the default URL provider and resource definitions, as described in the previous section, to the application client EAR using the ACRCT.
按照上面的讲解，使用ACRCT向应用程序客户端ear添加默认url提供程序和资源的定义。
Just as with the tree viewer, if you don't explicitly set the label provider on the table viewer, it USES the default label provider.
和树查看器一样，如果不显式地给表查看器设置标签提供程序，它就会使用缺省的标签提供程序。
The implementation class name and class path you see are the default for the DB2 JDBC provider.
您看到的实现类名和类路径都是DB 2JDBC提供程序所默认的。
Resources for the default messaging provider.
默认消息提供者的资源。
As for the other details, Tuscany is using ActiveMQ as it's default JMS provider but can be configured to use different providers as well, so some details would depend on the provider being used.
至于其他细节，Tuscany使用Active MQ作为其默认的JMS提供者，但是也可以配置以使用不同的提供者，因此一些细节依赖于所使用的提供者。
We began the original WebSphere application server ESB article series with an example showing how the System Integration Bus (SIBus) ACTS as the default JMS provider for the application server.
我们首先通过一个示例开始了最初的WebSphereApplicationServerESB系列文章，介绍系统集成总线(SIBus)如何作为应用服务器的缺省JMS提供程序。
If you are using WebSphere MQ rather than the default messaging provider, you should of course use SSL to WebSphere MQ.
如果您使用的是WebSpheremq而非默认的消息传递提供者，当然应该对WebSphere MQ使用SSL。
If the messaging engine is running on a remote application server, then the default messaging provider will use the LTPA support to flow the information contained in the Subject to the remote process.
如果消息传递引擎在远程应用服务器上运行，则缺省消息传递提供程序将使用LTPA支持来将Subject中包含的信息传递给远程进程。
What we have done is taken a copy of an existing Subject, that has been authenticated by the application server, and sent it to the default messaging provider.
我们所做的是复制现有的Subject(已经通过了应用服务器身份验证)并将其发送到缺省消息传递提供程序。
This works because the default messaging provider is part of the application server and can understand the format of a Subject authenticated by the application server.
这之所以有效，是因为缺省消息传递提供程序是应用服务器的一部分，可以理解通过了应用服务器身份验证的Subject的格式。
This article describes the basic technique for creating publish/subscribe interaction patterns using JMS bindings with the WebSphere Application Server default messaging provider as the JMS provider.
本文描述使用JMS绑定并将WebSphereApplicationServer缺省消息传递提供程序用作 JMS 提供程序来创建发布/订阅交互模式的基本技术。
This article describes the basic technique for creating publish/subscribe interaction patterns using JMS bindings with the WebSphere Application Server default messaging provider as the JMS provider.
本文描述使用JMS绑定并将WebSphereApplicationServer缺省消息传递提供程序用作 JMS 提供程序来创建发布/订阅交互模式的基本技术。
应用推荐