JBoss Seam uses 2 transactions for every request. 1 for the data processing and 1 for the rendering. I think this is a good strategy to reduce the amount of time locks are held for. is there a way to do something like this transparently in wicket? Currently I lazily open a session, begin a transaction and I commit/close by overriding the onEndRequest.
Thanks ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
