On Feb 8, 2007, at 9:14 PM, Eric Newcomer wrote: > Yes, an object has a function. But the business more naturally > thinks about "getting customer data" than about "the customer is an > object on which you perform a get function."
Hi Eric, I remember we had this discussion before - no OO designer is likely to model things this way. It's perfectly fine and custom practice to have classes with different roles, some of them more similar to "controllers", others more similar to "entities". Having a "CustomerManager" with a "get" operation that returns a "Customer" value object is absolutely object-oriented and not at all different from a typical SOA approach. A difference in a typical SOA approach is that the "customer value object" would likely be an XML document, but that's a completely different aspect than the one you point out. Stefan -- Stefan Tilkov, http://www.innoq.com/blog/st/
