WebSphere Process Server messages     Operating Systems: All supported
CWLAF0001E: A managed role is already defined for the {0} relationship.
Explanation: A one-to-one (identity) non-static relationship must have only one managed role.
User Action: In the Relationship editor, select the specified relationship and the role. In the Properties view, on the Details tab, clear the Managed checkbox on all roles except the one you want to specify as managed.

 

CWLAF0002E: No managed role was defined for the {0} relationship.
Explanation: Each identity and non-static relationships requires one managed role.
User Action: In the Relationship editor, select the specified relationship and the role to be managed. In the Properties view, on the Details tab, select the Managed checkbox.

 

CWLAF0003W: Managed roles are not required in non-identity relationship {0}.
Explanation: Non-identity relationships do not use managed roles.
User Action: In the Relationship editor, select the specified relationship and the role. In the Properties view, on the Details tab, clear the Managed checkbox.

 

CWLAF0004E: The {0} role is missing a key attribute.
Explanation: Each role requires at least one key attribute.
User Action: In the Relationship editor, select the specified role. Select the Add key attribute icon and add at least one key attribute.

 

CWLAF0005E: The {0} managed role has multiple key attributes.
Explanation: Each managed role must have only one key attribute.
User Action: In the Relationship editor, select the specified relationship and the role. Select the key attribute you want to remove and select Remove key attribute icon.

 

CWLAF0006E: The path of the {0} key attribute in the {1} role cannot start with a forward slash (/).
Explanation: The forward slash character is not allowed at the beginning of a key attribute path.
User Action: In the Relationship editor, select the specified role and the specified key attribute in the role. In the Properties view, on the Description tab, click Change and select the path to the new key attribute.

 

CWLAF0007E: The path of the {0} key attribute in the {1} role cannot end with a forward slash (/).
Explanation: The forward slash character is not allowed at the end of a key attribute path.
User Action: In the Relationship editor, select the specified role and the specified key attribute in the role. In the Properties view, on the Description tab, click Change and select the path to the new key attribute.

 

CWLAF0008E: The path of the {0} key attribute in the {1} role must not contain multiple slash (//).
Explanation: Only the single forward slash character (/) is allowed in a path, and it is not allowed at the beginning or at the end of the path.
User Action: In the text editor, open the role file and remove the multiple forward slashes from the key attribute path.

 

CWLAF0009E: The {0} relationship already exists in the workspace.
Explanation: The specified relationship name is being used. The qualified name of a relationship (name and namespace) must be unique in the workspace.
User Action: In the Business Integration view, delete one of the relationships that share the same name.

 

CWLAF0010E: The {1} role already exists in the {0} relationship.
Explanation: The specified role name is being used. The qualified name of a role (name and namespace) must be unique in the workspace.
User Action: In the Relationship editor, select the specified role and delete one of the roles that share the same name.

 

CWLAF0011E: The {0} business object referred to in the {1} role is not defined.
Explanation: The specified business object does not exist in the current or dependency projects.
User Action: In the business object editor, add the business object. Alternatively, in the relationship editor, refer the role to another business object that exists.

 

CWLAF0012E: The {0} key attribute used in the {1} role is not defined.
Explanation: The specified attribute does not exist in any business object definition in the current or dependency projects. One possible reason is that the attribute's path is incorrect.
User Action: In the business object editor, add the attribute to the business object. Alternatively, in the relationship editor, refer the role to another attribute that exists.

 

CWLAF0013E: The {0} relationship is not defined.
Explanation: The relationship does not exist in the current or dependency projects.
User Action: In the Business Integration view, delete this role. Then create a new relationship.

 

CWLAF0014E: The {0} role is not defined.
Explanation: A role that the relationship instance data file (<relationshipname>.ri) refers to does not exist.
User Action: In the Physical Resource view, open the relationship instance data file (<relationshipname>.ri) using the text editor. Remove the roleInstance elements in all sections for the role.

 

CWLAF0015E: The {0} property is not defined in the {1} relationship or role.
Explanation: The specific property does not exist in the current or dependency projects.
User Action: Open the relationship in the relationship editor and add the specified property for the relationship or for the role.

 

CWLAF0016E: The {0} key attribute is not defined in the {1} role.
Explanation: A key attribute used in the relationship instance does not exist in the role.
User Action: If the relationship instance data is necessary, then add the key attribute to the role in the relationship editor. If you no longer need the defined instance data, then go to the Physical Resource view, open the relationship instance data file (<relationshipname>.ri) and remove the defined values for the key attribute in all role instances.

 

CWLAF0017E: There are no key attributes defined for the {0} role in the relationship instance data.
Explanation: The key attribute value does not exist in the specified role definition.
User Action: In the relationship editor, select the relationship that contains specific role. In the Properties view, on the Instance Data tab, expand an instance ID and then select the role Instance with the specified role name. Enter a value for the key attribute.

 

CWLAF0018E: The schema of the relationship instance data file (.ri) is not correct.
Explanation: The root element of the schema must be relationshipInstance, relationshipInstanceBG, or relationshipInstanceRoot.
User Action: In the Physical Resource view, edit the relationship instance data file (<relationshipname>.ri) with a text editor, and correct the schema.

 

CWLAF0019E: The data for the {0} property is already defined in the {1} relationship.
Explanation: The relationship instance data file (<relationshipname>.ri) must not contain more than one data definition per property.
User Action: In the Physical Resource view, open the relationship instance data file (<relationshipname>.ri) for the relationship using the text editor. Remove one of the duplicate property definitions.

 

CWLAF0020E: The data for the {0} property is already defined in the {1} role.
Explanation: The relationship instance data definition must not contain more than one data definition per role property.
User Action: In the Physical Resource view, open the relationship instance data file (<relationshipname>.ri) for the relationship using the text editor. Remove one of the duplicate property definitions.

 

CWLAF0021E: The data for the {0} key attribute is already defined in the {1} role.
Explanation: The relationship instance data definition must not contain more than one data definition per key attribute.
User Action: In the Physical Resource view and open the relationship instance data file (<relationshipname>.ri) for the relationship using the text editor. Remove one of the duplicate attribute definitions.

 

CWLAF0022E: The {0} data type of the {1} property is not valid.
Explanation: A list of valid data types is defined in the XML Schema specification at (http://www.w3.org/TR/xmlschema-2/#built-in-datatypes).
User Action: In text editor, change the data type of the specific property to one of the valid data type.

 

CWLAF0023E: The {1} role in the {0} static relationship cannot be set to managed.
Explanation: A static relationship must not contain a managed role.
User Action: In the Relationship editor, select the specified relationship and the role. In the Properties view, on the Details tab, Clear the Managed checkbox.

 

CWLAF0024E: The value of the {0} key attribute of the {1} role is not defined.
Explanation: For static relationships, all key attribute values must be defined.
User Action: In the relationship editor, select the relationship that contains the specific role. In the Properties view, on the Instance Data tab, expand the marked instance ID and enter a value for the key attribute.

 

CWLAF0025E: The value of the {0} key attribute of the {1} role is empty.
Explanation: For static relationships, all key attribute values must be specified.
User Action: In the relationship editor, select the relationship that contains the specific role. In the Properties view, on the Instance Data tab, expand the marked instance ID and enter a value for the key attribute.

 

CWLAF0026E: The role instance data definition is missing for the {0} instance ID in the {1} relationship.
Explanation: Relationship instance definitions must contain at least one role definition per role in the relationship instance data file (<relationshipname>.ri). The validation detected that the syntax of the file is incorrect.
User Action: In the relationship editor, select the relationship. In the Properties view, on the Instance Data tab, create a new relationship instance definition and then remove the instance data definition for the specified instance ID.

 

CWLAF0027E: The index for the {0} multiple-cardinality key attribute in the {1} path of the {2} role is missing.
Explanation: Skipped levels of child business objects are not allowed if this child business object has multiple cardinality and no index is specified for it.
User Action: In the relationship editor, select the role and then select the key attribute that contains the error. In the Properties view, click Set to change the key attribute. Define one index on each business object level.

 

CWLAF0028E: The {0} path used to define a key attribute for the {1} role is not allowed.
Explanation: Another key attribute exists from another child business object that belongs to the same parent business object. Key attributes from different child business objects that belong to the same parent business object are not allowed in a role.
User Action: In the relationship editor, select the specified role and define the key attribute. Make sure that you use a key attribute from only one child business object.

 

CWLAF0029E: The {0} role contains a complex type key attribute with the {1} path.
Explanation: A key attribute must be a simple type property of a business object. It cannot have a complex type property as the key attribute.
User Action: In the relationship editor, select the role and remove the key attribute that is not valid. Add a new key attribute with a simple type property of a business object.

 

CWLAF0030E: An index is not allowed in the path of the {0} key attribute of the {2} role.
Explanation: Index values can only be set for array attributes.
User Action: In the relationship editor, select the role. Remove the key attribute that is not valid and add a new one with a valid index setting.

 

CWLAF0031E: An index is missing in the path setting of the {0} key attribute in the {2} role.
Explanation: Index values must be defined for all array attributes of a selected key attribute.
User Action: In the relationship editor, select the role. Remove the key attribute that is not valid and add a new one with a valid index setting. To manually add the missing index, open the relationship instance data file (<relationshipname>.ri) and the role file (<rolename>.rol) in the text editor, and add the index to path of the array attribute in the format of attribute[i], where i is the index and i must start from 1.

 

CWLAF0032E: The character {0} is not allowed in the relationship or role name {1}.
Explanation: Relationship and role names cannot contain periods (.) or forward slashes (/) or hypens (-).
User Action: In the relationship editor, select the relationship or role and change the name in the Properties view. Do not use Refactor > Rename.

 

CWLAF0033E: The {0} key attribute type that is used in the {1} role is not valid for a dynamic relationship.
Explanation: The following key attribute types are not valid in a dynamic relationship: date, dateTime, time, hexBinary, any, anyType, anySimpleType, and anyAttribute.
User Action: Double-click the error message. Select the specified role and then select the specified key attribute. In the Properties view, on the Description tab, select Change to change the specified key attribute to a valid type.

 

CWLAF0034W: The {0} property of the {1} business object that is defined as a key attribute for the {2} role is marked as optional.
Explanation: The specified property that is used as a role key attribute must not be set as an optional property because an error will occur if the property is missing during run time.
User Action: In the Business Integration view, open the specified business object and select the specified property. In the Properties view, on the Description tab, and then select the Required check box.

 

CWLAF0035E: The {0} key attribute in the {1} role cannot be of the union or list type.
Explanation: Key attributes of the union type are not valid in relationships.
User Action: Double-click the error message. Select the specified role and then select the specified key attribute. In the Properties view, on the Description tab, select Change to change the specified key attribute to a valid type.

 

CWLAF0036E: The {0} key attribute of the {1} role refers to a business object attribute that is of the array type, but there is no index specified in the {2} path.
Explanation: In a static relationship, an index is required when you use a business object attribute of the array type so that the element of the specified index can be used as the key attribute.
User Action: Double-click the error message. Select the specified role and then select the specified key attribute. In the Properties view, on the Description tab, select Change. In the table, click in the Index field of the specified key attribute and then specify the index.

 

CWLAF0037E: The {1} role of the {0} static lookup relationship has multiple key attributes.
Explanation: Static lookup relationships support only roles with one key attribute; multiple key attributes are not allowed.
User Action: Double-click the error message. Select the specified role and remove the additional key attributes from the role.

 

CWLAF0038E: The {0} key attribute type that is used in the {1} role is not valid for a static lookup relationship.
Explanation: The following key attribute types are valid for a lookup relationship: Boolean, double, float, int, long, and string.
User Action: Double-click the error message. Select the specified role and then select the specified key attribute. In the Properties view, on the Description tab, select Change to change the specified key attribute to a valid type.

 

CWLAF0039W: The {0} key attribute type of the {1} role in the dynamic relationship is an enumerated type.
Explanation: Enumerated types are not generally used in dynamic relationships because the values for the key attribute should not be limited to the enumeration values.
User Action: Double-click the error message. Select the specified role and delete the specified key attribute. Add a new key attribute.

 

CWLAF0040E: The path of the {0} element in the {1} role cannot begin with the @ character.
Explanation: The @ character can be used only before an attribute path to distinguish the attribute from other properties or business objects.
User Action: In a text editor, open the file for the specified role and remove the @ character from the element path.

 

CWLAF0041E: The {0} instance data value for the {1} key attribute of the {2} role is not valid.
Explanation: The key attribute instance data must be consistent with respect to its type.
User Action: Double-click the error message and select the relationship icon. In the Properties view, on the Instance Data tab, change the instance data of the key attribute to a value that is consistent to its data type (for example, the value for an integer type should a number, not a string).

 

CWLAF0042W: The {0} attribute of the {1} business object that is defined as a key attribute for the {2} role is not marked as required.
Explanation: The specified attribute that is used as a role key attribute must not be set as an optional or prohibited because an error will occur if the property is missing during run time.
User Action: In the Business Integration view, open the specified business object and select the specified attribute. In the Properties view, on the Description tab, and then select the Required check box.

 

CWLAF0043E: The {0} role cannot be simple type for non-static relationship.
Explanation: Only static relationship allows simple type as role type.
User Action: Open the relationship in the relationship editor and modify the type for the role.

 


Reference topic

Terms of use | Feedback

Timestamp icon Last updated: 9 June 2009