Currently, ECA converts models from proprietary modeller format (e.g. BPMN XML) into ECA config entities. The original model is also stored alongside the config entity and is used by the modeller for maintenance. Every time the modeller saves its model, ECA converts that to config again.
This is a one-way scenario and good enough, as long as the modeller is still being available and as long as the user doesn't want to replace the modeller for whatever reason.
If we were able to also convert from ECA config to modeller format, we would gain a lot of flexibility. We could define an interface which each modeller implementation needed to work against and they would be responsible to write the model in the correct syntax for themselves.
Gaining flexibility comes at some cost of course: implementing modellers will become more complex.
Postponed
2.1
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
