Stub jca — is used to generate a Record class for J2C applications.
stubjca——用于生成J2C应用程序的record类。
The resource model differs from the standard JCA implementation by including OLAP-style interactions.
资源模型不同于标准的JCA实现，因为它包括了OLAP 风格的交互。
We have not yet written JCA/JCE-related classes.
我们还没有编写与 JCA/JCE 相关的类。
A few capabilities that the JCA specification does not address will be included in the IBM JCA-compliant WebSphere Business Integration adapters.
一些JCA规范没有实现的功能将被包含在符合IBMJCA的WebSphereBusinessIntegration适配器中。
JCA resource adapters support two-way communication between the J2EE components and eis.
JCA资源适配器支持J2EE组件和EIS之间的双向通信。
JCA 1.5's transaction-inflow contract lets an enterprise information system (EIS) act as the transaction coordinator by starting and completing the transaction.
JCA 1.5的事务流入合约允许企业信息系统(EIS)启动和完成事务，充当事务的协调者。
Usually, you would choose the version in the cics15 or ims15 directories, which contain JCA 1.5-compliant adapters.
您通常会选择cics15或ims15目录中的版本，该版本包含与JCA 1.5兼容的适配器。
MQSeries/JCA/CCF: Existing mainframe-based services can be exposed as web services, thus revealing them to the outside world.
MQSeries/JCA/CCF：现有的基于主机的服务可以公开为Web 服务，从而向外界展示它们。
You've seen how the JCA message-inflow contract can be used to configure a resource adapter so that it can retrieve instances of, and invoke methods on, an MDB.
您已经看到如何用JCA 消息输入流合约来配置资源适配器，以便用它来检索MDB实例以及调用 MDB上的方法。
The initial JCA release provided a detailed life-cycle model for managed connections and their associated connection handles, but it included no such concept for the resource adapter as a whole.
最初的JCA版本为托管连接及其相关联的连接句柄提供了详细的生命周期模式，但是它没有为资源适配器提供这种概念。
These tools also have extensive support for J2EE Connector Architecture (JCA), which is vital for access to existing non-relational EIS systems.
这些工具也广泛支持J2EE连接器体系结构(J2EE Connector Architecture (JCA))，JCA对于访问现有的非关系型EIS系统很重要。
In the third and final article of this series, I'll cover the JCA 1.5 message-inflow contract, better known as message-driven bean support.
在本系列的第3篇也是最后一篇文章中，我将介绍JCA 1.5消息流入合约，它比较出名的地方是对消息驱动bean的支持。
V6-compatible applications are those applications that only run within a V6 environment, and include J2EE 1.4 applications, JCA 1.5 adapters, and any applications that call new APIs introduced in V6.
与版本 6兼容的应用程序是只在版本 6 的环境中运行的应用程序，包括J2EE 1.4 应用程序、JCA 1.5适配器和任何调用版本 6中新增的API 的应用程序。
You can deploy a JCA-compliant resource adapter to any J2EE-compliant application server.
您可以将遵循jca的资源适配器部署到任何遵循j2ee的应用程序服务器。
Thus, we can describe all of the JMS- and JCA-specific information about a service in the protocol binding part of the WSDL definition.
这样，我们就可以在WSDL定义中的协议绑定部分描述关于服务的所有特定于JMS和特定于JCA 的信息。
Techniques described in this article can be implemented with any application server that is compliant with J2EE 1.3 or higher, as well as both JCA 1.0- and JCA 1.5-compliant resource adapters.
任何与J2EE 1.3以及更高版本兼容的应用服务器，以及与JCA 1.0 和 JCA 1.5 都兼容的资源适配器，都可以实现本文描述的技术。
The JCA 1.5 specification has a solution: lazy enlistment.
JCA 1.5规范提供了一个解决方案：惰性征募。
Specification defined: Activation specifications are part of a standards specification (JCA 1.5).
定义的规范：激活规范是标准规范(JCA 1.5)的一部分。
It assumes a basic knowledge of both CICS and the JCA.
本文假设您了解CICS和JCA方面的基础知识。
Subsequently, other specifications were published to extend the features provided by JCA.
随后又发布了其他一些规范，以扩展JCA提供的特性。
The primary principle of JCA design is to separate cryptographic concepts from algorithmic implementations, so that different vendors can offer their tools within the JCA framework.
JCA设计的主要原理是将密码概念从算法实现中分离出来，以便不同的供应商可以在JCA框架内提供他们的工具。
JCA Resource Adapter Thread Pool (s).
JCA资源适配器线程池。
A working example will help explore some common JCA transaction issues.
实际的示例会有助于展示一些常见的JCA事务问题。
Two levels of programming interfaces are defined in the JCA specification.
JCA规范中定义了两种级别的编程接口。
The most prominent of these interfaces are JMS and JCA.
这些接口中最突出的是JMS和JCA。
Unfortunately, the JCA specification does not define the type of this property or what it means.
不幸的是，JCA规范没有定义这个属性的类型或者它的意义。
As its name suggests, this specification also provides an alternative to JCA work management.
顾名思义，这个规范还提供了JCA工作管理的一个替代。
Prior to JCA 1.5, the application server always acted as the transaction coordinator.
在JCA 1.5之前，应用服务器总是充当事务的协调者。
Second, if the data sources are legacy systems, you might have to use adapters or JCA.
第二种选择，如果数据源是遗留系统，可能就必须使用适配器或JCA。
For more information, refer to the JCA specification (see Resources).
要获取更多信息，请查阅jca规范(请参阅参考资料)。
应用推荐