> I would recommend
>
> Domain Driven Design - Evans
> Applying Domain Driven Design and Patterns - Nilsson
>
> In particular take a look at the specification and notification patterns.
I'd like to add the IoC pattern to look at. It's easy to create
pluggable validation using IoC which means that you can write the validation
in separated classes and still have flexible validation in your business
objects, without coupling between business object class and validator class.
FB
>
> Cheers,
>
> Greg
>
> On 2/12/07, Paul Cowan <[EMAIL PROTECTED]> wrote:
> > Hi,
> > Not sure if everyone has forgiven me for my last rant which was pretty
wrong
> :-) but I am looking for some advice to what I guess is a pretty common
> problem.We are developing an application that will have a lot of business
> rules that will change quite
> a lot during development. We have a domain model with aggregation used
quite
> a lot. Now the most advanced I have ever got with this in the past is to
have
> my POCO implement an IValidate interface and have the rules hard-coded into
a
> validate method.
> As I am sure you will agree this is a very inflexible approach.
> >
> > Does anyone know a better way of approaching this time honoured problem?
> > Cheers
> > Paul
> > ===================================
> > This list is hosted by DevelopMentor(r) http://www.develop.com
> >
> > View archives and manage your subscription(s) at
http://discuss.develop.com
> >
>
>
> --
> Studying for the Turing test
>
> ===================================
> This list is hosted by DevelopMentorR http://www.develop.com
>
> View archives and manage your subscription(s) at http://discuss.develop.com
===================================
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
