Thanks for all your hard work Dirk to resolve reported bugs and get
this release out.

Regards,

GLenn

-------- Original Message --------
Subject: [ANNOUNCEMENT] Commons DBCP 1.1 released
Date: Wed, 22 Oct 2003 15:29:59 -0700 (PDT)
From: Dirk Verbeeck <[EMAIL PROTECTED]>
Reply-To: Jakarta Commons Developers List <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED],       [EMAIL PROTECTED]

The Jakarta Commons team is pleased to announce the release of version 1.1
of the Jakarta Commons DBCP component.

Commons-DBCP provides database connection pooling services. Together with
Commons-Pool it is the default JNDI datasource provider for Tomcat.
More info: http://jakarta.apache.org/commons/dbcp/

There were a lot changes since the 1.0 release on 12 Aug 2002.
    * All existing features can now be configured by JNDI Context
      providers (Tomcat).
    * The double close() of a pooled connection is more effectively
      blocked.
    * Prepared statement pooling is now implemented in BasicDataSource.
    * Access to the underlying connection is blocked by default.
    * New minIdle parameter for a minimum number of idle connections ready
      for use.
    * New connection default properties:
      defaultCatalog & defaultTransactionIsolation.
    * Missing driverClassName will now give the following error
      "No suitable driver".
    * Bad validationQuery will produce a meaningful SQLException.
    * UML Class & sequence diagrams, configuration documentation.
    * This release contains bug fixes to all known issues.

The latest binary release is always available on the Jakarta Binary
Downloads page, its source is available from Jakarta Source Downloads
page.

-- Dirk Verbeeck

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to