Skip to content

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

Closed
23 tasks done
jvalkeal opened this issue Jan 18, 2017 · 0 comments
Closed
23 tasks done

Backport 1.2.x changes for 2.0.0.M1 #307

jvalkeal opened this issue Jan 18, 2017 · 0 comments
Labels
for/backport For backporting
Milestone

Comments

@jvalkeal
Copy link
Contributor

jvalkeal commented Jan 18, 2017

@jvalkeal jvalkeal added the for/backport For backporting label Jan 18, 2017
@jvalkeal jvalkeal added this to the 2.0.0.M1 milestone Jan 18, 2017
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 Jan 18, 2017
- Backport #292
- Backport #224
- Add support so that @WithStateMachine can be used with
  machines build via @EnableStateMachineFactory or via
  manual builders.
- Adding new annotation @EnableWithStateMachine to help
  handling needed context configuration.
- Add tests and docs.
- 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 that referenced this issue Mar 9, 2017
- Add new tests for DefaultStateMachineExecutor to find
  possible causes for a deadlock.
- Handle lifecycle scenario little differently
  if timer is fired during a executor starting phase
  order to not getting into a deadlock.
- Backport #315
- Relates to #307
jvalkeal added a commit that referenced this issue Mar 9, 2017
- Add support to uml parser to properly
  detect and use exit/entry points if those
  are used via connection ref points with
  submachine references.
- Backport #323
- Relates to #307
jvalkeal added a commit that referenced this issue Mar 9, 2017
- Add new api to Transition to expose calling
  its actions.
- Modify rest of a framework to first notify before
  calling transtion action.
- Backport #322
- Relates to #307
jvalkeal added a commit that referenced this issue Mar 9, 2017
- Trying to handle scenario where TimerTrigger keeps firing
  even if machine is stopped or has moved away from its
  hosting state.
- Explicitely handle trigger starts/stops in
  DefaultStateMachineExecutor when executor itself
  is started/stopped.
- Backport #321
- Relates to #307
@jvalkeal jvalkeal changed the title Backport 1.2.x changes Backport 1.2.x changes for 2.0.0.M1 May 5, 2017
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
- Change processor registration so that if @WithStateMachine is
  used with 'id', 'name' is skipped because it defaults to 'stateMachine'
  and would cause extra registration.
- Relates #307
- Backport #370
jvalkeal added a commit that referenced this issue Jul 9, 2017
- Add missing support for defining more than one
  end states and as it's just missing from javaconfig.
- Backport #368
- Relates #307
jvalkeal added a commit that referenced this issue Jul 9, 2017
- Fix case where method was annotated with
  @OnExtendedStateChanged(key = "V1"), V1 was
  changed which didn't result call to that method.
- Backport #387
- Relates #307
jvalkeal added a commit that referenced this issue Jul 9, 2017
- Fix AbstractStateMachinePersister to handle
  recursive machines and regions.
- Backport #391
- Relates #307
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
jvalkeal added a commit that referenced this issue Jul 9, 2017
- As passing in null context don't have any
  meaning other than doing reset with pre-defined
  behaviour which currently just resets back to
  initial state and clears extended state variables.
  Now Also clearing machine id back to null which is
  anyway a default value.
- Backport #381
- Relates #307
jvalkeal pushed a commit that referenced this issue Nov 12, 2017
jvalkeal added a commit that referenced this issue Nov 12, 2017
- In AbstractStateMachineFactory change used holder map
  to list so that same states don't get lost because of
  used key.
- Backport #416
- Relates #307
jvalkeal added a commit that referenced this issue Nov 12, 2017
- Makes things less chatty if BeanFactory is null in
  StateMachineHandlerCallHelper as this is usually a case
  with manual builders outside of app context.
- Backport #412
- Relates #307
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for/backport For backporting
Projects
None yet
Development

No branches or pull requests

1 participant