At the moment, at migrate time, add or remove elements is not allowed - only update of properties within the existing elements is allowed.

Breakdown

  • ACm-Runtime: in validation migrate POST, it will allow to add and remove elements. ACM-runtime will understand new and removed elements matching with the element-id of the migration with the old instance.
  • Participant-intermediary: it will merge properly elements and properties 
  • Participant: participant has the responsibility to deploy the new elements and undeploy the removed elements during migration.
  • It will possible to understand new and removed elements matching with the element-id of the migration with the old instance
  • this functionally could be implemented after new/old properties functionality (The participant needs to be aware of both the old properties and the new)


    void migrate(CompositionElementDto compositionElement, CompositionElementDto compositionElementTarget,
                 InstanceElementDto instanceElement, InstanceElementDto instanceElementMigrate) throws PfModelException;

Note

The composition in/outProperties are connected to the element definition, so when an element is removed means that in/outProperties of the old composition will continue to stay available till that composition is primed.

The instance in/outProperties are connected to the instance element, so when an element is removed means that in/outProperties will be removed, and after the migration they will be not available anymore.

  • No labels