Java201.com

• J2EE Connector Architecture 1.5 by Robert Eckstein   - [Clicks: 343]
  If you've ever tried to integrate legacy systems with a J2EE application server, you know that it can be quite a challenge. Managing connections, converting between different data types, and even sending messages between an application server and an Enterprise Information System (EIS) can leave an enterprise Java programmer with quite a headache. Thankfully, there's the J2EE Connector Architecture, now in version 1.5 in J2EE 1.4, which defines a standard architecture for connecting the J2EE platform to heterogeneous EISs.
  [Enterprise Java Technologies Tech Tips]
  http://java.sun.com/developer/EJTechTips/2004/tt1123.html#1 - Nov, 2004
• Creating Resource Adapters with J2EE Connector Architecture 1.5 by Alejandro E. Murillo, Binod P. G.   - [Clicks: 389]
  This article demonstrates some of the Connector Architecture features by showing you how to build an RA that provides synchronous and asynchronous access to email servers from client components of a J2EE 1.4 application server. The RA allows message-driven beans (MDBs) to receive email (javax.mail.Message) messages.
  http://developers.sun.com/prodtech/appserver/reference/techart/resource_adapters.html - Sep, 2004
• Using a JMS Provider with MDBs via the J2EE Connector Architecture by Debu Panda   - [Clicks: 142]
  Message-Driven Beans (MDBs) get a big boost in J2EE 1.4 via integration with the J2EE Connector Architecture (JCA), which opens up interesting possibilities to use messaging to and from legacy systems. Debu Panda shows how this can be accomplished.
  http://www.onjava.com/pub/a/onjava/2004/06/23/mdbjca.html - Jun, 2004
• J2EE Connector Architecture by Anthony Lai, Jyotsna Laxminarayanan, Lars Ewe   - [Clicks: 204]
  This article discusses some of the challenges of legacy system integration, then introduces the J2EE Connector Architecture (J2EE CA) and explains how it can significantly reduce the problems of integrating your legacy system. It also offers a comprehensive example of how to use the current version of J2EE CA, version 1.0, to access a common transaction-processing platform from a Java 2 Enterprise Edition (J2EE) platform application. This article concludes with an overview of the upcoming new release of J2EE CA, version 1.5, and explains some of the additional features and benefits introduced in this new version. This article assumes that you have a working knowledge of Java and J2EE.
  [Includes sample code]
  http://www.onjava.com/pub/a/onjava/2004/03/24/j2eeca.html - Mar, 2004
• What's New in the J2EE Connector Architecture 1.5 (Part 2) by Jennifer Rodoni Glore   - [Clicks: 135]
  This article is intended for EIS vendors, messaging providers, and developers who want to learn more about the Message Inflow and Transaction Inflow contracts that were introduced in the latest version of the Java 2, Enterprise Edition (J2EE) Connector Architecture (Connector 1.5). ... I'll focus solely on the two new contracts. Implementation details and specification requirements will be covered, and pseudo-code will be examined to see how an EIS vendor or messaging provider might implement the new contracts for a Connector 1.5-compatible resource adapter.
  http://java.sun.com/developer/technicalArticles/J2EE/connectorarch1_5/part2.html - Jan, 2004

[Top]