Padawn, Per your suggestion I tried the get method with the exact same results:
Listing listing = (Listing)session.get(Listing.class, Long.parseLong(sListingId)); I also changed the dispatcher so that it uses the HibernateSessionManager to get the current session explicitly on each request, to no avail. I fell like something simple is evading me. My dispatcher fires before the page render dispatcher, does its thing, and then returns true (if handled) like any other one. Do I need to do any manual hibernate cleanup? I thought this was handled by a background event but I'm at a bit of a loss... thanks again for all the input snoopy dance made me laugh :-D Padawn wrote: > Since it's just my intuition speaking, I may be off-base, but...this sounds > like the beloved Hibernate Proxy and/or Cache issue, both of which > SnoopyDance all-over gray concurrency areas. Try substituting the query > code for a, literally, straight get(persistentClass, databaseId); call and > see if the issue is still there. > Bit of a performance it, but better to sweat that later. > -- http://thegodcode.net --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
