What I refer to as a business object in this article, you could also just call a model object. Because of the simplicity of the example it might look like a VO at the beginning, but read further articles in the series to get an idea where this potentially can go towards. It can be much more than just a VO, which responsiblity is to transfer data accros tiers. The Cairngormstore, the ShoppingCart would be another model object. You can easily unit test these objects and I encourage everyone to extract the right functionality from commands and views into objects such as this when your application demands a better separation of concerns. Best, Alex
Alex Uhlmann
Consultant (Rich Internet Applications)
Adobe Consulting
Westpoint, 4 Redheughs Rigg,
South Gyle, Edinburgh, EH12 9DQ, UK
p: +44 (0) 131 338 6969
m: +44 (0) 7917 428 951
[EMAIL PROTECTED]
http://weblogs.macromedia.com/auhlmann
________________________________
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of lostinrecursion
Sent: 09 December 2006 10:53
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Business Objects and Value Objects/Cairngorm.
Distinction?
Hi all,
I was reading a fantastic series by Alex Uhlmann on "How Business
Logic can Manage Your Views"
(
http://weblogs.macromedia.com/auhlmann/archives/2006/06/cairngorm_sampl.
cfm
<http://weblogs.macromedia.com/auhlmann/archives/2006/06/cairngorm_sampl
.cfm> )
I have one question for someone who may know. Could someone tell me
the difference between a Business Object (such as the one Alex uses to
encapsulate model properties) and a Value Object (which I am used to
constructing).
Is it fair to say a business object is just a "faux" collection of
various Value Object (and non VO) properties in one convenient location?
Likening it to the Cairngorm Store, would a ShoppingCart be a Business
Object (as it encapsulates properties and performs application logic)
while a ShoppingCartElement might be a Value Object?
Thanks.
adobe_logo.gif
Description: adobe_logo.gif
