On Fri, Apr 24, 2009 at 1:28 PM, Igor Vaynberg <[email protected]> wrote: > lies! all lies! > > it makes perfect sense to put transactional boundaries on the ui > events. user "clicking a button" is an action that the user perceives > as being a unit of work which is where the transaction boundary should > be. > > it is also not uncommon to put transaction boundaries on the request - > which is also a ui artifact. > > dont get me wrong, you should still have transactional boundaries on > the domain object, but you should have a higher one on a > button.onsubmit() so that it combines whatever transactions the domain > calls will start into a single one.
We'll just have to agree to disagree here. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
