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. -- View this message in context: http://www.nabble.com/T5.0.14-SNAPSHOT%3A-strange-behavior-Dispatcher-when-using-a-Session-tp18624780p18639009.html Sent from the Tapestry - User mailing list archive at Nabble.com.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
