Hi Leonid, we're aiming to start the RC phase for 2.4.x ASAP (2-3 weeks is the current goal); I don't think we'll have time enough in the team to spend on de-duplicating code between those FSMs, we'd definitely be very thankful for external contributions attacking this problem!
Also, this doesn't most likely won't be API changing, so it could still get in during the RC phase. -- Konrad On 9 August 2015 at 22:40:33, Leonid Bakaleynik ([email protected]) wrote: What about removing duplication between the original FSM and the akka.persistence.fsm.FSM? Is there a time for this in 2.4? Thanks, Leonid On Saturday, August 8, 2015 at 11:51:01 PM UTC+3, Konrad Malawski wrote: That's because *Persistent*FSMActor lives in akka-*persistence* :-) See here: http://doc.akka.io/docs/akka/current/scala/persistence.html#Dependencies Notice that it's graduating from experimental mode in a few weeks (into Akka 2.4). -- Cheers, Konrad 'ktoso’ Malawski Akka @ Typesafe On 27 July 2015 at 16:53:37, Nader Aeinehchi ([email protected]) wrote: Hello everyone I find PersistentFSMActor to be a very interesting concept. I intend to use PersistentFSMActor as part of an automatic issue management. I wonder if there is an example of its usage? My hypothesis: 1. Each issue is represented as an PersistentFSMActor. 2. Each issue is "born" without data and can be started in some initial state. 3. Each state and its data are persisted and make the entire issue's history 4. If the issue is completed, it is persisted and terminated. 5. If an issue cannot be completed, it goes to some state (e.g. Waiting) and sleeps (persists). Then it is removed from the memory. 6. Upon new events, some IssueCoordinator actor wakes up the PersistentFSMActor(issue) and sends the issue an event. The event from IssueCoordinatedActor is stashed until the PersistentFSMActor(issue) is read from persistent medium and brought to its latest state. When the issue is in its latest state, the stashed event is played to the PersistentFSMActor(issue) Questions: I. Is the above aligned with the concepts of PersistentFSMActor? II. How can each issue be connected its own PersistentFSMActor? Any help is highly appreciated. Thanks. -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout. -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout. -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
