just one side question: why are you getting stale objects..?
In my eye's this means that you don't use (or don't use right)
detachablemodels..
You shouldn't carry hibernate objects over requests..
I get StaleObjectStateException if my DB is hit from multiple threads
at once and in between the beginning of a transaction and the end of it,
the underlying state of one of my objects has become stale. I need to
then roll back the transaction and try again. This is a perfectly normal
situation as far as I know and there is no way around it (i.e. it isn't
a bug in my code that's causing it).
Gili
--
http://www.desktopbeautifier.com/
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
