[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4156?page=c...
]
Steve Cohen commented on HHH-4156:
----------------------------------
Not to beat a dead horse, but now that I understand the problem, I like the way this was
working before the bug fix. This business of Hibernate inferring that I want to use c3p0
by the presence of one or more c3p0 tuning parameters is kind of dodgy IMHO. I would
rather that the user was forced to declare this intention explicitly. However, I
understand that this broke too much of the installed base, including me, when I upgraded
to a less than most-recent version that worked this way.
Still this guessing that Hibernate does here strikes me as ugly, and I will from here on
specify by defining the "hibernate.connection.provider_class" property whether
it's required or not.
c3p0 is not used when only specific hibernate.c3p0.* properties
---------------------------------------------------------------
Key: HHH-4156
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4156
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.5.3
Reporter: Marcelo Romulo Fernandes
Assignee: Strong Liu
Priority: Minor
Fix For: 3.5.4, 3.6.0.Beta1
in hibernate document, it says:
{quote}
C3P0 is an open source JDBC connection pool distributed along with Hibernate in the lib
directory. Hibernate will use its org.hibernate.connection.C3P0ConnectionProvider for
connection pooling if you set hibernate.c3p0.* properties.
{quote}
but this is not working anymore, if you not explicitly add this property:
<property
name="hibernate.connection.provider_class">org.hibernate.connection.C3P0ConnectionProvider</property>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira