>This would require duplicating error and transaction handling in every method. True, but you can compensate by inheriting a lot of common methods from a general implementation. Besides our base dao we hardly ever have to deal with transactions in our dao's. > 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.
Maurice Marrink 2005/12/16, John Patterson <[EMAIL PROTECTED]>: > On Friday 16 Dec 2005 05:40, Maurice Marrink wrote: > > We use the dao pattern. any exceptions are handled by the different dao's. > > This would require duplicating error and transaction handling in every method. > It also creates a new transaction for every data operation which does not > allow for making multiple operations atomic. > > > ------------------------------------------------------- > 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 > Wicket-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wicket-user > ------------------------------------------------------- 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_idv37&alloc_id865&op=click _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
