http://blog.phatboyg.com/2009/01/16/state-machine-for-managing-sagas/ Software Architecture, .NET, SOA Wed, 05 May 2010 03:41:41 +0000 hourly 1 http://wordpress.org/?v=3.2.1 http://blog.phatboyg.com/2009/01/16/state-machine-for-managing-sagas/comment-page-1/#comment-18637 MassTransit 0.6 Release Candidate - PhatBoyG (Chris Patterson) - Tue, 31 Mar 2009 02:18:09 +0000 http://blog.phatboyg.com/?p=739#comment-18637 [...] Saga State Machine With the all new method of defining sagas using a state/event fluent interface, it is now even easier to describe the business logic of a process and the events from which it is built. With the new state machine, it is not necessary to have message consumers and interfaces on your saga, you can just define the events in the class and they are wired automatically by the subscription framework. The early version of the syntax was discussed in this post. [...] [...] Saga State Machine With the all new method of defining sagas using a state/event fluent interface, it is now even easier to describe the business logic of a process and the events from which it is built. With the new state machine, it is not necessary to have message consumers and interfaces on your saga, you can just define the events in the class and they are wired automatically by the subscription framework. The early version of the syntax was discussed in this post. [...]

]]> http://blog.phatboyg.com/2009/01/16/state-machine-for-managing-sagas/comment-page-1/#comment-18636 MassTransit 0.6 Release Candidate Tue, 31 Mar 2009 02:16:59 +0000 http://blog.phatboyg.com/?p=739#comment-18636 [...] Saga State Machine With the all new method of defining sagas using a state/event fluent interface, it is now even easier to describe the business logic of a process and the events from which it is built. With the new state machine, it is not necessary to have message consumers and interfaces on your saga, you can just define the events in the class and they are wired automatically by the subscription framework. The early version of the syntax was discussed in this post. [...] [...] Saga State Machine With the all new method of defining sagas using a state/event fluent interface, it is now even easier to describe the business logic of a process and the events from which it is built. With the new state machine, it is not necessary to have message consumers and interfaces on your saga, you can just define the events in the class and they are wired automatically by the subscription framework. The early version of the syntax was discussed in this post. [...]

]]>