-
Notifications
You must be signed in to change notification settings - Fork 38
Rfc6:Motherapplication updates mashup components
When making a mashup of an application (the "mother application"), it should be possible to propagate the configuration of the components in the motherapplication to the corresponding components in the mashup(s). This RFC covers the implementation of that change.
The changes needed for the completion of this functionality are described here.
The modules which are affected by these changes are split in the viewer, viewer-admin and database.
The viewer doesn't have to be changed.
When creating a mashup, the user should define if the changes made to components in the mother application should be propagated to the mashup.
If so: When updating a component in the mother application, the viewer-admin must retrieve all the mashups, and update all the components which have a reference to this updated component.
When the user deletes a component from the mother application, all referencing configured_components should be uncoupled: the reference must be set to null.
configured_component
add reference to itself
We foresee no incompatibility with older version. All the old configurations will be kept and remain functional. Existing mashup don't have a reference.