close

Filter

loading table of contents...

Blueprint Developer Manual / Version 2010

Table Of Contents
5.6.2.4.7  AutoMergeSyncAction

This action extends the AutoMergeTranslationAction and allows to configure a merge strategy. See Javadoc of AutoMergeSyncAction for details.

mergeStrategyVariable
Required no
Description The name of the variable into which the merge strategy bean name is stored. The bean name refers to a bean in the spring application context that is an implementation of ThreeWayMerge.

Table 5.37. Attributes of AutoMergeSyncAction


<AggregationVariable name="derivedContents" type="Resource"/>
<AggregationVariable name="masterContentObjects" type="Resource"/>
<AggregationVariable name="autoMergeConflicts" type="Resource"/>
<Variable name="performer" type="User"/>
<Variable name="mergeStrategy" type="String"/>

<AutomatedTask name="Synchronize">
  ...
  <Action class="com.coremedia.translate.workflow.synchronization.AutoMergeSyncAction"
          autoMergePredicateFactoryName="allMergeablePropertiesPredicateFactory"
          derivedContentsVariable="derivedContents"
          masterContentObjectsVariable="masterContentObjects"
          resultVariable="autoMergeConflicts"
          performerVariable="performer"
          escalateOnConflict="true"
          mergeStrategyVariable="mergeStrategy"/>
</AutomatedTask>

      

Example 5.46. Usage of AutoMergeSyncAction


A custom merge strategy for a synchronization workflow can be configured by either by implementing the interface ThreeWayMerge or SyncThreeWayMerge and adding the bean to the spring application context. The interface SyncThreeWayMerge allows control about whether a property needs to be merged or updated.

The bean name can be passed to the synchronization workflow via the variable mergeStrategy. How to add a custom merge strategy to the studio client is decribed in Section 7.22.4, “Synchronization-Specific Customizations” in Studio Developer Manual.

Search Results

Table Of Contents