I just think that the visitor pattern is applied when you have
distinct classes that need to be traversed but you need to act
different depending on the type of the class, well, being visited.
The way you explained, seems that you only have Domain classes, and
domain class is unlikely to have these variations. So seems that you
only need to propagate a validation message, like:
object -> Validate
validate this:
validate my members
validate my collections
This is not something I'd use visitors for.
Anyway, I probably didn't understand it well and I'm just rambling
about an hypothetical design.
On 6/16/06, Craig Neuwirt <[EMAIL PROTECTED]> wrote:
> My goal is to perform validation as simple as possible given validation
> specific to a model as well as cross-domain validation.
--
Cheers,
hammett
http://hammett.castleproject.org/
_______________________________________________
CastleProject-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/castleproject-users
