The
ProxoolConnectionProvider has changed since Hibernate version 2.1.4 - mainly due
to issue HB-987.
The bigest impact of
those changes is it is now impossible to configure Proxool via properties
embedded in the hibernate.properties files. Too bad - it was a nice feature
(which is still supported by other connection providers).
Gavin says in its
bug description he couldn't configure Proxool properly this way. This is rather
strange because we are working this way since a long time and never had any
problem (could be he made use of features we never used). Anyway, a good idea
would have to first post a message on the proxool-dev
list...
As a proxool
developper I'd like to have this feature back in the ProxoolConnectionProvider
since it's removal will break many people's current
configuration.
==> Could someone
tell me if there are other reasons than those described in the bug description
(issues that will be fixed) that could prevent this 'embedded proxool config' to
be re-introduced in the standard Hibernate code base ?
<==
In the meantime,
does anyone else have comments/complains/wishes about Proxool when used with
Hibernate ?
Thanks,
-bertrand
PS: thank you such
much to all of you Hibernate developpers - it is an amazing tool
!
smime.p7s
Description: S/MIME cryptographic signature
