Grouper Developers Forum

[Chris Hyzer <>]

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 
> [mailto:]
> 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.