- CWLDE0000E: The validator was unable to validate the state machine due to an unexpected failure.
- Explanation: An exception was caught by the state machine validator. This exception should have been logged to the workspace log file.
- User Action: The workspace log file should contain an exception stack dump. Save a copy of the log file and a copy of your workspace. This information will assist IBM support in determining the cause of the problem.
- CWLDE0001E: The transition that starts the state machine does not have an operation.
- Explanation: The transition that starts the state must define which operation will create a new instance of the state machine.
- User Action: In the transition that starts the state machine, add one of the operations that one of the interfaces defined.
- CWLDE0002E: Automatic transitions are not supported for looping transitions.
- Explanation: The source and target states of the transition are the same. The automatic transition is not supported in this context because it can cause an infinite loop.
- User Action: Add either an operation or a timer to this transition.
- CWLDE0003E: The transition contains an operation, a duration, or an expiration element.
- Explanation: The transition from the initial state in a composite state must contain only the automatic element.
- User Action: Delete the operation, duration, or expiration element so that the transition contains only an automatic element.
- CWLDE0004E: The transition must contain one and only one of the following elements: automatic, operation, duration, or expiration.
- Explanation: Because a transition is characterized as automatic, operation-based, or timer-based, it cannot respond to more than one type of the following transition types: automatic, operation, duration, or expiration.
- User Action: Remove all except one of these elements.
- CWLDE0005E: The composite state has more than one default transition.
- Explanation: A default transition is a transition whose source state is a composite state and that does not contain a timer, an operation, or a condition. The default transition is taken when any final state in the composite state is reached. Only one default path is allowed.
- User Action: Remove the extra default transitions.
- CWLDE0006E: This transition will never be followed.
- Explanation: There are multiple transitions from the state, and one of the other transitions has been configured so that it will always be selected first.
- User Action: Either remove this transition, or reconfigure the other transition(s).
- CWLDE0007E: Because the state does not have incoming transitions, it is disconnected from the rest of the state machine.
- Explanation: Because the state is disconnected from the rest of the state machine, the state machine can never enter this state.
- User Action: Create a new transition from another state to this state. If the state is not needed, delete it.
- CWLDE0008W: Because the state does not have outgoing transitions, it disconnected from the rest of the state machine.
- Explanation: If a state does not have outgoing transitions, the state machine cannot exit this state once it is entered.
- User Action: Create a new transition from this state, and connect it to another state.
- CWLDE0009E: The default transition for a composite state has a condition defined on it.
- Explanation: When there is a condition defined on the default transition, the flow out of a composite state could become blocked.
- User Action: Use the state machine editor to remove the condition.
- CWLDE0010E: The transition from an initial state has a condition defined on it.
- Explanation: Because the initial state may have only one outbound transition, the flow to the next state cannot be blocked by a guard condition.
- User Action: Use the state machine editor to remove the condition.
- CWLDE0011E: The variable name {0} is reserved and cannot be used for another variable.
- Explanation: This name is reserved for the state machine to use internally.
- User Action: Use the property view of the state machine editor to specify another name for the variable.
- CWLDE0012I: The main state machine contains a terminate state.
- Explanation: A terminate state is typically used only in composite states to abruptly terminate the entire state machine.
- User Action: Consider using a final state instead.
- CWLDE0013E: The {0} variable has already been defined in this state machine.
- Explanation: State machines do not allow two variables with the same name.
- User Action: Use the property view of the state machine editor to specify another name for the variable.
- CWLDE0014E: Duration and expiration elements must not contain invoke elements.
- Explanation: The duration and expiration elements are extensions of another element that allows either a Java snippet or an invoke element. However, an invoke element is not allowed for duration and expiration elements.
- User Action: Remove the invoke element and add either a specific timeout value or Java code snippet.
- CWLDE0015E: An internal transition is not allowed.
- Explanation: A composite state must not have a self transition where the transition is marked as internal.
- User Action: Use the property view of the state machine editor to remove the internal setting from the transition.
- CWLDE0016E: The action or the condition is incorrect.
- Explanation: You must specify the type of an action or condition -- either an invoke, Java code, or a visual snippet. Only one type is allowed.
- User Action: Use the state machine editor to specify the type of the action or condition or to remove a type if more than one is defined.
- CWLDE0017W: The state machine might not be able to exit this state.
- Explanation: The only way to exit this state is by following transitions that have both timeouts and conditions. As a result, the state machine might enter this state but might never exit it.
- User Action: If it is possible that all of the conditions might evaluate to false, add another type of transition.
- CWLDE0018E: The referenced interface cannot be found.
- Explanation: The state machine refers to a WSDLPortType type interface using an XML QName. This QName cannot be resolved to an existing interface.
- User Action: Either change the reference to point to an existing interface, or create a new interface having the given target namespace and name.
- CWLDE0020W: The composite state does not contain a final state.
- Explanation: A final state is used with a default transition. A default transition is taken when a composite state enters a final state.
- User Action: Consider adding a final state especially if you expect to define a default transition for the state machine.
- CWLDE0021E: The composite state does not contain a final state.
- Explanation: The composite state has a default transition that is used only when the composite state enters a final state. Therefore, at least one final state is required when a default transition is defined.
- User Action: Use the state machine editor to either add at least one final state to the composite state or remove the default transition from the composite state.
- CWLDE0022E: The composite state machine is missing a composite state.
- Explanation: The composite state of the composite state machine file is incorrect.
- User Action: In the state machine editor, open the state machine and delete the composite state machine that is missing a composite state.
- CWLDE0023E: The {0} internal composite state machine does not have an associated state.
- Explanation: This error does not occur if you use only the state machine editor to edit the state machine.
- User Action: If the state machine editor cannot open this file, open the file with another editor and delete the section that defines the composite state machine with the given name.
- CWLDE0024E: The state name {0} is being used.
- Explanation: Every state must have a unique name.
- User Action: Specify another name for the state.
- CWLDE0025E: The getState operation cannot be used on a transition.
- Explanation: The getState operation is used to get the last committed state of the state machine. It cannot be used to transition from one state to another.
- User Action: Select another operation.
- CWLDE0027E: The timer has too many initial values.
- Explanation: A timer must be specified as either a value or Java code but not both.
- User Action: Remove either the value or the Java code.
- CWLDE0028E: Final states cannot have outgoing transitions.
- Explanation: A state machine ends as soon as it reaches a final state. No further transitions are allowed.
- User Action: Remove all outgoing transitions from the final states.
- CWLDE0029E: The terminate state has an outgoing transition.
- Explanation: A state machine ends as soon as it reaches a terminate state. Therefore, a terminate state cannot have an outgoing transition.
- User Action: Remove all outgoing transitions from the terminate states.
- CWLDE0030E: Transitions that flow from one state to another must not be internal.
- Explanation: Only looping transitions can be internal.
- User Action: Remove the internal setting from this transition.
- CWLDE0031E: The default transition is invalid.
- Explanation: Default transitions cannot loop back to the same composite state that is being exited.
- User Action: Use the state machine editor to select another target state for this transition.
- CWLDE0032E: The reference defines more than one interface.
- Explanation: Each reference must define only one interface because state machines do not support more than one interface on a reference.
- User Action: Use the state machine editor to delete all except one of the interfaces.
- CWLDE0033E: The initial state has too many outgoing transitions.
- Explanation: An initial state may have only one outgoing transition.
- User Action: Use the state machine editor to delete all but one of the transitions.
- CWLDE0034W: The state machine does not have a final state.
- Explanation: Unless a state machine loops forever, it usually contains a final state. Another option is to use a terminate state, which causes a state machine to end more abruptly. An abrupt end might suggest that the state machine ended with an error.
- User Action: If you do not intend the state machine to loop forever, add a final or terminate state.
- CWLDE0035E: It is not possible to enter this state.
- Explanation: All of the incoming transitions to this state are self-transitions, which means their source and target states are the same. Every state other than an initial state must have at least one incoming transition that is not a self-transition.
- User Action: Connect the state with the rest of the state machine by adding at least one incoming transition to it.
- CWLDE0036E: This composite state machine name {0} is already being used.
- Explanation: Each composite state machine must have a unique name.
- User Action: Specify another name for the composite state machine.
- CWLDE0037E: The property name {0} is already defined.
- Explanation: Each property must have a unique name.
- User Action: Use the state machine editor to specify another property name.
- CWLDE0038W: The display name of the state is not unique.
- Explanation: Each state has two names: an internal state name and a display name that the state machine editor displays. The internal state name must be unique, and the display name should be unique to avoid confusion.
- User Action: Use the state machine editor to change the display name to a unique name.
- CWLDE0039E: There are no interfaces specified when there should be at least one.
- Explanation: Each state machine must have at least one operation that starts the state machine.
- User Action: Use the state machine editor to add at least one interface to the state machine.
- CWLDE0040E: The operation name is missing.
- Explanation: Each operation must have a name.
- User Action: Select an operation that has a name.
- CWLDE0041E: The name of the interface that contains the operation is missing.
- Explanation: Each operation must indicate the interface that contains it.
- User Action: Use the state machine editor to select an interface that contains this operation.
- CWLDE0042E: This interface type is not supported.
- Explanation: State machines support only interfaces of the type WSDLPortType.
- User Action: Use the state machine editor to remove this interface and select an interface of the type WSDLPortType.
- CWLDE0043E: An interface has been selected more than once.
- Explanation: An interface must be selected only once.
- User Action: Use the state machine editor to remove all but one of the interfaces.
- CWLDE0044E: The interface that is specified is not listed in set of interfaces for this state machine.
- Explanation: All interfaces used in a state machine must be defined to the state machine.
- User Action: Use the state machine editor to define the interface to the state machine.
- CWLDE0045E: The {0} operation is defined in more than one interface.
- Explanation: For state machines, an operation cannot be in more than one interface.
- User Action: Use the interface editor to remove extra occurrences of the operation, or use the state machine editor to remove unnecessary interfaces.
- CWLDE0046E: The {0} operation is not defined for the specified interface.
- Explanation: The specified interface must define the operation.
- User Action: Use the state machine editor to select a different operation or interface, or use the interface editor to add the operation to the interface.
- CWLDE0047E: The interfaces element must be specified, and at least one interface must be defined.
- Explanation: Every state machine must have at least one interface.
- User Action: Use the state machine editor to add an interface to the state machine.
- CWLDE0048E: The correlationSet element must be specified, and at least one correlation property must be defined.
- Explanation: Every state machine must define at least one correlation property. The values of correlation properties distinguish one state machine instance from another.
- User Action: Use the state machine editor to add one or more correlation properties to the state machine.
- CWLDE0049E: The state machine definition file does not define a state machine.
- Explanation: This error occurs when the state machine file is edited in the text editor.
- User Action: Use the state machine editor to add states and transitions to the state machine.
- CWLDE0050E: The initial state is missing.
- Explanation: An initial state is required in the main state machine and in every composite state. Most likely, the state machine file has been edited with an editor other than the state machine editor.
- User Action: Use a text editor to reinsert the definition of the initial state, or delete the state machine and re-create it using the state machine editor.
- CWLDE0051E: The main state machine and every composite state must have at least two states.
- Explanation: The main state machine and every composite state must have an initial state and at least one other state that the initial state transitions to.
- User Action: Use the state machine editor to add and configure at least the minimum number of states and the transitions that connect them.
- CWLDE0052E: The main state machine and every composite state must have at least one transition.
- Explanation: The main state machine and every composite state must have an initial state and at least one other state that the initial state transitions to.
- User Action: Use the state machine editor to add and configure at least the minimum number of states and the transitions that connect them.
- CWLDE0053E: The target namespace for the state machine is missing.
- Explanation: A state machine is identified by its name and its target namespace. Therefore, these attributes are required.
- User Action: Use the state machine editor to give the state machine a target namespace.
- CWLDE0054E: The name of the composite state machine is missing.
- Explanation: The name of the composite state machine is required. This error usually occurs when the state machine file has been edited with a text editor.
- User Action: Use the state machine editor to remove the composite state and then reinsert it. If the state machine editor cannot open the file, use a text editor to replace the name attribute.
- CWLDE0055E: The name of the correlation set is missing.
- Explanation: The correlation set name is required. This type of error usually occurs only when you use a text editor to edit the state machine file. If you edit a state machine file using another editor instead of the state machine editor, the state machine editor might not be able to open it.
- User Action: Use a text editor to reinsert the correlation set name.
- CWLDE0056E: The name of the state machine definition is missing.
- Explanation: The state machine definition name is required. This type of error usually occurs only when you use a text editor to edit the state machine file. If you edit a state machine file using another editor instead of the state machine editor, the state machine editor might not be able to open it.
- User Action: Use a text editor to reinsert the name attribute for the state machine definition.
- CWLDE0057E: The {0} correlation set property is defined more than once.
- Explanation: Duplicate correlation set properties are not allowed.
- User Action: Use the state machine editor to remove all duplicate correlation set properties.
- CWLDE0058E: The {0} property that the correlation set refers to does not exist.
- Explanation: Do not use a text editor to edit a state machine definition. If you use a text editor, the state machine editor might not be able to recover from certain errors.
- User Action: Use a text editor to remove the correlation set element and all of the property elements from the state machine file. Then use the state machine editor to add the correlation set properties back into the state machine file.
- CWLDE0059E: The {0} property is not defined in the correlation set.
- Explanation: The internal structure of the state machine file is incorrect. This error occurs when the state machine file is edited directly.
- User Action: Use the state machine editor to remove the specified property, and then re-create the property in the state machine editor.
- CWLDE0060E: The correlation set does not have any properties defined for it.
- Explanation: The internal structure of the state machine file is incorrect. This error occurs when the state machine file is edited directly.
- User Action: Use a text editor to remove the correlation set element and all of the property elements. Then use the state machine editor to add the correlation set properties back to the state machine file.
- CWLDE0061E: The name of the correlation set property is missing.
- Explanation: The internal structure of the state machine file is incorrect. This error occurs when the state machine file is edited directly.
- User Action: Use a text editor to remove the correlation set element and all of the property elements. Then use the state machine editor to add the correlation set properties back to the state machine file.
- CWLDE0062E: The type for the {0} correlation set property is missing.
- Explanation: All correlation set properties must specify a simple XSD type.
- User Action: Use the state machine editor to select a type for the property.
- CWLDE0063E: The type specified on the {0} correlation set property does not exist.
- Explanation: The correlation set property refers to a type that cannot be found.
- User Action: Make sure that the specified type definition is available to the state machine file or select a different type.
- CWLDE0064E: The import element does not include the packages attribute.
- Explanation: The Java import makes Java packages and classes available to Java code; therefore, the import must define at least one Java package.
- User Action: In the properties view of the state machine editor, use the Java import tab to specify the Java packages to be included.
- CWLDE0065E: The transition must not flow to an initial state.
- Explanation: Because initial states are entered automatically, they cannot have inbound transitions.
- User Action: Use the state machine editor to remove the transition.
- CWLDE0067E: The getState operation is incorrectly configured.
- Explanation: The getState operation must have one output parameter, it must be named ''state'', and it must be of the type string.
- User Action: Use the interface editor to configure the output or operation as necessary.
- CWLDE0068E: The WSDLPortType interface element is missing the reference to an interface.
- Explanation: The reference to an interface WSDLPortType might be lost when the state machine file is edited directly. The required portType attribute of the interface element is missing.
- User Action: Use the state machine editor to add an interface to the interface definition.
- CWLDE0069E: The variable name is missing.
- Explanation: Each variable must have a unique name.
- User Action: In the property view of the state machine editor, specify a name for the variable.
- CWLDE0070E: The variable is configured incorrectly.
- Explanation: Either the type or the element attributes must be specified, but not both.
- User Action: Use a text editor to remove the definition of the specified variable from the state machine definition. Then use the state machine editor to add the variable again.
- CWLDE0071E: The type or element specified for the variable does not exist.
- Explanation: The variable refers to either an XSD type or element that cannot be found.
- User Action: Use the state machine editor to change the variable.
- CWLDE0072E: The source state of the transition is missing.
- Explanation: The internal structure of the state machine file is incorrect. This error occurs when the state machine file is edited directly.
- User Action: Use a text editor to remove the transition element from the state machine file. Then use the state machine editor to re-create the transition.
- CWLDE0073E: The target state of the transition is missing.
- Explanation: The internal structure of the state machine file is incorrect. This error occurs when the state machine file is edited directly.
- User Action: Use a text editor to remove the transition element from the state machine file, and then use the state machine editor to re-create the transition.
- CWLDE0074E: The name of the parameter is missing.
- Explanation: The internal structure of the state machine file is incorrect. This error occurs when the state machine file is edited directly.
- User Action: Use a text editor to remove the parameter element from the state machine file, and then use the state machine editor to re-create the parameter.
- CWLDE0075E: The associated variable for the parameter is missing.
- Explanation: The internal structure of the state machine file is incorrect. This error occurs when the state machine file is edited directly.
- User Action: Use a text editor to remove the parameter element from the state machine file, and then use the state machine editor to re-create the parameter.
- CWLDE0076E: The operation for the invoke element is missing.
- Explanation: The invoke element invokes an operation on a reference. You must specify which operation and reference to invoke.
- User Action: Use the state machine editor to select both a reference and an operation.
- CWLDE0077E: The reference for the invoke element is missing.
- Explanation: The invoke element invokes an operation on a reference. You must specify which operation and reference to invoke.
- User Action: Use the state machine editor to select both a reference and an operation.
- CWLDE0078E: The reference on the invoke element is undefined.
- Explanation: The reference that the invoke element refers to does not exist.
- User Action: Use the state machine editor to select a reference.
- CWLDE0080E: The name of the reference is missing.
- Explanation: Each reference must have a unique name.
- User Action: Use the state machine editor to give the reference a unique name.
- CWLDE0081E: The {0} operation is not defined in the {1} reference.
- Explanation: Each invoke element must identify an operation that is in an interface associated with the named reference.
- User Action: Use the state machine editor to select a different operation for the invoke element, or use the interface editor to add the specified operation to the interface.
- CWLDE0082E: The {0} operation must be used.
- Explanation: With the exceptions of getState and getDisplayState, every operation of every interface that is defined for the state machine must be used for at least one transition.
- User Action: If you do not need the specified operation, use the interface editor to remove it from the interface. Otherwise, use the state machine editor to modify the state machine file so that the operation is used for at least one transition.
- CWLDE0083E: The property alias does not specify a property name.
- Explanation: The property name is required and must refer to an existing correlation property.
- User Action: Use a text editor to remove the property alias. Then use the state machine editor to re-create the property alias.
- CWLDE0084E: The property name refers to a correlation property that does not exist.
- Explanation: The property name must refer to an existing correlation property.
- User Action: Use a text editor to remove the property alias. Then use the state machine editor to re-create the property alias.
- CWLDE0085E: The property alias is not associated with an input message.
- Explanation: A property alias locates the field in a message that represents a particular correlation property.
- User Action: Use a text editor to remove the property alias. Then use the state machine editor to re-create the property alias.
- CWLDE0086E: The message specified on the property alias does not exist.
- Explanation: A property alias locates the field in a message that represents a particular correlation property.
- User Action: Use a text editor to remove the property alias. Then use the state machine editor to re-create the property alias.
- CWLDE0087E: The {0} operation does not have a property alias for the {1} property.
- Explanation: Each operation must have one property alias for each property. A property alias locates the field in a message that represents a particular correlation property.
- User Action: Use the state machine editor to create a property alias for the specified property.
- CWLDE0088W: The {0} property has property aliases that are not used.
- Explanation: Each operation must have only one property alias for each property.
- User Action: Use a text editor to remove the unneeded property alias.
- CWLDE0089I: The {0} operation defines faults that are not used.
- Explanation: State machines support only string faults. If more than one string fault is defined, only the first string fault is used. If no string faults are defined, the operation is treated as though it has no faults.
- User Action: If the specified operation has no string faults, but the operation has faults, add a string fault.
- CWLDE0090E: The {0} operation defines more than one fault.
- Explanation: Operations can have only one fault. If a fault is defined, it must be of type string.
- User Action: Use the interface editor to delete all except one string type fault from the specified operation.
- CWLDE0091E: The fault on the {0} operation is incorrect.
- Explanation: Operations can have only one fault. If a fault is defined, it must be of type string.
- User Action: Use the interface editor to change the type of the fault or to remove it.
- CWLDE0092E: The {0} operation cannot be validated.
- Explanation: An exception has been logged to the workspace log file.
- User Action: To determine the cause of the problem, review the workspace log file. For more information, refer to the Troubleshooting Guide on the WebSphere Process Server Support Site (http://www.ibm.com/software/integration/wps/support/). If you still cannot determine the cause of the problem, save the log file and the workspace so that IBM Support can resolve the problem.
- CWLDE0094E: The expiration value is not a valid date.
- Explanation: The expiration value must be six comma-separated integers in the format year, month (0-11), day, hour, minute, second.
- User Action: Use the state machine editor to correct the expiration value.
- CWLDE0095E: The date and time has passed.
- Explanation: The expiration value must represent a date and time that is in the future.
- User Action: Use the state machine editor to choose a future date and time.
- CWLDE0096E: The {0} correlation set property is not a supported type.
- Explanation: State machines support only atomic, simple types and restrictions of atomic, simple types. Unions and lists of simple types are not supported.
- User Action: Use the state machine editor to select an appropriate type.
- CWLDE0097E: The transition is not allowed.
- Explanation: A transition with the same operation but without a condition already exists. The transition without a condition will always be selected over the one with a condition.
- User Action: Use the state machine editor to remove or change the transition.
- CWLDE0098E: The property alias does not have a part associated with it.
- Explanation: An existing part must be specified because some WSDL styles allow messages to have more than one part.
- User Action: Use a text editor to remove the indicated property alias. Then use the state machine editor to re-create the property alias.
- CWLDE0099E: The part specified in the property alias is not defined in the associated interface.
- Explanation: An existing part must be specified because some WSDL styles allow messages to have more than one part.
- User Action: Use a text editor to remove the indicated property alias. Then use the state machine editor to re-create the property alias.
- CWLDE0100E: The property alias does not correctly refer to the interface.
- Explanation: An unexpected exception occurred while processing the interface and the business objects to which it refers.
- User Action: Use the interface editor and business object editor to ensure that the interfaces and the business objects that they refer to are well formed. Use the state machine editor to remove the property alias and re-create it.
- CWLDE0101E: The {0} type to which the property alias refers is not the same as the {1} type.
- Explanation: The type of the attribute to which the query string refers must match the type of correlation property that the property alias refers to.
- User Action: Use the state machine editor to select a different attribute or to adjust the types so that they match.
- CWLDE0102E: The composite state does not have a default transition.
- Explanation: A composite state that has a final state must also have a default transition. When a final state in a composite state is reached, the default transition out of the composite state is automatically used.
- User Action: Use the state machine editor to create a default transition.
- CWLDE0103E: The {0} XPath in the property alias does not identify a value for the correlation property.
- Explanation: The XPath string specified in the property alias does not identify an existing field in the message that the property alias refers to.
- User Action: Use the state machine editor to edit the property alias so that it identifies a value for the correlation property.
- CWLDE0105E: An exception occurred while validating the invoke element.
- Explanation: While determining which input and output variables are available for the invoke operation to use, an exception occurred. The error might be in the interface or business objects that are used by the operation associated with the transition. The exception is logged in the workspace log file.
- User Action: Review the workspace log file to determine the cause of the problem. For more information, refer to the Troubleshooting guide on the WebSphere Process Server Support Site (http://www.ibm.com/software/integration/wps/support/). If you still cannot determine the cause of the problem, save the log file and the workspace so that IBM Support can resolve the problem.
- CWLDE0106E: The variable that is specified for the parameter is not defined.
- Explanation: State machines use variables to supply the input or accept the output of an invoked operation. There is a parameter for each input and output parameter of the operation. The specified parameter identifies a variable that does not exist.
- User Action: Use the state machine editor to create the variable or to associate the parameter with a different variable.
- CWLDE0107E: The {0} parameter of the {1} type does not match the variable of the {2} type.
- Explanation: The types of parameters and their variables must match.
- User Action: Use the state machine editor to change the variable or to select a different variable, or use the interface editor to change the type of the parameter.
- CWLDE0108E: Variable names that contain the string {0} are reserved and cannot be defined.
- Explanation: Certain variable names, such as the one specified, are reserved for the state machine to use internally.
- User Action: Use the state machine editor to specify a different name.
- CWLDE0109E: Variable names that end with the string {0} are reserved and cannot be defined.
- Explanation: Certain variable names, such as the one specified, are reserved for the state machine to use internally.
- User Action: Use the state machine editor to specify a different name.
- CWLDE0110E: The {0} input parameter for this invoke operation does not match any operation input.
- Explanation: For each input parameter of the invoked operation, there must be an invoke parameter with the same name.
- User Action: Use the state machine editor to correct the mapping of variables to operation input and output parameters.
- CWLDE0111E: An invoke parameter is not defined for the {0} input of the operation.
- Explanation: For each input parameter of the invoked operation, there must be an invoke parameter with the same name.
- User Action: Use the state machine editor to correct the mapping of variables to operation input and output parameters.
- CWLDE0112E: An invoke parameter is not defined for the {0} output of the operation.
- Explanation: For each output parameter of the invoked operation, there must be an invoke parameter with the same name.
- User Action: Use the state machine editor to correct the mapping of variables to operation input and output parameters.
- CWLDE0113E: The {0} output parameter for this invoke does not match an operation output.
- Explanation: For each output parameter of the invoked operation, there must be an invoke parameter with the same name.
- User Action: Use the state machine editor to correct the mapping of variables to operation input and output parameters.
- CWLDE0114E: The {0} parameter is already defined.
- Explanation: Each parameter must have a unique name.
- User Action: Use a text editor to remove the duplicate parameter definitions.
- CWLDE0118W: The operation name {0} is longer than 38 characters.
- Explanation: The debugger places a 38-character limit on operation names.
- User Action: If you plan to use the debugger with this state machine, limit the operation name length to 38 characters.
- CWLDE0119W: The state name {0} is longer than 32 characters.
- Explanation: The debugger places a 32-character limit on state names.
- User Action: If you plan to use the debugger with this state machine, limit the state name length to 32 characters.
- CWLDE0120W: The transition name {0} is longer than 37 characters.
- Explanation: The debugger places a 37-character limit on transition names.
- User Action: If you plan to use the debugger with this state machine, limit the transition name length to 37 characters.
- CWLDE0121E: The state name is missing.
- Explanation: Each state must have a unique name.
- User Action: Use the state machine editor to assign a unique name to the state.
- CWLDE0122E: The transition name is missing.
- Explanation: Every transition must have a unique name. Because the state machine editor automatically assigns names to transitions, this error usually occurs when the state machine file is edited outside of the state machine editor.
- User Action: Either use a text editor to add the name, or use the state machine editor to delete the transition and then re-create it.
- CWLDE0123E: The getDisplayState operation cannot be used on a transition.
- Explanation: The getDisplayState operation retrieves the last committed display state of the state machine. It cannot be used to transition from one state to another.
- User Action: Use the state machine editor to select a different operation.
- CWLDE0124E: The getDisplayState operation is incorrectly configured.
- Explanation: The getDisplayState operation must have one output parameter; the parameter must be named "state", and it must be of the type string.
- User Action: Use the interface editor to modify the output or operation.
- CWLDE0125E: The business state machine contains errors. Code generation has stopped.
- User Action: If validation is disable, enable validation so that you can see what validation errors exist. Correct the causes of the validation errors and rebuild the state machine.
- CWLDE0126E: The display name of the state is missing.
- Explanation: Each state must have a unique display name to distinguish it from other states in the state machine editor.
- User Action: Use the properties view of the state machine editor to assign a unique display name to this state.
- CWLDE0127E: The operation is missing a required correlation element.
- Explanation: When the operation contains a correlations element, the correlations element must contain a correlation element.
- User Action: Use the properties view of the state machine editor to specify whether the initial operation sets the correlation properties on the request message or the reply message.
- CWLDE0128E: The correlation element in the operation does not refer to an existing correlation set.
- Explanation: The operation must contain a child correlation element with a set attribute that refers to an existing correlation set by name. This error usually occurs when the state machine file is edited outside of the state machine editor.
- User Action: Use the properties view of the state machine editor to toggle the setting that indicates whether the initial operation sets the correlation properties on the request message or the reply message.
- CWLDE0129E: The value of the initiate attribute is incorrect.
- Explanation: The value of the initiate attribute must either "response" or "request".
- User Action: Use the properties view of the state machine editor to toggle the setting that indicates whether the initial operation sets the correlation properties on the request message or the reply message.
- CWLDE0130E: The operation cannot be used in this context.
- Explanation: If the state machine is initiated with an uncorrelated message, the initializing operation can be used only on the initial transition.
- User Action: Use the state machine editor to select a different operation for this transition.
- CWLDE0131E: Only the initial operation can include correlation information.
- Explanation: The state machine can set correlation elements on the initial request message or on the reply to the initial request message. No other operation may set the correlation.
- User Action: Use a text editor to remove this correlation information.
- CWLDE0132E: The property alias already exists.
- Explanation: The property alias that associates the given property with the specified message is a duplicate.
- User Action: Use a text editor to remove the extra property alias.
- CWLDE0133E: The {0} property must be mapped to the input message for the {1} operation.
- Explanation: The property alias is mapped to an output message. The initial operation is configured to set the correlation using the input message.
- User Action: Use the state machine editor to reset the property alias for the property.
- CWLDE0134E: The {0} property must have a property alias for both the input and the output messages that are associated with the {1} operation.
- Explanation: If the state machine uses only one operation and the correlation is initialized with the output message, then two property aliases are required.
- User Action: Use the state machine editor to create a property alias for both the input and the output messages for the specified operation.
- CWLDE0135E: The transition name undef is a reserved name.
- Explanation: The state machine editor automatically names transitions.
- User Action: Use a text editor to rename the transition, or use the state machine editor to delete and re-create the transition.
- CWLDE0136E: The {0} property alias must be mapped to the output message for the {1} operation.
- Explanation: The property alias is mapped to an input message. However, the initial operation is configured to set the correlation using the output message.
- User Action: Use the state machine editor to reset the property alias for the property.
- CWLDE0137E: The {0} variable is already used for the {1} parameter.
- Explanation: A variable may be used to initialize only one input parameter per invocation.
- User Action: Use the state machine editor to select a different variable.
- CWLDE0138E: The message is not used by any operation.
- Explanation: The property alias refers to a message that is not used by any operation.
- User Action: Use the interface editor to define an operation that uses the message or use the state machine editor to remove the property alias.
- CWLDE0139E: The auto deletion value {0} is incorrect.
- Explanation: The auto deletion attribute controls whether a state machine is deleted when it completes either successfully or after an error.
- User Action: Use the state machine editor to select a valid value -- yes, no, or onSuccessfulCompletion.
- CWLDE0140E: The template name {0} is incorrect.
- Explanation: The template name must refer to a valid process template name and cannot be equal to the empty string.
- User Action: Use the state machine editor to enter a valid template name.
- CWLDE3000E: The {0} business state machine cannot be built.
- Explanation: A system component detected a problem and raised an exception condition.
- User Action: Save a copy of the workspace log file and a copy of your workspace and then contact IBM Software Support. The workspace log file contains an exception stack dump which can help IBM Support determine the cause of the error.
- CWLDE3001E: An error occurred during the invocation of the guard on the transition {0} in the state machine {1}.
- Explanation: The user-defined guard condition caused the exception. Another transition will be selected if it is available. If another transition is not available, the state machine will remain in the state {2} until another event occurs.
- User Action: The guard condition might contain an error. Use the debugger to determine why the guard condition is functioning incorrectly.
- CWLDE3002E: An error occurred during the invocation of a transition action on the transition {0} in the state machine {1}.
- Explanation: The user-defined transition action caused the exception. The current transition will be aborted. The state machine will remain in the state.
- User Action: The transition action might contain an error. Use the debugger to determine why the transition action is functioning incorrectly.
- CWLDE3003E: An error occurred during the invocation of a transition action on the transition {0} in the state machine {1}.
- Explanation: The user-defined transition action caused the exception. The current transition will continue executing.
- User Action: The transition action might contain an error. Use the debugger to determine why the transition action is functioning incorrectly.
- CWLDE3004E: An error occurred during the invocation of an entry action on the state {0} in the state machine {1}.
- Explanation: The user-defined entry action caused the exception.
- User Action: The entry action may contain an error. Use the debugger to determine why the entry action is functioning incorrectly.
- CWLDE3005E: An error occurred during the invocation of an exit action on the state {0} in the state machine {1}.
- Explanation: The user-defined exit action caused the exception.
- User Action: The exit action may contain an error. Use the debugger to determine why the exit action is functioning incorrectly.
- CWLDE5100E: The preferredInteractionStyle property for the {1} interface in the {0} state machine component file is set incorrectly.
- Explanation: State machines support only the asynchronous interaction style. The value of this attribute in the component file must be ''async''.
- User Action: In the Properties view of the assembly editor, change the setting for the preferredInteractionStyle property to ''async''.
- CWLDE5101E: The {0} state machine component file contains at least one interface of the wrong type.
- Explanation: State machines support WSDLPortType interfaces only.
- User Action: In the Properties view of the assembly editor, remove or change all interfaces that are not of the WSDLPortType type.
- CWLDE5102E: The {0} state machine component file contains an unused interface: {1}.
- Explanation: The state machine must also use each interface that is defined in the component file.
- User Action: In the Properties view of the assembly editor, remove the unused interfaces or change the state machine to use these interfaces.
- CWLDE5103E: The {0} state machine component file does not contain an interface that corresponds to the {1} interface in the state machine implementation file.
- Explanation: Each interface that a state machine uses must be exposed in the component file.
- User Action: In the Properties view of the assembly editor, add the missing interfaces or change the state machine to remove any extra interfaces defined there.
- CWLDE5104E: The {1} reference in the {0} state machine component file specifies a multiplicity property that is not valid.
- Explanation: State machines support only references with a multiplicity of 1..1.
- User Action: In the Properties view of the assembly editor, change the multiplicity of the reference to 1..1.
- CWLDE5105E: The {0} state machine component file refers to {1}, which does not have an interface.
- Explanation: State machines require that every reference in the component file contain exactly one interface. In addition, the interface must be of the type WSDLPortType.
- User Action: Use the Properties view of the assembly editor to remove invalid references or to add new references.
- CWLDE5106E: The {0} state machine component file refers to {1}, which has more than one interface.
- Explanation: For state machines, every reference in the component file must contain exactly one interface of the WSDLPortType type.
- User Action: In the Properties view of the assembly editor, change the interface for the reference or remove the reference and add a different one.
- CWLDE5107E: The {0} state machine component file refers to the {1} reference, which has at least one interface of the wrong type.
- Explanation: For state machines, every reference in the component file must contain exactly one interface. In addition, the interface must be of the WSDLPortType type.
- User Action: In the Properties view of the assembly editor, change the interface for the reference or remove the reference and add a different one.
- CWLDE5108E: The {0} state machine component file contains an unused reference: {1}.
- Explanation: The implementing state machine must use each reference that is defined in the component file.
- User Action: In the Properties view of the assembly editor, remove the unused references or change the state machine to use these references.
- CWLDE5109E: The {0} state machine component file does not contain a reference that corresponds to the {1} reference in the state machine implementation file.
- Explanation: Each reference that a state machine uses must be exposed in the component file.
- User Action: In the Properties view of the assembly editor, add the missing references or change the state machine to remove extra references defined there.
- CWLDE5110E: The {0} state machine component file specifies a transaction quality-of-service (QoS) qualifier more than once.
- Explanation: To avoid conflicting values, the transaction QoS qualifier must be specified only once for an interface.
- User Action: In the Properties view of the assembly editor, remove all except one transaction QoS qualifiers.
- CWLDE5111E: The {0} state machine component file specifies an ActivitySession quality-of-service (QoS) qualifier, which is not allowed in this context.
- Explanation: State machines do not support activity sessions. Therefore, the ActivitySession QoS qualifier is not allowed.
- User Action: In the Properties view of the assembly editor, remove the ActivitySession QoS qualifier from the implementation.
- CWLDE5112E: The {0} state machine component file contains an implementation quality-of-service (QoS) qualifier with a value that is not valid.
- Explanation: For state machines, the transaction QoS qualifier must have a value of ''global''.
- User Action: In the Properties view of the assembly editor, define the transaction implementation QoS qualifier with a value of ''global''.
- CWLDE5113E: The {0} state machine component file specifies the JoinActivitySession quality-of-service (QoS) qualifier, which is not allowed in this context.
- Explanation: State machines do not support activity sessions. Therefore, the JoinActivitySession QoS qualifier is not allowed.
- User Action: In the Properties view of the assembly editor, remove the JoinActivitySession QoS qualifiers from all interfaces.
- CWLDE5114E: The {1} interface in the {0} state machine component file specifies the JoinActivitySession quality-of-service (QoS) qualifier, which is not allowed in this context.
- Explanation: State machines do not support activity sessions. Therefore, the JoinActivitySession QoS qualifier is not allowed.
- User Action: In the Properties view of the assembly editor, remove the JoinActivitySession QoS qualifiers from all interfaces.
- CWLDE5115E: The {0} state machine component file contains a JoinTransaction quality-of-service (QoS) qualifier with a value that is not valid.
- Explanation: State machines do not support joining a transaction. Therefore, the JoinTransaction QoS qualifier must be specified with a value of ''false''.
- User Action: In the Properties view of the assembly editor, define that the JoinTransaction QoS qualifier for all operations or interfaces with a value of ''false''. You may also specify this QoS qualifier globally for all interfaces and operations.
- CWLDE5116E: The {1} interface in the state machine component file ''{0}'' contains a JoinTransaction quality-of-service (QoS) qualifier with a value that is not valid.
- Explanation: State machines do not support joining a transaction. Therefore, the JoinTransaction QoS qualifier must be specified with a value of ''false''.
- User Action: In the Properties view of the assembly editor, define the JoinTransaction QoS qualifier for all operations or interfaces with a value of ''false''. You may also specify this QoS qualifier globally for all interfaces and operations.
- CWLDE5117E: The {0} state machine component file specifies the JoinTransaction quality-of-service (QoS) qualifier globally more than once.
- Explanation: To avoid conflicting values, state machines require that the JoinTransaction QoS qualifier be specified globally no more than once.
- User Action: In the Properties view of the assembly editor, remove all JoinTransaction QoS qualifiers at the global level except one.
- CWLDE5118E: The {1} interface of the {0} state machine component file specifies the JoinTransaction quality-of-service (QoS) qualifier more than once.
- Explanation: To avoid conflicting values, state machines require that the JoinTransaction QoS qualifier be specified no more than once for an interface.
- User Action: In the Properties view of the assembly editor, remove all JoinTransaction QoS qualifiers except one.
- CWLDE5119E: The {1} interface in the {0} state machine component file is missing a JoinTransaction quality-of-service (QoS) qualifier.
- Explanation: State machines do not support joining a transaction. Therefore, the JoinTransaction QoS qualifier must be specified with a value of ''false''.
- User Action: In the Properties view of the assembly editor, define the JoinTransaction QoS qualifier for all operations or interfaces with a value of ''false''. You may also specify this QoS qualifier globally for all interfaces and operations.
- CWLDE5120E: The {2} operation of the {1} interface in the {0} state machine component file specifies the JoinActivitySession quality-of-service (QoS) qualifier, which is not allowed in this context.
- Explanation: State machines do not support activity sessions. Therefore, the JoinActivitySession QoS qualifier is not allowed.
- User Action: In the Properties view of the assembly editor, remove the JoinActivitySession QoS qualifiers from all operations.
- CWLDE5121E: The {2} operation of the {1} interface in the {0} state machine component file is missing the JoinTransaction quality-of-service (QoS) qualifier.
- Explanation: State machines do not support joining a transaction. Therefore, the JoinTransaction QoS qualifier must be specified and must have a value of ''false''.
- User Action: In the Properties view of the assembly editor, define the JoinTransaction QoS qualifier for all operations or interfaces with a value of ''false''. You may also specify this QoS qualifier globally for all interfaces and operations.
- CWLDE5122E: The {2} operation of the {1} interface in the {0} state machine component file contains a JoinTransaction quality-of-service (QoS) qualifier with an value that is not valid.
- Explanation: State machines do not support joining a transaction. Therefore, the JoinTransaction QoS qualifier must be specified with a value of ''false''.
- User Action: In the Properties view of the assembly editor, define that the JoinTransaction QoS qualifier for all operations or interfaces a value of ''false''. You may also specifiy this QoS qualifier globally for all interfaces and operations.
- CWLDE5123E: The {0} state machine component file specifies a SuspendActivitySession quality-of-service (QoS) qualifier, which is not allowed in this context.
- Explanation: State machines do not support activity sessions. Therefore, the SuspendActivitySession QoS qualifier is not allowed.
- User Action: In the Properties view of the assembly editor, remove the SuspendActivitySession QoS qualifiers from all of the references.
- CWLDE5124E: The {1} reference in the {0} state machine component file specifies a SuspendActivitySessio quality-of-service (QoS) qualifier, which is not allowed in this context.
- Explanation: State machines do not support activity sessions. Therefore, the SuspendActivitySession QoS qualifier is not allowed.
- User Action: In the Properties view of the assembly editor, remove the SuspendActivitySession QoS qualifiers from all of the references.
- CWLDE5125E: The {0} state machine component file refers to a quality-of-service (QoS) qualifier for asynchronous invocations at the global level that has a value other than ''commit''.
- Explanation: State machines require a value of ''commit'' to indicate that the invocation should occur after the current transaction commits.
- User Action: In the Properties view of the assembly editor, change the value of this QoS qualifier to ''commit''.
- CWLDE5126E: The {1} reference in the {0} state machine component file refers to a quality-of-service (QoS) qualifier with value that is not valid.
- Explanation: State machines support only a value of ''commit'' for asynchronous invocations to indicate that one-way, asynchronous invocations should occur after the current transaction commits.
- User Action: In the Properties view of the assembly editor, change the value of the asynchronous invocation QoS qualifier to ''commit''.
- CWLDE5127E: The reference quality-of-service (QoS) qualifier for asynchronous invocations is specified more than once at the global level for all references in the {0} state machine component file.
- Explanation: To prevent conflicting values from being specified, the reference QoS qualifier may not be specified more than once at the global level.
- User Action: In the Properties view of the assembly editor, remove the extra reference QoS qualifiers from the asynchronous invocations.
- CWLDE5128E: The reference quality-of-service (QoS) qualifier for asynchronous invocations is specified more than once for the {1} reference in the {0} state machine component file.
- Explanation: To prevent conflicting values from being specified, the reference QoS qualifier may not be specified more than once for a particular reference.
- User Action: In the Properties view of the assembly editor, remove the extra reference QoS qualifiers from the asynchronous invocations. You may specify the reference QoS qualifier globally for all asynchronous invocations.
- CWLDE5129E: The {1} reference in the {0} state machine component file does not specify an asynchronous invocation quality-of-service (QoS) for asynchronous invocations.
- Explanation: An asynchronous invocation QoS qualifier identifies when asynchronous, one-way operations should be delivered to the target. State machines require that the asynchronous invocation QoS qualifier have a value of ''commit'' to indicate that the invocation should occur after the current transaction commits.
- User Action: In the Properties view of the assembly editor, add the asynchronous invocation QoS qualifier to the reference. You may specify the asynchronous invocation QoS qualifier globally for all references.
- CWLDE5130E: The {0} component file must correctly identify a state machine implementation.
- Explanation: The ''sacl'' attribute that is in the component file either does not exist or it does not have a value.
- User Action: In the assembly editor, regenerate the implementation or select a new implementation. If you no longer need this component file, delete it.
- CWLDE5131E: The {1} state machine implementation file does not exist for the component defined in {0}.
- Explanation: The ''sacl'' attribute that is in the component file refers to a state machine implementation file that does not exist.
- User Action: In the assembly editor, regenerate the implementation or select a new implementation. If you no longer need the component file, delete it.
- CWLDE5132E: The {2} operation of the {1} interface of the {0} state machine component file specifies a JoinTransaction quality-of-service (QoS) qualifier more than once.
- Explanation: The JoinTransaction QoS qualifier may be specified only once.
- User Action: Use the assembly editor to remove the extra occurrences of the JoinTransaction operation QoS qualifier.
- CWLDE5133E: The {1} reference in the {0} state machine component file has a matching reference in the state machine implementation file that has the wrong number of interfaces.
- Explanation: Corresponding references in the component definition and the state machine definition must have the same number and type of interfaces.
- User Action: Use the assembly editor or the state machine editor to ensure that corresponding references in the component and implementation files have the same number and type of interfaces.
- CWLDE5134E: The {1} reference in the {0} state machine component file has a matching reference in the state machine implementation file, but the interfaces are not equivalent.
- Explanation: Corresponding references in the component definition and the state machine definition must have the same number and type of interfaces.
- User Action: Use the assembly editor or the state machine editor, to ensure that corresponding references in the component and implementation files have the same number and type of interfaces.
- CWLDE5135E: An exception occurred while attempting to load the {0} resource.
- Explanation: The state machine validator detected an unexpected exception.
- User Action: The workspace log file should contain an exception stack dump. Save a copy of the log file and a copy of your workspace. This information will assist IBM support in determining the cause of the problem.
- CWLDE5136W: The wire on the {1} reference is ignored in the {0} state machine component file.
- Explanation: The corresponding reference in the sacl file has a process template specified. The process template takes precedence.
- User Action: Use the assembly editor to remove the wire between the state machine and the corresponding component.