I'm not sure what you mean by having ColdSpring "write the service layer for you", since usually you already have service layer objects and AOP just wraps them to add some extra functionality (is this what you mean?). However, you can just write an AOP advice that applies transaction handling to any method you want (Barney has already done this and his advice is up for download at his site). You're right though, nested transactions didn't make it into CF8 (which sucks since I saw it demoed during the beta tour).
On Nov 6, 2007 4:41 AM, Tom Chiverton <[EMAIL PROTECTED]> wrote: > > On Friday 26 Oct 2007, [EMAIL PROTECTED] wrote: > > +1 for Service layer as the place to manage transactions that span > multiple > > domain objects, or multiple kinds of domain objects. > > What if you are using (ColdSpring) AOP to write the service layer for you > ? > Then you're stuck with putting the transaction in each Manager's method, > and > wrapping calls to all the other Managers that make up that method too. > Which seems like massive overkill, and certainly not elegant, and I'm not > sure > CF8 finial supports nested transactions... > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
