Installing JNDI File System Service Provider
This section describes how to download and install File System Service Provider for JNDI.
Derby JDBC DataSource class can be used directly to create a connection as shown in the previous tutorial.
But that's not the suggested way of getting a connection.
JDBC document suggests you to create DataSource object
and make it available through a directory service via JNDI.
The application program can retrieve it whenever needed.
In order to try this method, I have to download and install the
JNDI File System Service Provider package from Sun (now Oracle) as described below:
- Go to DOWNLOAD JNDI SOFTWARE Website
- Click the Download link next to "Download JNDI 1.2.1 & More".
- Click the radio button: "Accept License Agreement".
- Click the link: "File System Service Provider, 1.2 Beta 3", create a directory \local\fscontext, and save the downloaded file as:
- Unzip \local\fscontext\fscontext-1_2-beta3.zip. You are done with the installation.
Open \local\fscontext\doc\providers\jndi-fs.html to read the documentation. The first paragraph gives you a good summary:
JNDI offers a universal naming API and a standardized way to store objects in a namespace. The file system service provider supports these features for a local or networked file system. Its purpose is two-fold:
- Allow clients to traverse the file system namespace using JNDI's context interface.
- Allow clients to store Java objects in the file system.
These two separate functions are actually handled by two different providers (i.e., classes).
The first class handles accessing the file system and can be used independently of the second.
The second class handles storage of Java objects and is used in conjunction with the first
(i.e., it is a subclass of the first).
Table of Contents
About This Book
JDBC (Java Database Connectivity) Introduction
JDK (Java SE) Installation
Installing and Running Java DB - Derby
Derby (Java DB) JDBC Driver
►Derby (Java DB) JDBC DataSource Objects
Derby - Connection with DataSource Objects
Derby - Using ClientDataSource Directly
►Installing JNDI File System Service Provider
Derby - Storing ClientDataSource Objects on File System
Derby - Looking Up ClientDataSource Objects on File System
What Happens If Client JDBC DataSource JAR Is Missing?
Java DB (Derby) - DML Statements
Java DB (Derby) - ResultSet Objects of Queries
Java DB (Derby) - PreparedStatement
MySQL Installation on Windows
MySQL JDBC Driver (MySQL Connector/J)
MySQL - PreparedStatement
MySQL - Reference Implementation of JdbcRowSet
MySQL - JBDC CallableStatement
MySQL CLOB (Character Large Object) - TEXT
MySQL BLOB (Binary Large Object) - BLOB
Oracle Express Edition Installation on Windows
Oracle JDBC Drivers
Oracle - Reference Implementation of JdbcRowSet
Oracle - PreparedStatement
Oracle - JBDC CallableStatement
Oracle CLOB (Character Large Object) - TEXT
Oracle BLOB (Binary Large Object) - BLOB
Microsoft SQL Server Express Edition
Microsoft JDBC Driver for SQL Server
Microsoft JDBC Driver - Query Statements and Result Sets
Microsoft JDBC Driver - DatabaseMetaData Object
Microsoft JDBC Driver - DDL Statements
Microsoft JDBC Driver - DML Statements
SQL Server - PreparedStatement
SQL Server CLOB (Character Large Object) - TEXT
SQL Server BLOB (Binary Large Object) - BLOB
JDBC-ODBC Bridge Driver - sun.jdbc.odbc.JdbcOdbcDriver
JDBC-ODBC Bridge Driver - Flat Text Files
JDBC-ODBC Bridge Driver - MS Access
JDBC-ODBC Bridge Driver - MS SQL Server
Summary of JDBC Drivers and Database Servers
Using Connection Pool with JDBC
Full Version in PDF/EPUB