The use case which will provide more usability is:

• provide subnodes for each data stores entries
• be able to configure each Data Store entries (Destination and server) in the property view

I don't see any easy extensible possibilities without introducing another extension point helping to build the internal model.

With the current model, I would just add org.fusesource.ide.camel.editor.provider.ext.ICustomGlobalConfigElementContribution.canHandle(AsbtractCamelModelElement) and org.fusesource.ide.camel.editor.provider.ext.ICustomGlobalConfigElementContribution.onGlobalElementDeleted(AsbtractCamelModelElement) (previously based on Node)

We will need to be able to convert EMF models on each modification with AsbtractCamelModelement (and vice/versa). Not sure about the performance impact.

I evaluate it to a one week work (one week fully dedicated to that)

For now I would recommend to just modify canHandle and onGlobalElementDeleted interface to be based on Internal model instead of Node