You may want to consider creating a factory class for database
connections. I'd suggest a singleton that initializes a data source or
connection pool on initialization and then provides a facade to it (i.e.
it implements methods with the same or similar names to the methods in the
datasource that simply call the corresponding methods from the datasource).

The compiled class goes into WEB-INF/classes (in the directory of its
package), and can be used from JSP's.

For example:
- The class is nl.opk.test.DataSourceFacade and contains at least the
 public static method getInstance().
- Then the JSP can then use it thus:
    <%@ page language="java" %>
    <%@ page import="nl.opk.test.DataSourceFacade" %>

    <%
        DataSourceFacade dsf = DataSourceFacade.getInstance();
    %>

Notes:
- Use a singleton to ensure the different JSP's use the same datasource /
 connection pool.
- You probably want the method getInstance to read a properties file that
 defines the connection to the database. I'd suggest a ResourceBundle
 that reads the resources from "nl.opk.test.Database", so you can place a
 file "Database.properties" in the same directory as the class. The
 .properties file contains comments (empty lines and lines beginning with
 a hash (#)), and <name>=<value> pairs.

Oscar