Designer 10.15 | Centrasite Eclipse UI Help | Tasks | Working with Registry Objects | Versioning Services
 
Versioning Services
 
Handling of Associations
When you create a new version of a registry object of the Service type, the following actions are performed:
*A new registry object of the Service type is created, which represents the new version and has its own key.
*The name and description of the old version are copied to the new version. You can modify them later, if required, either manually or by attaching a new WSDL file to the new service version.
*The Namespaces of the new version is the one you specify in the New Version wizard.
*The Properties of Registry Objects of the old version are copied to the new version, except for the following: The new version has its own unique key. The user version identifier of the new version is the one you specify in the New Version wizard.
*The major version number of the CentraSite version identifier is increased by 1 for the new version, the minor version number is set to 0.
*The Status, Stability and Expiration of Registry Objects of the old version are copied to the new version.
*The new version is assigned to the same organization as the old version.
*The new version is assigned the same internal and external Classifying Registry Objects as the old version.
*The service bindings and specification links of the old service version are copied to the new version. Registry objects which are referenced by the specification links (e.g. Interface objects) are also copied. If these objects are versionable, the copies are represented as new versions. The new service version re-uses all required files of the old version in the repository. New versions of the relevant External Links are created, which link the new service version and the existing files.
* Associations Between Registry Objects of the old service version as well as of its service bindings and specification links are copied to the new version according to the rules described below.
* Attributes of the old version are copied to the new version. See above for the actions performed for properties, classifications, associations or external links. The same actions are performed when copying attributes that visualize properties, classifications, associations or external links.
*Subscriptions for Notifications at the old version are NOT copied to the new version. Similarly, if you added the old version to your Using Favorites, the new version is NOT added automatically.
*The Security Settings for Registry Objects of the old version are copied to the new version.
*The Audit Logs of the old version is copied to the new version, and a new entry is added for the versioning operation at the new version.