Grouper Developers Forum

[Dave Donnelly <>]

Chris, and others interested in Hibernate3,

If you are relying on the DBCP connection pool lib that came
with Hibernate2, be aware that their DBCPConnectionProvider
class is no longer available in Hibernate3. Their documentation
states that a connection provider is specified in the hibernate
config file, and through a heuristic search, determines which
connection provider to use. If for any reason it fails to
find one (and if you're using 'hibernate.dbcp.*' it will fail)
then Hibernate3 silently uses its own internal, less-than-production-
quality connection pool. I found this out when the DBA at Stanford
asked me why Signet's DB had 40 open connections all the time.

One of the Hibernate developers assured some mail list that use
of DBCP is possible. He stated that none of Hibernate dev team
uses DBCP (so neither should you ;-), and removed it from Hibr3.
To use it you will need to write your own implementation of
org.hibernate.connection.ConnectionProvider. I found a few partial
implementations on the web but wimped-out and simply used the C3P0
connection pool that came with Hibernate3. Seems to work fine so far.
Note that there are 6 C3P0 configuration settings that _must_ be in
the Hibernate3 config file
(@see http://www.mchange.com/projects/c3p0/index.html#hibernate-specific)

--Dave Donnelly
Signet Project




Chris Hyzer wrote:

They should probably remove their own hib3 jars and do any upgrade steps hibernate recommends to get on the same (latest and greatest) version that comes with grouper if they aren't already on it.  Typically this is not a lot of work if any, but good to know about...  incidentally, maybe we shouldn't use any features in 3.2 that aren't in 3.1 or 3.0 (if possible) to make things a little more forgiving...

http://www.hibernate.org/250.html

Chris

  

-----Original Message-----
From: Kathryn Huxtable []
Sent: Wednesday, February 06, 2008 2:26 PM
To: Grouper Dev
Subject: [grouper-dev] Questions about interoperability of multiple
Hibernate3 databases

Given that the Grouper API is likely to be moving to Hibernate3, a
move I support, how will this interoperate should someone write a
program that uses both the Grouper API and another database or API
that also uses Hibernate3?

At KU, they have a web interface that stores rules for populating
groups from KU's IdMS database. KU uses Hibernate3 for the IdMS access
code, but the Grouper they're using still uses Hibernate2, so there's
no conflict at the moment.

Will this be a problem in the future?

-K, who talks to people at KU about once a month, just to keep in
touch.