Object Reference Types in the Enterprise
Services Repository
Object Reference Types
There are different types of object references in the Enterprise Services Repository. The semantic conditions of the object types involved determine which object references are used. This cannot be altered by the user. Nevertheless, it is important to note the differences between the individual object reference types because they can behave differently when you copy an object.
The following types of object reference exist:
Object Reference Types in the Enterprise Services Repository
Object Reference Type |
Description |
Absolute object reference |
Software component version of the referenced object is not dependent on the software component version of the referencing object. After it has been copied to a new software component version, the referencing object references an object in the original software component version. The object reference is not damaged by the copying procedure because the referenced object already exists in the original software component version. In the case of absolute object references, you can select the software component version of the object used when you create the reference. |
Relative object reference |
Software component version of the referenced object is identical to the software component version of the referencing object. This also applies when the referenced object is located in a software component version on which the software component version of the referencing object is structured. After it has been copied to a new software component version, the referencing object references an object in the new software component version. Since the referenced object is not copied as well, the object reference initially cannot be followed. If, in the Enterprise Services Builder, you want to navigate to the referenced object from the copy of the referenced object, the system displays a message to this effect. So that the object reference becomes valid again, you must copy the referenced object with the same name to the new software component version SWC2 as well. The namespace of the copied referenced object must be the same as the namespace of the object that was originally referenced. In the case of relative object references, the software component version of the referenced object is fixed when the reference is created and cannot be selected. |
Automatic Object Reference |
If the software component version of the referenced object is identical to the software component version of the object to be referenced, then the automatic object reference acts like a relative object reference. Otherwise, the automatic object reference acts like an absolute reference. |
All object references between interface objects are relative object references.
Interface objects are only complete when they are together with the objects that they reference and must therefore always be shipped together.
The object reference from a message type to a data type is a relative object reference. Message type and data type must be in the same software component version. Both objects are shipped together.