On Tue, Jul 28, 2009 at 12:25, Rickard Öberg<[email protected]> wrote: > /* This is an event method. It is an "after the fact" method, and the tense > used in the name follows this. It takes only one argument, which is an event > object that is a subtype of DomainEvent which is a subtype of ValueComposite > and Identity, signifying that it is immutable and identifiable. DomainEvent > ALWAYS contains properties for date of firing and the user who fired it. > Custom mandatory data can be added in subclasses. Event methods may NOT > throw exceptions, and may NOT perform input data checking, since they are > not allowed to say no. It *does* return the created OU, but this is for > convenience of the calling command method only. @Event methods will have a > SideEffect that creates a persistent event to be put on disk and distributed > to whoever is interested in what is happening in the domain. */ > �...@event > OrganizationalUnit organizationalUnitCreated(CreatedEvent event);
Can this is defined in private mixin? and, how do u order the event handler execution? > Thoughts and comments on this? Same thought as Niclas. Regards, Edward Yakop _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
