-
Notifications
You must be signed in to change notification settings - Fork 627
Backport 1.2.x changes for 2.0.0.M1 #307
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
for/backport
For backporting
Milestone
Comments
jvalkeal
added a commit
that referenced
this issue
Jan 18, 2017
- Backport #298 - Factory now listens machine event if autostart is requested which should give fully started machine i.e. if asynch executor is used. Bails out after 30 seconds. Further tweaks like allowing user to define this time or conditionally not wait could be added later. - Fix typos. - Relates to #307
jvalkeal
added a commit
that referenced
this issue
Feb 10, 2017
- Modify StateMachineConfiguration and StateMachineFactoryConfiguration so that if you have different states and events classes with multiple machines or factories, you can autowire by types without adding qualifiers. - Manually try to discover generic types from enclosing adapther class and if succesfull pass that information into bean definition as ResolvableType. - Backporting #306 - Relates to #307
jvalkeal
added a commit
to jvalkeal/spring-statemachine
that referenced
this issue
May 5, 2017
- Add missing serialisation for history map and machine id - Fix possible NPE with extended state - Backport spring-projects#331 - Backport spring-projects#333 - Relates spring-projects#307
jvalkeal
added a commit
to jvalkeal/spring-statemachine
that referenced
this issue
May 5, 2017
- Polish to do checks for debug/trace logs - Backport spring-projects#329 - Relates spring-projects#307
jvalkeal
added a commit
to jvalkeal/spring-statemachine
that referenced
this issue
May 5, 2017
- Executor is following anonymous transitions in a loop and if there is an exception in actions with this transition, effectively executor ended into infinite loop. - No bailing out from this loop if we cannot continue. - Backport spring-projects#344 - Relates spring-projects#307
jvalkeal
added a commit
to jvalkeal/spring-statemachine
that referenced
this issue
May 5, 2017
- Now calling post state interceptor with correct/same state as pre. - Backport spring-projects#353 - Relates spring-projects#307
jvalkeal
added a commit
to jvalkeal/spring-statemachine
that referenced
this issue
May 5, 2017
- Adding support for javaconfig/uml to define actions for transitions leading out from a choice or junction states. - Support for action for incoming transition is already implemented as it is defined as normal transition. - Backport spring-projects#108 - Relates spring-projects#307
jvalkeal
added a commit
that referenced
this issue
May 19, 2017
- Adding null check for current state - Remove synchronization from scheduleEventQueueProcessing method in executor. Looks like this sync is not really needed and indeed may cause jvm level deadlocks if threads are used for execution. - Change how some internals in AbstractStateMachine are synchronized to limit changes for deadlock. - Relates to #307 - Backport of #359 #360
jvalkeal
added a commit
that referenced
this issue
Jul 9, 2017
- Fixing machine lifecycle logic when machine is restored which effectively should not touch any lifecycle methods as start/stop is user level action. - Remove start/stop from restore and attempt to do same when root machine is started. This also needed some further changes as some functionality for restore was essentially broken - Backport #386 - Relates #307
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue to track needed backports from branch 1.2.x into master.
The text was updated successfully, but these errors were encountered: