Thanks for the reply Taha! It is indeed very useful. I still find it hard to believe that you can't load/rebuild the entire different hibernate session with Tapestry. No matter the time it takes. As I said, I only need those databases to work one at the time.
Somehow I imagined it like this: - create different hibernate configuration for each database - create a session helper to execute something like this sessionFactory = new Configuration().configure().buildSessionFactory(); - load the session object back to tapestry But, can it be done? -- View this message in context: http://tapestry.1045711.n5.nabble.com/Again-with-the-tapestry-hibernate-and-switching-the-database-tp5716477p5716495.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
