> > It also creates a new transaction for every data operation which does not > > allow for making multiple operations atomic. > > Not true. Our base dao has methods for batching saves, updates and the > like that use the currently running transaction, with 1 single method > call you can then commit this transaction whenever you want. >
So you have transaction related methods on your DAO? If so the user is responsible for defining the transaction boundary's. I would prefer this to be automatically handled by the container OR by some wicket specific handler. Separation of concerns and all that... ------------------------------------------------------- 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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
