private support for your internal/customer projects ... custom extensions and distributions ... versioned snapshots for indefinite support ... scalability guidance for your apps and Ajax/Comet projects ... development services from 1 day to full product delivery
Here are examples of configuring a JNDI datasource for various databases.
All of these examples correspond to a
These examples assume that all of the datasources are declared at the
JVM scope, but you can use other scopes if desired. You can configure all
JNDI resources in a
jetty.xml file or in a
WEB-INF/jetty-env.xml file, or a context XML file. See the
section Deciding Where to Declare Resources for more information.
You must provide Jetty with the libraries necessary to instantiate
the datasource you have configured by putting the corresponding Jar in
Pooling datasources enables connection pooling, which lets you reuse an existing connection instead of creating a new connection to the database. This is highly efficient in terms of memory allocation and speed of the request to the database. We highly recommend this option for production environments.
The following is a list of the pooled datasource examples we have worked with in the past:
Connection pooling, available at c3p0 Jar.
Connection pooling, available at dbcp Jar.
If you are deploying in a production environment, we highly recommend using a Pooling DataSource. Since that is not always an option we have a handful of examples for non-pooling datasources listed here as well.
The following is a list of the non-pooled datasource examples:
For more information, refer to: Oracle Database JDBC documentation.