conflictPotential element

Type:	conflictPotential
Namespace:	(default namespace)
XML Schema:	ns0.xsd

Change sets have a design time baseline, the base line change set that they were originally created from. More than one change set can be designed upon / created from a single base. Deployments have a deployment baseline, the deployment (within an environment) which they follow, like a link in a chain. Each deployment can have at most a single child deployment based on (linked to) it. We tolerate the deployment of two change sets based on the same base into a given environment only if there are no conflicts between the change set and the changes that it has 'inherited' by being deployed on a different deployment base (e.g. a child, or grand child (etc) of its original design time baseline). The reason we do this is to make it easier for (truly unrelated) change sets to be developed in parallel. Since change sets are editable even after deployment (in non-production environments), we need to be able to report conflicts that might have arisen since deployment, or which were known about but overridden at the time of deployment. This class is used to communicate that possibility to clients. It defines the branch (list of chained chain sets) that a change set deployment is exposed to via the above, and also any conflicts currently detectable against that branch. Deployment objects can optionally carry one of these objects in it, which allows the client to display the current conflicts to the user, thus allowing them to be resolved over time.

Example XML

<?xml version="1.0" encoding="UTF-8"?>
<conflictPotential>
  <branch>...</branch>
  <conflicts>
    <difference>
      <reasons>...</reasons>
      <reasons>...</reasons>
      <!--...more "reasons" elements...-->
      <type>...</type>
      <name>...</name>
      <resourceUrl>...</resourceUrl>
      <serviceResource>
        <resourceType>...</resourceType>
        <group>...</group>
        <name>...</name>
        <configuration>...</configuration>
        <key>...</key>
      </serviceResource>
      <validationIssues>
        <issueType>...</issueType>
        <activityPath>...</activityPath>
        <capabilityName>...</capabilityName>
        <exitNumber>...</exitNumber>
        <parameterNumber>...</parameterNumber>
      </validationIssues>
      <validationIssues>
        <!--...-->
      </validationIssues>
      <!--...more "validationIssues" elements...-->
      <revertible>...</revertible>
    </difference>
    <difference>
      <!--...-->
    </difference>
    <!--...more "difference" elements...-->
  </conflicts>
</conflictPotential>