commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From di...@apache.org
Subject cvs commit: jakarta-commons/dbcp release_notes.txt
Date Sun, 26 Oct 2003 15:39:18 GMT
dirkv       2003/10/26 07:39:18

  Modified:    dbcp     release_notes.txt
  Log:
  fix some typos
  
  Revision  Changes    Path
  1.5       +4 -4      jakarta-commons/dbcp/release_notes.txt
  
  Index: release_notes.txt
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/dbcp/release_notes.txt,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- release_notes.txt	20 Oct 2003 18:25:15 -0000	1.4
  +++ release_notes.txt	26 Oct 2003 15:39:18 -0000	1.5
  @@ -1,7 +1,7 @@
   Release notes for Commons-DBCP 1.1
   ===================================
   There were a lot changes since the 1.0 release on 12 Aug 2002.
  -* All existing featueres can now be configured by JNDI Context providers (Tomcat)
  +* All existing features can now be configured by JNDI Context providers (Tomcat)
   
   * The double close() of a pooled connection is more effectively blocked
     (you may experience more "Already closed" SQLExceptions)
  @@ -9,7 +9,7 @@
   * Prepared statement pooling is now implemented in BasicDataSource
     (set poolPreparedStatements=true, maxOpenPreparedStatements=xxx)
   
  -* Access to the undelying connection is blocked by default
  +* Access to the underlying connection is blocked by default
     You can access the underlying connection by setting
     accessToUnderlyingConnectionAllowed=true and by using the following construct:
     Connection dconn = ((DelegatingConnection) conn).getInnermostDelegate();
  @@ -18,9 +18,9 @@
   
   * New connection default properties: defaultCatalog & defaultTransactionIsolation
   
  -* Missing driverClassName will now give the folowing error "No suitable driver"
  +* Missing driverClassName will now give the following error "No suitable driver"
   
  -* Bad validationQuery will produce a meaningfull SQLException
  +* Bad validationQuery will produce a meaningful SQLException
   
   * UML Class & sequence diagrams, configuration documentation
   
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message