Refer to the URL
for a good tutorial about the RequestDispatcher class. Refer to the URL
for official specifications and documentation for the
various Java API specifications.
5.2.2 JDBC connections for Domino
JDBC(TM) is an object interface that allows Java applications, applets, and
agents to retrieve and manipulate data in database management systems
using SQL. The interface allows a single application to connect to many
different types of databases through a standard protocol.
The Lotus Domino Driver for JDBC implements the JDBC 1.0 specification. It
can be for the Windows 95, Windows 98, and Windows NT 4.0 operating
systems. This is a Type 2 driver, which means that it is comprised of a
combination of Java classes and non Java compiled code. It is currently not
available for any other platform (including Linux).
The Lotus Domino Driver for JDBC allows Java programmers to access
Domino/Notes databases using JDBC. Users can work with any JDBC
enabled reporting tool to access Lotus Domino databases. Java programmers
can use any Java Database Connectivity (JDBC) standard enabled
application tool to access Lotus Domino databases as easily as any relational
database. When running this JDBC driver with Domino R5, Java
programmers can write Servlets that access Domino data. The Lotus Domino
Driver for JDBC makes Domino databases look like another relational
back end source to the SQL tool or application interface by producing result
sets that mirror the relational model. An application can also perform a SQL
Join of data from Domino with data from a relational database, such as
Oracle, Sybase, or DB/2.
Product features include:
Java standard access to Domino 4.5x, 4.6x, and R5x databases.
Compatible with Netscape Communicator 4.05 and higher.
Compatible with Microsoft Internet Explorer 4.01 with service pack 1 and
Includes signed and unsigned version for maximum flexibility when
creating Java applets that use JDBC
Year 2000 ready; so, it correctly reads and interprets dates in two digit
year (mm/dd/yy) and four digit year (mm/dd/yyyy) format.
Tested with IBM s Visual Age for Java Version 2.0, IBM s WebSphere
Application Server 2.0, Lotus eSuite DevPack 1.5, Borland s JBuilder 3
Chapter 5. Extending the case study