Closed don-vip closed 5 years ago
Could you give that test project so that I could run it myself. I don't immediately where things might go wrong.
Sure, I'm working on producing a standalone project. I started debugging the problem and noticed my machine initialization results in two internal machines created in AbstractStateMachineFactory.getStateMachine(UUID, String)
:
Something goes wrong when that uml file is parsed and it's sometimes difficult to point exact issue until you follow debugs. I didn't see issue straight out from uml why parsing things there are states associated with multiple machines, as that would then try to create multiple machines. Think I find it quickly if I can run this project.
Right, looks like a some sort of dump bug in a parser. Looks like when I added a name to a choice, it doesn't fail anymore.
<subvertex xmi:type="uml:Pseudostate" xmi:id="_ozCHYKuaEeihzLPJstSt-Q" kind="choice" name="CHOICE"/>
At least when I manually added this file to uml parsing tests. Can you verify this as well as I think you didn't name that choice field in papyrus. I remember doing some auto-naming for some fields but it may be that forget to check these pseudostates.
I created a small Spring Boot project showing the problem. Simply run the application (it fails to start): spring-statemachine-issue591.zip
Thanks for your quick analysis! I confirm adding a name to the choice solves the problem :)
I'm trying to implement with 2.0.2 a simple state machine which begins by a choice. I am unable to do so and always face this error:
I tried two variants of it, as I wondered if having two transitions towards the final state are allowed or not in UML:
But the result is the same. Here is my Java config:
Is my diagram somewhat invalid or is it a bug? The message is not clear, as I have defined an initial state.