Deprecate eca.model config entity type

The raw data from the modeler will either be ignored or stored in thirdparty settings of the eca.eca config entity.

You want to store the BPMN XML data in third party settings of eca.eca.* configuration entities? This will mean a significant load overhead when loading an ECA process configuration just for execution. Until now by separating this, loading that data was only done when needed (i.e. when configuring ECA via UI).

Yes, the overhead of handling a separate config file outweighs that easily. And the XML data storage will be optional, so it can be turned off, as we can now open ECA models in bpmn_io without having the XML data available. So, users who're worried about the size of the XML data will be able to turn their storage off.

So, users who're worried about the size of the XML data will be able to turn their storage off.

Our clients are using the modeler UI in order to better understand it. And one particular detail is the way *they* have arranged & placed the items in that modeler, not how the system would do this automatically. It is a visual helper which brings massive value for better understanding. So I don't think this is an acceptable compromise.

Yeah, one can not have everything at any time.

There is another option, which should be easy to implement:

We move this over to the Modeler API and provide 3 options in the configuration for each combination of model owner and modeler:

1. Do not save raw model data at all
2. Do save raw model data as third-party setting with the model owner's config entity
3. Do save raw model data in a separate config entity

This will be implemented in 📌 Extend handling of raw model data Active .

The proposal from #6 is now implemented in modeler_api 1.0.x