[Proxool-cvs] proxool CHANGES.txt,1.25,1.26

[<bil...@us...>]

Update of /cvsroot/proxool/proxool
In directory sc8-pr-cvs1:/tmp/cvs-serv24675

Modified Files:
	CHANGES.txt 
Log Message:
0.8.0RC2

Index: CHANGES.txt
===================================================================
RCS file: /cvsroot/proxool/proxool/CHANGES.txt,v
retrieving revision 1.25
retrieving revision 1.26
diff -C2 -d -r1.25 -r1.26
*** CHANGES.txt	30 Aug 2003 11:44:54 -0000	1.25
--- CHANGES.txt	1 Oct 2003 19:31:54 -0000	1.26
***************
*** 6,13 ****
  $Author$
  
! 0.7.3 - (30 August, 2003)
  
! - Fix to documentation. Defining more than one type of fatal SQL exception
!   is done with a comma delimited list.
  
  - New getDelegateConnection() method on ProxoolFacade gives you access
--- 6,17 ----
  $Author$
  
! 0.8.0 - (October, 2003)
  
! - We now use Cglib's proxy library. Together with dropping the use of Timer
!   and only referencing ShutdownHooks at runtime we are now able to support
!   JDKs 1.2, 1.3 and 1.4 out of the box (Without Ant applied patches, which
!   were horrible).
! 
! - Proxool is now available as a JMX component.
  
  - New getDelegateConnection() method on ProxoolFacade gives you access
***************
*** 24,28 ****
    regardless of your timezone. This was a display bug only and didn't
    effect the behaviour of the pool itself.
!    
  - Connections that are about to be expired no longer bother to reset
    themselves (because they'll never be used again anyway). This was
--- 28,32 ----
    regardless of your timezone. This was a display bug only and didn't
    effect the behaviour of the pool itself.
! 
  - Connections that are about to be expired no longer bother to reset
    themselves (because they'll never be used again anyway). This was
***************
*** 30,36 ****
    database which then caused problems during the reset.
  
  - Fixed ConcurrentModificationException that happened in some
    environments during automatic statement closure.
!    
  0.7.2 - April 28, 2003
  
--- 34,61 ----
    database which then caused problems during the reset.
  
+ - Added fatal-sql-exception-wrapper-class property. If a fatal exception is
+   detected then it is wrapped up inside the exception defined by this
+   property. This can make exception handling easier is frameworks like
+   Struts. Two wrappers are provided (FataSQLException and FatalRuntimeException)
+   but you can also define your own.
+ 
+ - Added test-before-use and test-after-use properties. They will trigger a test of
+   the connection (as defined by house-keeper-test-sql) just before a connection
+   is handed out and just after it is closed (put back in the pool) respectively.
+   These are both off by default.
+ 
  - Fixed ConcurrentModificationException that happened in some
    environments during automatic statement closure.
! 
! - Fixed bug where if there was an Error during prototyping (not an SQLException,
!   not a RuntimeException but something serious like NoClassDefFoundError) then
!   the prototyper would keep attempting to make connections as fast as it could
!   (and never succeed in making any). Much better for the prototyper to give
!   up in that situation and try again when it is next asked (which, by default,
!   would be 30 seconds later).
! 
! - Fix to documentation. Defining more than one type of fatal SQL exception
!   is done with a comma delimited list.
! 
  0.7.2 - April 28, 2003