We can then use connBean as we would any JDBC connection. Many tools can
create command beans automatically, which makes this command architecture
so attractive. A lot of these tools already use connection pooling.
It is critical, then, that:
Existing applications already use connection pooling.
Development wizards, classes, and templates can fully enable database
connection reuse through pooling.
Using the J2EE connector architecture
A database is but one form of an enterprise information system ( EIS ). Like-
wise, connection pooling through data sources is only one part of the total
package. J2EE defines a transparent architecture for connecting to a generic
EIS . This framework allows a vendor to achieve robust connection support,
with connection pooling, security, and other complex considerations, through
the support of a single specification. Web application server vendors can sup-
port a single interface and gain access to an increasing number of systems.
Figure 7.4 shows how the connection architecture works. EIS s access web
application functions through special adapters, provided by the individual EIS
vendor. This adapter collaborates with the web application server to provide
Figure 7.4 The J2EE common connector architecture uses vendor-provided adapters, operating
through a common interface, to collaborate with the web application servers to provide
transaction integrity, security, and efficient connection management. Connection pooling is
included in the specification.