PaloT wrote: > > Hi, > I read our blog and I have questions (I ask here because nobody read > comments bellow blog): > > Do we somehow limit which type of event (Command/Message) can be fired > from service? > No limitation
PaloT wrote: > > Can we fire CommandEvent from service? > Yes PaloT wrote: > > Than after event reply aren't some events duplicated (one from replay > and one from service)? > I'm not sure that I understand the question. If you are using EventSourcing and the replay mechanism it is always the CommandEvents that are replayed and if they result in additional DomainEvents to be published they will be published again during replay. This can definitely be unwanted and must be handled by the application. Fowler describes this issue and talkes about gateways that must be aware of replay mode and avoid interaction with external parties. Currently we have not done anything about this. PaloT wrote: > > If we can't fire CommandEvent from service do we have some well know > patter which will bridge two services - for example service will fire > DomainEvent and some integration code will generate CommandEvent as > reaction to DomainEvent? > That is possible to do. We will write more examples in the blog. PaloT wrote: > > Don't we have to store some information about event like > module/application where it was created, ... for replay? > The EventSourcing mechanism operate on CommandEvents, which are persistent and stored with the ordinary persistence mechanism in Sculptor, i.e. in the same db as the business component where the specific CommandEvent is defined. PaloT wrote: > > > Regards > > Pavel > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > 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/BLOG%3A-EDA-sculptor-support-tp29208795s17564p29230038.html Sent from the Fornax-Platform mailing list archive at Nabble.com. ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Fornax-developer mailing list Fornax-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fornax-developer
