Before I get into the meat of using ColdSpring to save even more time (by writing the Service layer for you, believe it or not), I wanted to take time out to give you some 'take home' reading and also address some terminology issues.
Firstly, here's the reading list :-)
http://www-128.ibm.com/developerworks/java/library/j-aopwork15/ (for Java's Spring, but makes some good general points while doing so)
http://cdscott.blogspot.com/2005/09/introduction-to-coldspring-aop.html
http://cdscott.blogspot.com/2005/10/coldspring-aop-tutorial-part-one.html
http://cdscott.blogspot.com/2005/11/coldspring-aop-tutorial-part-two.html
http://cdscott.blogspot.com/2006/02/introducing-auto-magic-remoting-with.html
http://cdscott.blogspot.com/2006/07/pointcuts-even-more-fun-with-regex.html
As you can see from the dates, this is 'well baked' technology that's been around a while in ColdSpring, and it really does seem to take the pain out of the Service tier. But I'm getting ahead of myself.
Before going onwards, I wanted to point out that when I say that 'Managers' are exposed by, and have external interactions mediated by, 'Services', you may find the wider community uses 'Manager' and 'Service' to mean the same type of thing, as well as 'Business Object' or 'Domain Object' to mean 'transfer' or 'value' object. Services' are just proxies or remote facades (or RemoteFactoryBeans, if you've done your reading :-) ) in that context.
I choose the names because 'Managers' manage things, as opposed to the 'Services' that serve them up.
I'll stick to my definitions for now, so as to keep this series consistent, but in future I'll try to use one of the alternatives.