My first design was like this (since Office is the Aggregate Root)...
but it's the aggregate root of a certain Employee entity as well and I
tought it could become cluttered... then i switched to having the
Create task in the Project Tasks but didn't made much sense because in
plain english it should be an Office Task to create the Project.
Thanks for the reply.
On Sep 2, 4:35 am, Ryan Barrett <
r...@seldonplan.com> wrote:
> If Office is your aggregate, then you can (and IMHO should) put a factory
> method on it for creation of Projects. However in my experience the word
> Project has a tendancy to denote something pretty important for your domain,
> which can exist outside of the bounds of one aggregate.
>
> --
> Ryan
>
> On 2 September 2010 01:40, Felipe Amorim <
felipe.leu...@gmail.com> wrote:
>
> > First off,
> > I'm doing some testing with WCHM.
>
> > In this application I got an Office that has Projects associated, in a
> > manner that a Project entity can only exist inside an Office one.
>
> > My question is, should i leave the responsability of creating a
> > project (to the ProjectTask or to the Office task). There are some
> > business rules to be enforced.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "S#arp Architecture" group.
> > To post to this group, send email to
sharp-arc...@googlegroups.com.
> > To unsubscribe from this group, send email to
> >
sharp-architect...@googlegroups.com<
sharp-architecture%2Bunsu...@googlegroups.com>
> > .