If I understand correctly, that's exactly what WebFlow is for. Either <action-state>
or <decision-state>
give you the ability to examine model objects (and other objects) and choose different transitions based on what you read.
Choose next view-state dynamically based on Model state?
-
25-09-2022 - |
Question
With Spring WebFlow, is it possible to avoid hard-wiring the possible transitions between view-states ?
I am thinking of getting the name of the next view-state
based on model validation rules.
That would be a way of creating a work-flow based on the model state.
Solution
Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow