Nor does the JCA specification explicitly support dynamic connection. JCA规范也没有明确支持动态连接。
Now JCA defines a standard architecture for connecting between applications and each type of EIS. 现在JCA定义了一个标准体系结构,用于在应用程序和每个类型的EIS之间进行连接。
We have said above that the J2EE standard defines ways to integrate non-J2EE applications by the use of APIs like JMS and JCA. 我们在上面已经说过,J2EE标准定义了一些通过使用象JMS和JCA这样的API集成非J2EE应用程序的方法。
The JCA specification defines a set of interfaces that allows development of pluggable application server components called resource adapters. JCA规范定义了一套接口,通过这些接口可以开发被称为资源适配器的可插入应用程序服务器组件。
JCA resource adapters support two-way communication between the J2EE components and EIS JCA资源适配器支持J2EE组件和EIS之间的双向通信
We can integrate J2EE and Web services technologies by defining specific protocol bindings for JMS and JCA in WSDL; this allows us to define back-end interfaces in a common, protocol-independent way. 我们可以通过用WSDL定义用于JMS和JCA的特定的协议绑定来集成J2EE和Web服务技术;这样我们就可以用一种通用的、独立于协议的方式来定义后端接口。
The WebSphere JCA adapter provides a mechanism to store and retrieve enterprise data in J2EE ™. WebSphereJCA适配器提供了一种在J2EE™中存储和检索企业数据的机制。
Second, if the data sources are legacy systems, you might have to use adapters or JCA. 第二种选择,如果数据源是遗留系统,可能就必须使用适配器或JCA。
We have not yet written JCA/ JCE-related classes. 我们还没有编写与JCA/JCE相关的类。
JCA allows you to integrate existing EIS while maintaining correct transactional semantics required for e-business. JCA允许在集成现有的EIS系统的同时,维持电子商务所需要的正确的事务性语义。
Conversation support is being positioned as a future J2EE extension for building conversational JCA adapters. 对话支持被定位成用于构建对话性JCA适配器的、未来的J2EE扩展。
To help manage this, the JCA transaction contract defines a set of architected interfaces through which the application server and the EIS coordinate the transaction. 为了有助于实现这一点,JCA事务合约定义了一套框架性接口,通过这套接口,应用程序服务器和EIS可以协调事务。
As mentioned above, a JCA Resource Adapter is used to link JMS resources and the SIB. 正如上面提到的,JCA资源适配器用于将JMS资源和SIB联系起来。
We will handle all the algorithm-and key-related issues in this method after writing the wrapper classes for JCA/ JCE. 在编写了用于JCA/JCE的封装器类之后,我们将在这个方法中处理所有与算法和密钥相关的问题。
It supports connectivity to EIS applications via IBM WebSphere Adapters based on JCA specifications. 它支持通过基于JCA规范的IBMWEBSphere适配器连接到EIS应用程序。
After these simple steps, we are all set to use JCA/ JCE in our XML Encryption application. 完成这些简单步骤之后,我们完全准备好开始在XML加密应用程序中使用JCA/JCE。
Such an Activation Specification is based on the Java Connector Architecture ( JCA) that provides a standardized way to communicate with enterprise information systems using Java. 此类激活规范基于JavaConnectorArchitecture(JCA),后者提供了使用Java与企业信息系统通信的标准化方法。
Using JCA and JCE in our implementation of XML Encryption 在我们的XML加密实现中使用JCA和JCE
The resource model differs from the standard JCA implementation by including OLAP-style interactions. 资源模型不同于标准的JCA实现,因为它包括了OLAP风格的交互。
The only requirement is that the Java environment acts as an JCA provider. 唯一的要求在于该Java环境充当JCA提供者。
In this article, I'll explain how the JCA transaction contract helps implement transactional behavior in e-business applications. 在本文中,我将解释JCA事务合约如何帮助电子商务应用程序实现事务性行为。
The import/ export files are based on the JMS binding, instead of the JCA adapter binding. 这些导入/导出文件基于JMS绑定,而不是JCA适配器绑定。
We've already mentioned JMS and JCA, which are the protocols that are probably the most relevant to enterprise application integration. 我们已经提到了JMS和JCA,它们可能是与企业应用程序集成联系最为紧密的协议。
The most prominent of these interfaces are JMS and JCA. 这些接口中最突出的是JMS和JCA。
JCA defines a series of Engine classes, where each Engine provides a cryptographic function. JCA定义了一系列引擎(Engine)类,其中每个引擎提供一种密码功能。
SCA defines several different types of bindings, including Web service, stateless session EJB, JMS, JCA, SCA default binding, and so on. SCA定义了多个不同的绑定类型,包括Web服务、无状态会话EJB、JMS、JCA、SCA缺省绑定等等。
JCA Resource Adapter Thread Pool ( s). JCA资源适配器线程池。
Subsequently, other specifications were published to extend the features provided by JCA. 随后又发布了其他一些规范,以扩展JCA提供的特性。
Technologies such as JCA and JMS still get used, but their APIs are not use directly by the component developer. 诸如JCA和JMS的技术依旧被使用,但是组件开发者不直接使用它们API。