WebSphere Process Server messages     Operating Systems: All supported
CWLBN0001I: A Business Graph cannot be marked as created
Explanation: Given DataObject is instance of BusinessGraph. MarkCreated API accepts only DataObjects which are instances of BusinessObjects.
User Action: Invoke the API by passing BusinessObject as a parameter instead of BusinessGraph.

 

CWLBN0002I: The DataObject is not in a Business Graph
Explanation: The DataObject passed as a parameter is a standalone BusinessObject that is not contained in any BusinessGraph.
User Action: Put the standalone DataObject in BusinessGraph hierarchy

 

CWLBN0003I: A Business Graph with a verb set to Delete cannot contain a created object.
Explanation: Verb of the BusinessGraph for the given DataObject is set to delete and thus it can'tbe marked as created.
User Action: Set the value of the verb to any value other than delete.

 

CWLBN0004I: A Business Graph with a verb set to Retrieve cannot contain a Created object.
Explanation: A Business Graph with a verb set to Retrieve cannot contain a Created object.
User Action: Set the value of the verb to any value other than retrieve.

 

CWLBN0005I: The given business object is already deleted and therefore cannot be marked as Created
Explanation: The specified business object is in the list of deleted objects of the change summary, so it cannot be marked as created.
User Action: The operation is not valid and cannot be performed on the specified business object. Change the code to avoid calling BOChangeSummary#markCreated() on a deleted business object.

 

CWLBN0006I: The business object has been created, so it cannot be marked as "updated".
Explanation: The specified business object is in the "created" list of the change summary because it is created after logging begins, so it cannot be marked as updated.
User Action: This operation cannot be performed on the specified business object. Change the code to avoid calling BOChangeSummary#markUpdated() on a created business object.

 

CWLBN0007I: The given DataObject is not contained in any container
Explanation: The given DataObject is not contained in any container
User Action: Make the given DataObject as a part of the BusinessGraph hierarchy.

 

CWLBN0008I: The business object is not in the data section, so it cannot be marked as updated.
Explanation: The business object not in the data section may be either deleted or stand-alone object. Therefore, users cannot mark it as updated in business graph.
User Action: Change the code to avoid calling BOChangeSummary#markUpdated() on a business object not in data section. Check the container type of this business object to determine if the container is a business object.

 

CWLBN0009I: The DataObject is deleted and therefore cannot be marked as updated
Explanation: The DataObject is deleted and and currently resides in the deleted list of the changeSummary. Thus it cannot be marked as updated.
User Action: This operation is invalid for the given DataObject.

 

CWLBN0011I: A Business Graph cannot be marked as deleted.
Explanation: A Business Graph cannot be marked as deleted. Input parameter can't be BusinessGraph instance
User Action: This operation is invalid for the given DataObject.

 

CWLBN0012I: A Business Graph with a verb set to Create cannot contain a deleted object.
Explanation: A Business Graph with a verb set to Create cannot contain a deleted object.
User Action: Set the value of verb to any value other than Create.

 

CWLBN0013I: A Business Graph with a verb set to Retrieve cannot contain a deleted object.
Explanation: A Business Graph with a verb set to Retrieve cannot contain a deleted object.
User Action: Set the value of verb to any value other than Retrieve.

 

CWLBN0014I: Add old values is not defined for properties with multiple values.
Explanation: This is a limitation of BOChangeSummary#addOldValue(). It supports adding value for single value property only, not multiple value property.
User Action: This operation is not valid for the given parameter. Change the code to avoid calling BOChangeSummary#addOldValue() with a multiple value property.

 

CWLBN0015W: The target property exists in the target object
Explanation: The property already been set in target object
User Action: Make sure that the property path is correct

 

CWLBN0016W: The source object cannot be a Business Graph object.
Explanation: The Business Graph object should be the root object, it can't been copied into another Business Graph or Business Object.
User Action: Make sure that the source object is a Business Object.

 

CWLBN0017W: The target path should be an empty list.
Explanation: The target path should be an empty list.
User Action: Make sure that the target path is empty.

 

CWLBN0018I: The copied property should be a simple type property.
Explanation: The copyPropertyInto() method only handle the simple type property.
User Action: Make sure that the copied property is a simple type property.

 

CWLBN0019I: The source DataObject type is different from the target type.
Explanation: The source DataObject type should be exactly same as the target type.
User Action: Make sure that the source DataObject type is the same as that of target type.

 

CWLBN0020I: The given schema is invalid because it contains more than one root level DataObject
Explanation: The given schema is invalid as it contains more than one root level DataObject
User Action: none

 

CWLBN0021I: A Business Graph does not have an old container.
Explanation: A Business Graph does not have an old container.
User Action: none.

 

CWLBN0022I: A data object is expected.
Explanation: BOXMLSerializer should always loads a date object from an XML file. A non-dataObject can be created if the XML file doesn't contain a business object instance.
User Action: Do not use BOXMLSerializer to load XML file which doesn't contain a business object instance. Check the XML file if it matches any of the business object definitions.

 

CWLBN0023I: No DataObjects were found in the document
Explanation: The XML document that was passed did not have any contents.
User Action: none

 

CWLBN0024I: There was no document found to save.
Explanation: No document was found to save.
User Action: Make sure that the document is valid.

 

CWLBN0026I: DataObject cannot be null.
Explanation: Dataobject that is expected to be saved cannot be null
User Action: Make sure that the DataObject is valid

 

CWLBN0027I: The root element cannot be null or empty.
Explanation: The root element that is passed to the serializer can't be a null or empty. The value should be a valid XML element name.
User Action: Do not call BOXMLSerializer#writeDataObject() with a empty or null root element as parameter.

 

CWLBN0028I: Because the old value exists, a new value for "old value" cannot be set.
Explanation: The old value already exists for a property in the change summary. User cannot specify another "old value" for this property.
User Action: Change the code to avoid calling this BOChangeSummary#addOldValue() on a property that already has old value. Use BOChangeSummary#getOldValue() to test if a property already has old value.

 

CWLBN0029I: Targetnamespace cannot be null.
Explanation: Targetnamespace passed as an input cannot be null.
User Action: Make sure that the Targetnamespace is valid.

 

CWLBN0030I: No container, resource, or DataGraph is allowed for the DataObject.
Explanation: No container, resource, or DataGraph is allowed for the DataObject.
User Action: none

 

CWLBN0031I: A business graph does not have an old container.
Explanation: A business graph object should always be the root container of its own graph. It doesn't have an old container.
User Action: Change the code to avoid calling BOChangeSummary#getOldContainer() with the business graph as the parameter.

 

CWLBN0032I: The DataObject was recorded as updated in the changeSummary and then it was Deleted while changeSummary was turned off.
Explanation: The DataObject was recorded as updated in the changeSummary and then it was Deleted while changeSummary was turned off.
User Action: Validation logic has detected inconsistency in the ChangeSummary data.

 

CWLBN0033I: The DataObject was recorded as created in the changeSummary and then it was Deleted while changeSummary was turned off.
Explanation: The DataObject was recorded as created in the changeSummary and then it was Deleted while changeSummary was turned off.
User Action: Validation logic has detected inconsistency in the ChangeSummary data.

 

CWLBN0034I: The feature is not a many value feature.
Explanation: The feature is not a many value feature.
User Action: The feature is not a many value feature.Thus this operation is not defined for it.

 

CWLBN1000E: The value ''{0}'' is not a valid value
Explanation: The property value set in the Business Object is not defined as part of the Union members.
User Action: Make sure the property value is defined as part of the Union members. Correct the value accordingly as specified in the schema.

 

CWLBN1001E: The value ''{0}'' of type ''{1}'' must be of type '{'{2}'}'
Explanation: The data type for this property value set in the Business Object is not one of the defined type in Union members.
User Action: Make sure the property type is defined as part of the Union member types. Correct the type accordingly as specified in the schema.

 

CWLBN1002E: The value ''{0}'' must be less than ''{1}''
Explanation: The property value is larger than the maxExclusive constraining facets defined in the schema.
User Action: Make sure the property value is less than the maxExclusive constraining facets. Correct the value accordingly as specified in the schema.

 

CWLBN1003E: The value ''{0}'' must be greater than ''{1}''
Explanation: The property value is less than the minExclusive constraining facets defined in the schema.
User Action: Make sure the property value is greater than the minExclusive constraining facets. Correct the value accordingly as specified in the schema.

 

CWLBN1004E: The value ''{0}'' must be less than or equal to ''{1}''
Explanation: The property value is larger than the maxInclusive constraining facets defined in the schema.
User Action: Make sure the property value is less than the maxInclusive constraining facets. Correct the value accordingly as specified in the schema.

 

CWLBN1005E: The value ''{0}'' must be greater than or equal to ''{1}''
Explanation: The property value is less than the minInclusive constraining facets defined in the schema.
User Action: Make sure the property value is greater than the minInclusive constraining facets. Correct the value accordingly as specified in the schema.

 

CWLBN1006E: The value ''{0}'' must be one of '{'{1}'}'
Explanation: The property value must be one of the defined values specified in Enumeration facet.
User Action: Make sure the property value is defined as part of the Enumeration value set. Correct the value accordingly as specified in the schema.

 

CWLBN1007E: The value ''{0}'' must match the pattern '{'{1}'}'
Explanation: The property is not matching the pattern constraining facet defined in the schema.
User Action: Make sure the property value is matching the pattern constraining facet. Correct the value accordingly as specified in the schema.

 

CWLBN1008E: The value ''{0}'' with length {1} must be of length {2}
Explanation: The property length is not the same as the Length constraining facet defined in the schema.
User Action: Make sure the property length is same as the Length constraining facet. Correct the value accordingly as specified in the schema.

 

CWLBN1009E: The value ''{0}'' with length {1} must have at least length {2}
Explanation: The property length is less than the Length constraining facet defined in the schema.
User Action: Make sure the property length is at least as the Length constraining facet. Correct the value accordingly as specified in the schema.

 

CWLBN1010E: The value ''{0}'' with length {1} may have at most length {2}
Explanation: The property length is over the Length constraining facet defined in the schema.
User Action: Make sure the property length is no more than the Length constraining facet. Correct the value accordingly as specified in the schema.

 

CWLBN1011E: The value ''{0}'' may have at most {1} digits
Explanation: The property value has more digits than the Digit constraining facet defined in the schema.
User Action: Make sure the property value has less digits than the Digit constraining facet. Correct the value accordingly as specified in the schema.

 

CWLBN1012E: The value ''{0}'' may have at most {1} fraction digits
Explanation: The property value has more fraction digits than the Fraction digit constraining facet defined in the schema.
User Action: Make sure the property value has less fraction digits than the Fraction digit constraining facet. Correct the value accordingly as specified in the schema.

 

CWLBN1013E: The value ''{0}'' must be match one of '{'{1}'}'
Explanation: The property is not matching the pattern constraining facet defined in the schema.
User Action: Make sure the property value is matching the pattern constraining facet. Correct the value accordingly as specified in the schema.

 

CWLBN1014E: The property ''{0}'' of ''{1}'' is not nillable, but has a value of null
Explanation: A property that cannot be set to null has been set to null.
User Action: Do not set the property to null.

 

CWLBN1015E: The property ''{0}'' of ''{1}'' with {2} values must have at least {3} values
Explanation: A property has fewer values than it must have.
User Action: Make sure the property is set with at least the minimum number of values required.

 

CWLBN1016E: The property ''{0}'' of ''{1}'' with {2} values may have at most {3} values
Explanation: A property has more values than it may have.
User Action: Make sure the property is set with at most the msximum number of values allowed.

 

CWLBN1017E: The value ''{0}'' of type ''{1}'' must be of type ''{2}''
Explanation: A property is of a type incompatible with what is expected for that property.
User Action: Ensure that the property is of the correct type.

 

CWLBN1018E: Errors occurred validating the BO ''{0}''
Explanation: The BusinessObject being validated has errors identified where it does not match the requirements specified in the schema describing the BO.
User Action: Correct the values in the fields identified as being in error.

 


Reference topic

Terms of use | Feedback

Timestamp icon Last updated: 9 June 2009