There's nothing wrong imnsho with a Command manipulating the model on the ModelLocator directly. "Simplest thing that works" is never wrong, it's just a target for possible future refactoring.
Steven
|
From: cairngorm-devel@yahoogroups.com [mailto:cairngorm-devel@yahoogroups.com] On Behalf Of Evan Gifford
Sent: 12 October 2006 22:37
To: cairngorm-devel@yahoogroups.com
Subject: [cairngorm-devel] Best Practices - Ok to update VO on modelLocator directly from Command?
I’ve got a quick question,
Once a response is sent back from the BusinessDelegate to the Command, should the command “know” about the modelLocator .. and be allowed to access the ValueObject directly or should it always be done how it is done in the Cairngorm Store, and have the command call a public method located on the model which updates the Value Object?
Thanks guys.
-Evan
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.408 / Virus Database: 268.13.2/472 - Release Date: 10/11/2006
