I know the multiple database question has been beat to death on the forums here but I do have an idea / question. We have a use-case on our Spring (1.1.5) + Hibernate (2.1.8) where we need to store the same information into multiple databases. Basically the domain mappings would be the same just the database they pointed to would need to change.

What would be the danger, if any, of getting a Session from a SessionFactory and using something like Session.reconnect to "switch out" the connection at runtime? That way we can get a default connection from the SessionFactory and use AOP as needed to switch out the connection.

Thanks,
C

why not just use user provided connections ?
sf.openSession(yourConnection)

AOP is not something one should apply anywhere just because you can ,)

-max

Here, here! I couldn't agree more. :)

I guess my answer to your question would be because we would have to 'manually' manage the Session in our DAOs. Since we've bit off on Spring's abstraction of the Hibernate API that would be a re-write of most, if not all, of our DAOs. I'm not aware of any way to tell Spring's HibernateDAOSupport or HibernateTemplate to use the SessionFactory.openSession(Connection) call. But, I'll be extremely happy if I'm wrong and someone can point me in the right direction. :)

Since all that really changes is the database target where the information gets stored it just seems easier (it may not be in reality) to work a way to use multiple data sources/connections to those databases.