One more comment: I think there is small issue with the multi database support. It looks like the 'per thread' instance of HibernateSessionManager isn't per thread at all.
The Inject annotation used to create the session uses the masterobjectprovider to build the session, but this gets only be done once (!) the hibernatesessionmanagerimpl injected to HibernateSessionObjectProvider is NOT build again on the next thread. So basically the per thread definition is useless as you are working with a application wide session object iso per thread (request) I could be wrong but this is what i saw after some debugging... Antal -- View this message in context: http://tapestry.1045711.n5.nabble.com/Blog-Post-Tapestry-Magic-1-tp4307443p4403229.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
