Which part sounds awkard? Having domain object specify specific validators and combine that with a contextual validation? or something else
My goal is to perform validation as simple as possible given validation specific to a model as well as cross-domain validation.
How have you handled that in the past? Did you just create a Validation service that accepts domain objects?
As always, I welcome your criticism :-)
On 6/16/06, hammett <[EMAIL PROTECTED]> wrote:
This sounds awkward.
On 6/16/06, Craig Neuwirt <[EMAIL PROTECTED] > wrote:
> It would be the normal approach. Each DomainObject would accept an
> IDomainVisitor and call back on it. The visitor would collect useful info
> such that after calling the DomainObjects IsValid method, it could then
> check cross-dependency validation.
--
Cheers,
hammett
http://hammett.castleproject.org/
_______________________________________________
CastleProject-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/castleproject-users
_______________________________________________ CastleProject-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/castleproject-users
