We already tried this approach, but we were having problems with queries. We're using a never-flush policy, but it seems that queries require you to flush your session to avoid returning stale data. I need to post-process query results to take account of changes to session objects. This doesn´t seem trivial, though. I don´t want to reinvent the wheel, but I'm looking for a general enough approach to reuse it in several projects.On 10 Nov (19:13), Martin Paoletta wrote:I understand why this is happening, What I've been missing is something like a business transaction that can span several r-r cycles, with an identity map (which should solve the problem of repeated objects) andRe-use the same Session in each R-R cycle, but don't forget to disconnect() and reconnect() it. Use a Servlet Filter, this works great with the Open Session View pattern.Be careful though, your scope changes with that technique and you may have "half"-stale data for a long time.
Bye,
Martin Paoletta
------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
