Grouper Developers Forum

[Kathryn Huxtable <>]

What about configuration files? Do they conflict? I think it ought to  
be possible to set up completely separate IOC-style setups for  
different Hibernate3 databases.

(I don't think upgrading the Hibernate libs will be a problem for them  
when it comes to that. I'm guessing they're still running on Grouper  
1.1. They've got an awful lot of projects and not a lot of staff.)

-K

On Feb 6, 2008, at 1:48 PM, 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 
> > [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.