Ok, No problem, i have them now running both at the same time (with some slight modifications to ur classes, wrapped up in a separate module). Which is why i encountered this issue.
I guess i'm gonna make an extra Session interface which extends the hibernate session interface and then have the HibernateSessionObjectProvider returns this new Session interface. That way i can work with both. So if i then inject a (hibernate)session i'll get the default tapestry-hibernate one and if i inject the (multi)session one i also get a hibernate session but from a specific factory / entity. Antal -- View this message in context: http://tapestry.1045711.n5.nabble.com/Blog-Post-Tapestry-Magic-1-tp4307443p4390046.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
