The after effect is that the J2EE programmers have to use low-level APIs
to implement integration concerns.
Programmers create integration code having hard coded dependencies between
specific applications and data sources, which are neither efficient nor flexible. Hence,
a way to do integration in a loosely coupled manner and to port the integration
solution as a whole is missing. Components and services are only a part of the
integration solution. It also includes the strategy to integrate, the patterns adapted
to route and transform messages and similar artifacts. All these differ for different
vendor's products and JBI is trying to bring standardization across this space.
JBI and JCA??”Competing or Complementing
The J2EE Connector Architecture (JCA) defines standards for connecting the J2EE
platform to heterogeneous EIS systems. Examples of EIS systems include CICS, IMS,
TPF systems, ERP, database systems, and legacy applications not written in the Java
programming language. The JCA enables the integration of EISs with application
servers and enterprise applications by defining a developer-level API and a
vendor-level SPI.
Pages:
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79