Re: Domain Event Objects vs Standard Events

"Rikard Pavelic [email protected] [domaindrivendesign]" <[email protected]> Thu, 28 May 2015 01:02:10 +0200
Newsgroups gmane.comp.programming.domain-driven-design
Organization N.G.S.
Message-ID <[email protected]>
On Wed, 27 May 2015 18:35:54 -0400
"Marco Paul [email protected] [domaindrivendesign]"
<[email protected]> wrote:

> Rikard
> 
> How are u raising your domain events from within your aggregate?

Most of the events come from outside anyway.
Those which are raised during processing are raised using
repository/service which has a reference to the current transaction/unit
of work. So can't really say I'm a fan of raising events from within
the aggregate, mostly from within various services.

> "The issue with this code (except static Bus.Publish) is that event is
> > tied to the instance. Not sure when this would be useful."
> > 
> 
> Not sure what u meant by this as domain events are always associated
> with an instance of a domain concept

Just that I find it strange that different aggregate instances have
different event delegates. 
For example, if you create an instance of the
Consignee in another part of the code, it wont invoke your handler.

Regards,
Rikard

-- 
Rikard Pavelic
https://dsl-platform.com/
http://templater.info/


------------------------------------
Posted by: Rikard Pavelic <[email protected]>
------------------------------------


------------------------------------

Yahoo Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/domaindrivendesign/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/domaindrivendesign/join
    (Yahoo! ID required)

<*> To change settings via email:
    [email protected] 
    [email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo Groups is subject to:
    https://info.yahoo.com/legal/us/yahoo/utos/terms/