We have been thinking back and forth regarding CommandEvent and DomainEvent, but finally seattled for separating them in the DSL, because they have very different purpose. CommandEvent only comes in to play when going down the path of CQRS and EventSourcing.
Take a look at the shipping sample, it covers everything. SVN: http://fornax.svn.sourceforge.net/svnroot/fornax/trunk/cartridges/sculptor/mongodb-sample/sculptor-shipping/ /Patrik PaloT wrote: > > Some questions: > - Do we need both "DomainEvent" and also "CommandEvent" in model? Only > difference is that one is persistent and second not? > - Do you plan to persistent automatically CommandEvents as framework > feature? > - Can you explain "publish" and "subscribe" semantic in more details - > what is generated > > Sorry to annoy you now with this questions. I'm sure you will write > some doc but I want play with it, it looks interesting. > > Thanks > > Pavel > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > Fornax-developer mailing list > Fornax-developer@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/fornax-developer > > -- View this message in context: http://old.nabble.com/CSC-520-tp28990047s17564p28993174.html Sent from the Fornax-Platform mailing list archive at Nabble.com. ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Fornax-developer mailing list Fornax-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fornax-developer
