Perhaps I just don't understand the problem or I don't know enough about the session issues but for me it seems to work without any problems: I've just put the hivetranse jars in, defined service points for every DAO and the Session in hivemodule.xml and then I can CRUD my domain objects inside the DAOs with autowired session...
Andreas On 13. Apr 2006 - 20:37:52, Mark Reynolds wrote: | | Jean-Francois, | | I certainly did not mean to imply this is a bug or any deficiency of | hivetranse. I find hivetranse quite solid. :) | | I believe that it wasn't primarily designed for a Tapestry application | or tailored exclusively for Hiberate. So for me, it is a question of how | should it (or can it) be properly applied to a Tapestry application? | | I did try the approach you suggest, but it really is not very natural to | make it work with Tapestry's form/object updating and validation, unless | you create separate domain objects for the web layer and persistence | and copy from one to another, which I would like to avoid. At least that | was the best I could come up with... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
