- CWWBW0001I: Validated process model ''{0}'' successfully: {1} warnings, {2} information.
- Explanation: The validated process model does not contain any validation errors. The installation of the application can be continued.
- User Action: Check any warnings or informational messages. These messages provide more information and any actions that you need to take.
- CWWBW0002E: Validated process model ''{0}'' with findings: {1} errors, {2} warnings, {3} information.
- Explanation: The validated process model contains one or more validation errors. The installation of the application cannot be continued.
- User Action: Correct all of the reported errors and re-install the application. The messages provide more information about the error and any actions that you need to take. If theapplication was created with the corresponding tool, ensure that the release levels of the tool andof the run time are compatible. If the application is installed in an ND environment, ensurethat all of the servers are at the same release level.
- CWWBW0003E: Validated process model ''{0}'' with findings: {1} errors, {2} warnings, {3} information: {4}
- Explanation: The validated process model contains one or more validation errors. The installation of the application cannot be continued.
- User Action: Correct all of the reported errors and re-install the application. The messages provide more information about the error and any actions that you need to take. If theapplication was created with the corresponding tool, ensure that the release levels of the tool andof the run time are compatible. If the application is installed in an ND environment, ensurethat all of the servers are at the same release level.
- CWWBW0004E: A syntactical error was found (row: {0}, column: {1}): {2}
- Explanation: The BPEL file does not validate against the schema.
- User Action: Ensure that the BPEL file is syntactically correct.
- CWWBW0005W: A syntactical warning was found (row: {0}, column: {1}): {2}
- Explanation: The BPEL file validates with warnings against the schema.
- User Action: Ensure that the BPEL file is syntactically correct.
- CWWBW0006E: The BPEL resource cannot be loaded.
- Explanation: The semantical validation of the BPEL resource was canceled because of the BPEL resource is not valid or an internal problem occurred.
- User Action: Correct all of the reported syntactical errors. If fatal errors exist, for example, when the resource is not well-formed, theresource cannot be loaded. If no other errors are reported, contact IBM Software Support.
- CWWBW0007E: The file could not be read. Detail message: ''{0}''.
- Explanation: The BPEL file could not be found or another error occurred when the file was read.
- User Action: Check the detail message.
- CWWBW0050E: BPEL validation error: {0}.
- Explanation: General purpose message used when the product is in service and a new message is needed.
- User Action: Check the error message for a description of the error.
- CWWBW0051W: BPEL validation warning: {0}.
- Explanation: General purpose message used when the product is in service and a new message is needed.
- User Action: Check the warning message for a description of the warning.
- CWWBW0052I: BPEL validation information: {0}.
- Explanation: General purpose message used when the product is in service and a new message is needed.
- User Action: None.
- CWWBW0101E: The process element must contain an activity.
- Explanation: An empty process element cannot be executed.
- User Action: Add an activity to the process element. The activity can be a structured activity, such as a parallel activities activity, or a sequence activity. The structured activities cancontain basic and structured activities, for example, receive activities, replyactivities, assign activities, and scope activities.
- CWWBW0102E: The catch element must contain an activity (process fault handler, catch element {0}).
- Explanation: An empty catch element cannot be executed.
- User Action: Add an activity to the catch element or remove the element.
- CWWBW0103E: The catch all element must contain an activity (process fault handler).
- Explanation: An empty catch all element cannot be executed.
- User Action: Add an activity to the catch all element or remove the element.
- CWWBW0104E: The onEvent event must contain an activity (process event handler, onEvent event {0}).
- Explanation: An empty onEvent event cannot be executed.
- User Action: Add an activity to the onEvent event or remove the event.
- CWWBW0105E: The timeout event must contain an activity (process event handler, timeout event {0}).
- Explanation: An empty timeout event cannot be executed.
- User Action: Add an activity to the timeout event or remove the event.
- CWWBW0106E: The partnerLinkType must be set (process partner ''{0}'').
- Explanation: The partnerLinkType defines up to two roles that a process can have when it interacts with other services.
- User Action: Set the partnerLinkType.
- CWWBW0107E: The partner attribute must be set (process event handler, onEvent event {0}).
- Explanation: For an onEvent event, the partner attribute must be set.
- User Action: Set the partner attribute.
- CWWBW0108E: The operation attribute must be set (process event handler, onEvent event {0}).
- Explanation: The operation attribute must be set for an onEvent event.
- User Action: Set the operation attribute.
- CWWBW0109E: The parameter variable must be set (process event handler, input/output element of onEvent event {0}, parameter {1}, parameter name ''{2}'').
- Explanation: The parameter variable must be set.
- User Action: Set the parameter variable.
- CWWBW0110E: The correlation set must refer to at least one property (correlation set ''{0}'').
- Explanation: None.
- User Action: In the correlation set, refer to an existing property or create a new one.
- CWWBW0111E: The name attribute must be set (process adminTask or activityAdminTask element).
- Explanation: The name attribute must be set for all of the adminTask elements.
- User Action: Set the name attribute.
- CWWBW0112E: The name attribute must be set (process event handler, onEvent event {0}, task element).
- Explanation: The name attribute must be set for all of the task elements.
- User Action: Set the name attribute.
- CWWBW0113E: The duration attribute of the timeout element must be set (process timeout event {0}).
- Explanation: None.
- User Action: Set the duration attribute of the timeout element.
- CWWBW0200E: The catch element must contain an activity (fault handler of activity ''{0}'', catch element {1}).
- Explanation: An empty catch element cannot be executed.
- User Action: Add an activity to the catch element or remove the element.
- CWWBW0201E: The catch all element must contain an activity (fault handler of activity ''{0}'').
- Explanation: An empty catch all element cannot be executed.
- User Action: Add an activity to the catch all element or remove the element.
- CWWBW0202E: The compensation handler must contain an activity (compensation handler of activity ''{0}'').
- Explanation: An empty compensation handler cannot be executed.
- User Action: Remove the compensation handler or add an activity to it.
- CWWBW0203E: The partner attribute must be set (activity ''{0}'').
- Explanation: For invoke, receive, and reply activities, the partner attribute must be set.
- User Action: Set the partner attribute.
- CWWBW0204E: The operation must be set (activity ''{0}'').
- Explanation: For invoke, receive, and reply activities, the operation attribute must be set.
- User Action: Set the operation attribute.
- CWWBW0205E: The duration attribute of the timeout element must be set (activity ''{0}'').
- Explanation: None.
- User Action: Set the duration attribute of the timeout element.
- CWWBW0206E: The parameter variable must be set (input/output element of activity ''{0}'', parameter {1}, parameter name ''{2}'').
- Explanation: None.
- User Action: Set the parameter variable.
- CWWBW0207E: The name attribute must be set (activity ''{0}'', adminTask element).
- Explanation: The name attribute must be set for all of the adminTask elements.
- User Action: Set the name attribute.
- CWWBW0208E: The name attribute must be set (activity ''{0}'', task element).
- Explanation: The name attribute must be set for all of the task elements.
- User Action: Set the name attribute.
- CWWBW0300E: The assign activity must contain a copy element (assign activity ''{0}'').
- Explanation: The assign activity must contain one or more copy elements. These elements specify the data that is to be copied, its location, and the destination of the copied data.
- User Action: Add a copy element.
- CWWBW0301E: The copy element must contain a from-element (assign activity ''{0}'', copy element {1}).
- Explanation: The copy element must contain one from-element and one to-element. These elements specify the data that is to be copied, its location, and the destination of the copied data.
- User Action: Add a from-element.
- CWWBW0302E: The copy element must contain a to-element (assign activity ''{0}'', copy element {1}).
- Explanation: The copy element must contain one from-element and one to-element. These elements specify the data that is to be copied, its location, and the destination of the copied data.
- User Action: Add a to-element.
- CWWBW0303E: The reference-scheme attribute must be set (assign activity ''{0}'', copy element {1}, from-spec, serviceRef element).
- Explanation: None.
- User Action: Set the reference-scheme attribute.
- CWWBW0304E: The serviceRef element cannot be empty (assign activity ''{0}'', copy element {1}, from-spec, serviceRef element).
- Explanation: The serviceRef element must contain an element.
- User Action: Set any of the allowed elements.
- CWWBW0600E: The parallel activities activity must contain an activity (parallel activities activity ''{0}'').
- Explanation: An empty parallel activities activity cannot be executed.
- User Action: Remove the parallel activities activity, or add an activity to it.
- CWWBW0700E: The partner attribute of the undo action must be set (invoke activity ''{0}'').
- Explanation: For an undo action in an invoke activity, the partner attribute must be set.
- User Action: Set the partner attribute.
- CWWBW0701E: The operation attribute of the undo action must be set (invoke activity ''{0}'').
- Explanation: For an undo action in an invoke activity, the operation attribute must be set.
- User Action: Set the operation attribute.
- CWWBW0702E: The parameter variable of the undo action must be set (input/output element of invoke activity ''{0}'', parameter {1}, parameter name ''{2}'').
- Explanation: None.
- User Action: Set the parameter variable of the undo action.
- CWWBW0800E: The receive choice activity must contain an receive element (receive choice activity ''{0}'').
- Explanation: An empty receive choice activity cannot be executed.
- User Action: Add an receive element to the receive choice activity or remove the activity.
- CWWBW0801E: The receive element must contain an activity (receive choice activity ''{0}'', receive element {1}).
- Explanation: An empty receive element cannot be executed.
- User Action: Add an activity to the receive element or remove the element.
- CWWBW0802E: The timeout event must contain an activity (receive choice activity ''{0}'', timeout event {1}).
- Explanation: An empty timeout event cannot be executed.
- User Action: Add an activity to the timeout event or remove the event.
- CWWBW0803E: The partner attribute must be set (receive choice activity ''{0}'', receive element {1}).
- Explanation: For an receive element, the partner attribute must be set.
- User Action: Set the partner attribute.
- CWWBW0804E: The operation attribute must be set (receive choice activity ''{0}'', receive element {1}).
- Explanation: For an receive element, the operation attribute must be set.
- User Action: Set the operation attribute.
- CWWBW0805E: The parameter variable must be set (receive choice activity ''{0}'', input/output element of receive element {1}, parameter {2}, parameter name ''{3}'').
- Explanation: None.
- User Action: Set the parameter variable.
- CWWBW0806E: The name attribute must be set (receive choice activity ''{0}'', receive element {1}, task element).
- Explanation: The name attribute must be set for all of the task elements.
- User Action: Set the name attribute.
- CWWBW0807E: The duration attribute of the timeout element must be set (receive choice activity ''{0}'', timeout event {1}).
- Explanation: None.
- User Action: Set the duration attribute of the timeout element.
- CWWBW1200E: The scope activity must contain an activity (scope activity ''{0}'').
- Explanation: An empty scope activity cannot be executed.
- User Action: Remove the scope activity, or add an activity to it.
- CWWBW1201E: The onEvent event must contain an activity (event handler of scope activity ''{0}'', onEvent event {1}).
- Explanation: An empty onEvent event cannot be executed.
- User Action: Add an activity to the onEvent event, or remove the event.
- CWWBW1202E: The timeout event must contain an activity (event handler of scope activity ''{0}'', timeout event {1}).
- Explanation: An empty timeout event cannot be executed.
- User Action: Add an activity to the timeout event, or remove the event.
- CWWBW1203E: The partner attribute must be set (scope activity ''{0}'', onEvent event {1}).
- Explanation: For an onEvent event, the partner attribute must be set.
- User Action: Set the partner attribute.
- CWWBW1204E: The operation attribute must be set (scope activity ''{0}'', onEvent event {1}).
- Explanation: For an onEvent event, the operation attribute must be set.
- User Action: Set the operation attribute.
- CWWBW1205E: The parameter variable must be set (scope activity ''{0}'', input/output element of onEvent event {1}, parameter {2}, parameter name ''{3}'').
- Explanation: None.
- User Action: Set the parameter variable.
- CWWBW1206E: The name attribute must be set (scope activity ''{0}'', onEvent event {1}, task element).
- Explanation: The name attribute must be set for all of the task elements.
- User Action: Set the name attribute.
- CWWBW1207E: The duration attribute of the timeout element must be set (scope activity ''{0}'', timeout event {1}).
- Explanation: None.
- User Action: Set the duration attribute of the timeout element.
- CWWBW1300E: The sequence activity must contain an activity (sequence activity ''{0}'').
- Explanation: An empty sequence activity cannot be executed.
- User Action: Remove the sequence activity, or add an activity to it.
- CWWBW1400E: The choice activity must contain a case element (choice activity ''{0}'').
- Explanation: An empty choice activity cannot be executed.
- User Action: Add a case element to the choice activity, or remove the activity.
- CWWBW1401E: The case element must specify a condition (choice activity ''{0}'', case element {1}).
- Explanation: The condition defines which case branch is executed. The value of the condition is either true or false when it is executed.
- User Action: Specify the case condition.
- CWWBW1402E: The case element must contain an activity (choice activity ''{0}'', case element {1}).
- Explanation: An empty case element cannot be executed.
- User Action: Add an activity to the case element, or remove the element.
- CWWBW1403E: The otherwise element must contain an activity (choice activity ''{0}'').
- Explanation: An empty otherwise element cannot be executed.
- User Action: Add an activity to the otherwise element, or remove the element.
- CWWBW1500E: The throw activity requires a faultName attribute (throw activity ''{0}'').
- Explanation: The faultName attribute must be set for a throw activity.
- User Action: Set the faultName attribute.
- CWWBW1700E: The while loop activity must specify a condition (while loop activity ''{0}'').
- Explanation: The condition specifies whether the activity is executed again. When the condition is executed, it holds either true or false.
- User Action: Specify a condition for the while loop activity.
- CWWBW1701E: The while loop activity must contain an activity (while loop activity ''{0}'').
- Explanation: An empty while loop activity cannot be executed.
- User Action: Remove the while loop activity, or add an activity to it.
- CWWBW3000E: The schemaLocation attribute is not set. It must be one of ''{0}''.
- Explanation: The schemaLocation attribute must be set in the process element otherwise the syntactical validation cannot be performed.
- User Action: Set the schemaLocation attribute to one of the supported values.
- CWWBW3001E: The value of the schemaLocation attribute is incorrect. It must be set to one of ''{0}'', or a value handled by a custom activity plug-in.
- Explanation: The value of the schemaLocation attribute must be correct, otherwise the syntactical validation cannot be performed.
- User Action: Set the schemaLocation attribute to one of the supported values.
- CWWBW3002E: The partnerLinkType ''{0}'' was not found (process partner ''{1}'').
- Explanation: The partnerLinkType referenced in the process partner is not defined in the WSDL interface.
- User Action: Check that the partnerLinkType is defined correctly in the WSDL interface.
- CWWBW3003E: The myRole role ''{0}'' was not found (process partner ''{1}'', partnerLinkType ''{2}'').
- Explanation: The role referenced in the partner is not defined in the partnerLinkType.
- User Action: Check that the role is defined correctly in the partnerLinkType.
- CWWBW3004E: The portType in the role ''{0}'' is not set (process partner ''{1}'', partnerLinkType ''{2}'').
- Explanation: The portType in the role is needed to access the operations.
- User Action: Ensure that the portType is set.
- CWWBW3005E: The portType ''{0}'' was not found (process partner ''{1}'', partnerLinkType ''{2}'', role ''{3}'').
- Explanation: The portType referenced in the role is not defined in the WSDL interface.
- User Action: Check that the portType is defined correctly in the WSDL interface.
- CWWBW3006E: The partnerRole role ''{0}'' was not found (process partner ''{1}'', partnerLinkType ''{2}'').
- Explanation: The role referenced in the partner is not defined in the partnerLinkType.
- User Action: Check that the role is defined correctly in the partnerLinkType.
- CWWBW3007E: Either the myRole role, the partnerRole role, or both must be defined (process partner ''{0}'').
- Explanation: A partner must have a definition for the myRole role, the partnerRole role, or both.
- User Action: Define the roles for the partner.
- CWWBW3008E: There are too many variable type definitions set for the process variable ''{0}'' (messageType ''{1}'', type ''{2}'', element ''{3}'').
- Explanation: The messageType, type, or element attributes define the type of a variable. Exactly one of these attributes must be set.
- User Action: Ensure that there is only one variable type definition set for the process variable.
- CWWBW3009E: The process variable ''{0}'' must have a variable type definition.
- Explanation: The messageType, type, or element attributes are used to specify the type of a variable. Exactly one of these attributes must be set.
- User Action: Provide a variable type definition for the variable.
- CWWBW3010E: The messageType ''{0}'' was not found (process variable ''{1}'').
- Explanation: The messageType referenced in the process variable must be defined in a WSDL interface.
- User Action: Check that the messageType definition is correctly referenced and that it is defined correctly in an accessible WSDL interface.
- CWWBW3011E: The XSD type definition ''{0}'' was not found (process variable ''{1}'').
- Explanation: The XSD type definition referenced in the process variable must be either a valid built-in XML schema simple type or it must be defined in-line in a WSDLinterface or in an XML schema.
- User Action: Check that the XSD type definition is correctly referenced and that it is defined correctly.
- CWWBW3012E: The XSD element declaration ''{0}'' was not found (process variable ''{1}'').
- Explanation: The XSD element declaration referenced in the process variable must be either defined in-line in a WSDL interface or in an XML schema.
- User Action: Check that the XSD element declaration is correctly referenced and that it is defined correctly.
- CWWBW3013E: The process variable name ''{0}'' is used already.
- Explanation: The name of a variable must be unique within its own scope.
- User Action: Use a different variable name.
- CWWBW3014E: The catch element must have a fault name, a fault variable with a type specification, or both of these attributes set(process fault handler, catch element {0}).
- Explanation: For a catch element, the fault name, the fault variable with a type specification, or both must be set.
- User Action: Remove the catch element or define a fault name, a fault variable with a type specification, or both.
- CWWBW3015E: If the catch element has the fault variable set, it must also have a type specification set (process fault handler, catch element {0},fault variable ''{1}'').
- Explanation: If the fault variable is set on the catch element, the type specification must be set too.
- User Action: Specify a type for the catch element.
- CWWBW3016E: The catch element cannot have the fault message type and the fault type set (process fault handler, catch element {0}, fault message type ''{1}'',faultType ''{2}'').
- Explanation: Either the fault message type or the fault type can be set on the catch element.
- User Action: Either remove the fault message type or the fault type.
- CWWBW3017E: If the catch element has the fault message type set, it must also have a fault variable set (process fault handler, catch element {0},fault message type ''{1}'').
- Explanation: If the fault message type is set on the catch element, the fault variable must be set too.
- User Action: Define the fault variable.
- CWWBW3018E: If the catch element has the fault type set, it must also have a fault variable set (process fault handler, catch element {0},fault type ''{1}'').
- Explanation: If the fault type is set on the catch element, the fault variable must be set too.
- User Action: Specify a fault variable for the catch element.
- CWWBW3019E: The messageType ''{0}'' was not found (process fault handler, catch element {1}, fault variable ''{2}'').
- Explanation: The messageType referenced in the variable is not defined in the WSDL interface.
- User Action: Check that the messageType is defined correctly in the WSDL interface.
- CWWBW3020E: The type ''{0}'' was not found (process fault handler, catch element {1}, fault variable ''{2}'').
- Explanation: The type referenced in the variable is not defined in the WSDL interface.
- User Action: Check that the type is defined correctly in the WSDL interface.
- CWWBW3021E: The process fault handler must contain a catch element or a catch all element.
- Explanation: A fault handler must have at least one catch element or one catch all element.
- User Action: Define a catch element, or a catch all element, or remove the fault handler.
- CWWBW3022E: The fault message type ''{0}'' cannot be used here, because it uses part-level messages (process fault handler, catch element {1},fault variable ''{2}'').
- Explanation: A variable that uses a messageType with one or more parts that reference message types can be used only as an input variable in invoke or transformactivities and in Java snippets.
- User Action: Use a different messageType for the fault variable.
- CWWBW3023E: The display ID ''{0}'' is not unique.
- Explanation: The display ID is an identifier for the activities of a process model. This ID must be unique.
- User Action: Ensure that all of the display IDs are unique.
- CWWBW3024W: The microflow specifies the autonomy attribute. The attribute will be ignored.
- Explanation: For a microflow, the autonomy is derived from the invocation circumstances of the microflow.
- User Action: Remove the autonomy attribute from the process.
- CWWBW3025W: The macroflow specifies the compensationSphere attribute. The attribute will be ignored.
- Explanation: The compensationSphere attribute is meaningless for macroflows, because macroflows do not have an associated compensation sphere.
- User Action: Remove the compensationSphere attribute from the process.
- CWWBW3026E: The process event handler must contain an onEvent event or an timeout event.
- Explanation: An event handler must have at least one onEvent event or one timeout event.
- User Action: Define an onEvent event, or an timeout event, or remove the event handler.
- CWWBW3027E: The partner ''{0}'' was not found (process onEvent event {1}).
- Explanation: The partner referenced in the onEvent event is not defined.
- User Action: Ensure that the partner is correct and that it is defined.
- CWWBW3028E: The partner ''{0}'' does not define the myRole role (process onEvent event {1}).
- Explanation: Partners must define the myRole role if these links are used in onEvent events.
- User Action: Define the myRole role for the partner or use a different partner.
- CWWBW3029E: The portType ''{0}'' was not found (process onEvent event {1}).
- Explanation: The portType referenced in the onEvent event is not defined in the WSDL interface.
- User Action: Ensure that the portType is correct and that it is defined in the WSDL interface.
- CWWBW3030E: The portType referenced in the process onEvent event {0} and in the myRole role ''{1}'' must be the same (partner ''{2}'', partnerLinkType ''{3}'').
- Explanation: The portType attribute in the onEvent event is optional. When this attribute is set, it must be the same as the portType in the myRole role in the partner.
- User Action: Ensure that the port types are the same.
- CWWBW3031E: The operation ''{0}'' was not found (process onEvent event {1}).
- Explanation: The operation referenced in the onEvent event is not defined in the WSDL interface.
- User Action: Ensure that the operation is correct and that it is defined in the WSDL interface.
- CWWBW3032E: The input element is not defined in the operation ''{0}'' (process onEvent event {1}).
- Explanation: The operation referenced in the onEvent event must have an input element.
- User Action: Define an input element, or use a different operation.
- CWWBW3033E: The messageType is not set in the input element of the operation ''{0}'' (process onEvent event {1}).
- Explanation: The input messageType must be set when the operation is used in this onEvent event.
- User Action: Set the input messageType or use a different operation.
- CWWBW3034E: The messageType ''{0}'' referenced in the operation ''{1}'' was not found (process onEvent event {2}).
- Explanation: The messageType referenced must be defined when the operation is used in this onEvent event.
- User Action: Set the messageType, or use a different operation.
- CWWBW3035E: The messageType of variable ''{0}'' and the input element of the operation ''{1}'' must be the same (process onEvent event {2}).
- Explanation: The messageType of the variable and the input element of the operation must be the same.
- User Action: Ensure that both the variable and the input element have the same messageType.
- CWWBW3036E: The variable is not set (process onEvent event {0}).
- Explanation: A mandatory variable for the onEvent event is not defined.
- User Action: Define the mandatory variable.
- CWWBW3037E: The messageType is not set (process onEvent event {0}).
- Explanation: A mandatory messageType for the onEvent event is not defined.
- User Action: Define the mandatory messageType.
- CWWBW3038E: The messageType ''{0}'' was not found (process onEvent event {1}).
- Explanation: The messageType referenced in the onEvent event is not defined in the WSDL interface.
- User Action: Check that the messageType is defined correctly in the WSDL interface.
- CWWBW3039E: The correlation set ''{0}'' was not found (process onEvent event {1}).
- Explanation: The correlation set used in the onEvent event is not defined.
- User Action: Either define the correlation set, or remove it from the onEvent event.
- CWWBW3040E: The process timeout event must specify at least a for expression, an until expression, or a repeatEvery expression (process timeout event {0}).
- Explanation: The for element defines the duration expression after which the event is signaled. The until element specifieswhen the timeout event is fired. If the repeatEvery element is specified, the timeout eventis fired repeatedly once each time the duration period expires. One of these threeexpressions or a repeatEvery expression with a for expression or an until expressionmust occur in an timeout event.
- User Action: Specify a for expression, an until expression, or a repeatEvery expression.
- CWWBW3041E: The process timeout event must specify at least a for expression, an until expression, a timeout expression, or a repeatEvery expression (process timeout event {0}).
- Explanation: The for element defines the duration expression after which the event is signaled. The until element specifieswhen the timeout event is fired. The timeout element specifies a timeout using acalendar supplied by the WebSphere Application Server scheduling service, or user-writtencalendars adhering to those conventions. If the repeatEvery element is specified, the timeout eventis fired repeatedly once each time the duration period expires. One of these fourexpressions or a repeatEvery expression with a for expression, an until expression, or atimeout expression must occur in an timeout event.
- User Action: Specify a for expression, an until expression, a timeout expression, or a repeatEvery expression.
- CWWBW3042E: The process timeout event cannot specify a for expression and a timeout expression or an until expression and a timeout expression (process timeout event {0}).
- Explanation: The for element defines the duration expression after which the event is signaled. The until element specifieswhen the timeout event is fired. The timeout element specifies a timeout using acalendar supplied by the WebSphere Application Server scheduling service, or user-writtencalendars adhering to those conventions. If the repeatEvery element is specified, the timeout eventis fired repeatedly once each time the duration period expires. One of these fourexpressions or a repeatEvery expression with a for expression, an until expressionor a timeout expression must occur in an timeout event.
- User Action: Specify a for expression, an until expression, a timeout expression, or a repeatEvery expression.
- CWWBW3043E: The expression language ''{0}'' is not supported. It must be one of ''{1}'' (process timeout event {2}).
- Explanation: The specified expression language is unknown. Expressions specified in this expression language cannot be executed.
- User Action: Use one of the supported expression languages.
- CWWBW3044E: The process query language ''{0}'' is not supported. It must be one of ''{1}''.
- Explanation: The specified query language is unknown. Queries specified in this query language cannot be executed.
- User Action: Use one of the supported query languages.
- CWWBW3045E: The process expression language ''{0}'' is not supported. It must be one of ''{1}''.
- Explanation: The specified expression language is unknown. Expressions specified in this expression language cannot be executed.
- User Action: Use one of the supported expression languages.
- CWWBW3046E: The property ''{0}'' was not found (process correlation set ''{1}'').
- Explanation: The property used must be defined.
- User Action: Define the property, or remove it from the correlation set.
- CWWBW3047E: The type of the property ''{0}'' is not set (process correlation set ''{1}'').
- Explanation: The type of the property must be set. Only XML schema simple types are allowed.
- User Action: Set the XML schema simple type for the property.
- CWWBW3048E: The type ''{0}'' of the property ''{1}'' was not found or is not an allowed or valid XML schema simple type in this context (process correlation set ''{2}'').
- Explanation: The type used in the property of the correlation set is either not defined, not allowed (for example, it is a complex type, a list type, or a union type), or not valid(for example, a loop in the type definition). Allowed types are all of the XML schemaprimitive simple types and all simple types derived by restriction from a primitive simple type.
- User Action: Select an allowed XML schema simple type.
- CWWBW3049I: The correlation set ''{0}'' is not used.
- Explanation: An unused correlation set was found in the process model.
- User Action: Use the correlation set in an activity, or remove the correlation set from the model.
- CWWBW3050E: The correlation set ''{0}'' is used, but it is never initiated.
- Explanation: A correlation set that is used must be initiated.
- User Action: Initiate the correlation set in the activity where the correlation set is first used.
- CWWBW3051E: A task activity cannot be used in a non-interruptible process (task ''{0}'').
- Explanation: Microflows (non-interruptible processes) must not contain asynchronous activities, such as human task activities or wait activities.
- User Action: Define the process as a long-running process or remove the asynchronous activity.
- CWWBW3052E: A wait activity cannot be used in a non-interruptible process (wait activity ''{0}'').
- Explanation: Microflows (non-interruptible processes) must not contain asynchronous activities, such as human task activities or wait activities.
- User Action: Define the process as a long-running process or remove the asynchronous activity.
- CWWBW3053E: An timeout event in a receive choice activity cannot be used in a non-interruptible process (receive choice activity ''{0}'').
- Explanation: Receive choice activities in microflows (non-interruptible processes) cannot have timeout events.
- User Action: Remove the timeout events, or define the process as long-running.
- CWWBW3054E: A non-interruptible process must not contain more than one receive choice or receive activity: ''{0}''.
- Explanation: Microflows (non-interruptible processes) can have only one start point.
- User Action: Define only one receive choice or receive activity, or define the process as long-running.
- CWWBW3055E: The process does not implement the operation ''{0}'' of the port type ''{1}''.
- Explanation: The process model currently implements one or more operations of the given port type, but not of the given operation.
- User Action: Add a receive choice or receive activity, or an onEvent event with the given port type and operation to the process, or remove this operation from the port type.
- CWWBW3056E: The process is not startable. No receive choice or receive activity was found that creates a new process instance and does not have incoming links or preceding basic activities.
- Explanation: A process is only startable when a receive choice or receive activity is available that creates a new process instance and when this activity is not the target of anylinks or has any preceding basic activities.
- User Action: Ensure that all of the receive choice and receive activities are defined correctly, or add a receive choice or receive activity that can create a process instance.
- CWWBW3057E: The variable must not be set because an output element is available (process onEvent event {0}, variable ''{1}'').
- Explanation: The data received by this onEvent event can be stored in the onEvent variable, which must be message-typed, or in one or more XSD-typedvariables specified in the output element.
- User Action: Remove the variable attribute from the onEvent event.
- CWWBW3058E: Abstract processes are not supported.
- Explanation: Abstract process models are not supported because they cannot be executed.
- User Action: Declare the process model as non-abstract.
- CWWBW3059E: The parameter-extension cannot be used for the message ''{0}'' (process onEvent event {1}).
- Explanation: The input message of the used operation in the onEvent event cannot be used together with the parameter-extension. For example, the message contains an array, whichcannot be mapped to data-typed variables in the process.
- User Action: Either modify the message to be used with the parameter extension or use a message-type variable.
- CWWBW3060E: The parameter ''{0}'' is not mapped to an element or part (process onEvent event {1}, parameter {2}).
- Explanation: A parameter have been found which does not map to an element in the wrapper or to a part in the message.
- User Action: Remove the parameter or map it to a valid element or part.
- CWWBW3061E: The variable name ''{0}'' is used already in the same onEvent event (output element of process onEvent event {1}, parameter {2}).
- Explanation: A variable name can be used only once in an output element.
- User Action: Use another variable name.
- CWWBW3062E: A matching propertyAlias definition was not found for the property ''{0}'' and the messageType ''{1}'' (process onEvent event {2}, correlation set ''{3}'').
- Explanation: A propertyAlias definition is needed to map the parts of a messageType to the correlation properties.
- User Action: Define the propertyAlias.
- CWWBW3063E: The part ''{0}'' referenced in the propertyAlias for the property ''{1}'' and the messageType ''{2}'' was not found (process onEvent event {3},correlation set ''{4}'').
- Explanation: The part must be defined for the messageType.
- User Action: Define the part, or use an existing part in the propertyAlias.
- CWWBW3064E: The part ''{0}'' referenced in the propertyAlias for the property ''{1}'' and the messageType ''{2}'' does not reference a valid XMLschema simple type (process onEvent event {3}, correlation set ''{4}'').
- Explanation: The selected part of the messageType must be an XML schema simple type because a property can only have XML schema simple types.
- User Action: Select a part that has an XML schema simple type.
- CWWBW3065E: The type of the part ''{0}'' of the messageType ''{1}'' and the type of the property ''{2}'' are not the same (process onEvent event {3}, correlation set ''{4}'').
- Explanation: The selected part of the messageType in the propertyAlias does not have the same type as the property type.
- User Action: Select a part that has same XML schema simple type as the property type.
- CWWBW3066E: Multiple propertyAlias definitions were found for the property ''{0}'' and the messageType ''{1}'' (process onEvent event {2}, correlation set ''{3}'').
- Explanation: A property-messageType pair can have only one propertyAlias definition.
- User Action: Ensure that only one propertyAlias is available for the property-messageType pair. If you need more than one part of a messageType as a property,create properties and propertyAlias definitions for additional parts of the same messageType.
- CWWBW3067E: The referenced human task ''{0}'' cannot be found (process adminTask or activityAdminTask element).
- Explanation: The human task referenced in the process adminTask or the activityAdminTask element cannot be found.
- User Action: Remove the human task reference or ensure that the human task can be found.
- CWWBW3068E: The referenced human task ''{0}'' is not an administrative task (process adminTask or activityAdminTask element).
- Explanation: The human task referenced in the process adminTask or the activityAdminTask element must be an administrative task.
- User Action: Reference an administrative task.
- CWWBW3069E: The referenced human task ''{0}'' cannot be found (process onEvent event {1}).
- Explanation: The human task referenced in the process onEvent event cannot be found.
- User Action: Remove the human task reference or ensure that the human task can be found.
- CWWBW3070E: The referenced human task ''{0}'' is not an originating task (process onEvent event {1}).
- Explanation: The human task referenced in the process onEvent event must be an originating task.
- User Action: Reference an originating task.
- CWWBW3071E: The portType referenced in the process onEvent event {0} and in the referenced human task ''{1}'' must be the same.
- Explanation: The portTypes must be the same.
- User Action: Ensure that the portTypes are the same.
- CWWBW3072E: The operation referenced in the process onEvent event {0} and in the referenced human task ''{1}'' must be the same.
- Explanation: The operations must be the same.
- User Action: Ensure that the operations are the same.
- CWWBW3073E: The part is not set in the propertyAlias for the property ''{0}'' and the messageType ''{1}'' (process onEvent event {2},correlation set ''{3}'').
- Explanation: The part must be set in the propertyAlias.
- User Action: Set the part.
- CWWBW3074E: The query language ''{0}'' used in the propertyAlias is not supported. It must be one of ''{1}'' (process onEvent event {2},correlation set ''{3}'', propertyAlias for the property ''{4}'' and the messageType ''{5}'').
- Explanation: The specified query language is unknown. Queries specified in this query language cannot be run.
- User Action: Use one of the supported query languages.
- CWWBW3075E: The expression is not valid (process timeout event {0}, expression language ''{1}'').
- Explanation: The specified expression is not a valid expression for the given expression language.
- User Action: Check the expression and the expression language.
- CWWBW3076E: A reply activity was not found that matches the process onEvent event {0}.
- Explanation: For each two-way operation onEvent event in the process event handler, the process must contain at least one reply activity with the same port type and operation.
- User Action: Add a reply activity to the process with the same port type and operation as the process onEvent event.
- CWWBW3077E: An event handler cannot be used in a non-interruptible process.
- Explanation: Microflows (non-interruptible processes) must not contain event handlers, neither on the process nor on scope activities.
- User Action: Define the process as a long-running process or remove the event handler.
- CWWBW3078E: An event handler cannot be used in a non-interruptible process (scope activity ''{0}'').
- Explanation: Microflows (non-interruptible processes) must not contain event handlers, neither on the process nor on scope activities.
- User Action: Define the process as a long-running process or remove the event handler.
- CWWBW3079E: A compensation handler cannot be used in a non-interruptible process (activity ''{0}'').
- Explanation: Microflows (non-interruptible processes) must not contain compensation handlers, neither on scope activities nor on invoke activities. However, the undo actionon invoke activities can be used within microflows.
- User Action: Define the process as a long-running process or remove the compensation handler.
- CWWBW3080E: An expiration element cannot be used in a non-interruptible process (activity ''{0}'').
- Explanation: Microflows (non-interruptible processes) must not contain any expiration elements.
- User Action: Define the process as a long-running process or remove the expiration element.
- CWWBW3081E: A compensate activity cannot be used in a non-interruptible process (compensate activity ''{0}'').
- Explanation: Microflows (non-interruptible processes) must not contain compensate activities.
- User Action: Define the process as a long-running process or remove the compensate activity.
- CWWBW3082W: The one-way process specifies the autonomy 'child'. The attribute will be ignored.
- Explanation: For an one-way process, the autonomy cannot be set to 'child' because one-way processes are called asynchronously, not synchronously.
- User Action: Remove the autonomy attribute from the process or set it to 'peer'.
- CWWBW3083E: There are too many variable type definitions set for the variable ''{0}'' (process onEvent event {1}, parameter {2}, type ''{3}'', element ''{4}'').
- Explanation: The type, or element attributes define the type of a variable. Exactly one of these attributes must be set.
- User Action: Ensure that there is only one variable type definition set for the variable.
- CWWBW3084E: The XSD element declaration ''{0}'' was not found (process onEvent event {1}, parameter {2}, variable ''{3}'').
- Explanation: The XSD element declaration referenced in the variable must be either defined in-line in a WSDL interface or in an XML schema.
- User Action: Check that the XSD element declaration is correctly referenced and that it is defined correctly.
- CWWBW3085E: The XSD type definition ''{0}'' was not found (process onEvent event {1}, parameter {2}, variable ''{3}'').
- Explanation: The XSD type definition referenced in the variable must be either a valid built-in XML schema simple type or it must be defined in-line in a WSDLinterface or in an XML schema.
- User Action: Check that the XSD type definition is correctly referenced and that it is defined correctly.
- CWWBW3086E: The variable ''{0}'' must have a variable type definition (process onEvent event {1}, parameter {2}).
- Explanation: The type, or element attributes are used to specify the type of a variable. Exactly one of these attributes must be set.
- User Action: Provide a variable type definition for the variable.
- CWWBW3087E: The XSD type definition ''{0}'' was not found (process onEvent event {1}, parameter {2}, matching part or element ''{3}'').
- Explanation: The XSD type definition referenced in the matching part or element must be either a valid built-in XML schema simple type or it must be defined in-line in a WSDLinterface or in an XML schema.
- User Action: Check that the XSD type definition is correctly referenced and that it is defined correctly.
- CWWBW3088E: The XSD element declaration ''{0}'' was not found (process onEvent event {1}, parameter {2}, matching part or element ''{3}'').
- Explanation: The XSD element declaration referenced in the matching part or element must be either defined in-line in a WSDL interface or in an XML schema.
- User Action: Check that the XSD element declaration is correctly referenced and that it is defined correctly.
- CWWBW3089E: The element ''{0}'' cannot be assigned to variable ''{1}'' because the data type does not match (process onEvent event {2}, parameter {3}).
- Explanation: The selected element and the variable are of incompatible types. Only compatible types can be assigned, for example from xsd:string to xsd:string.
- User Action: Ensure the types are compatible.
- CWWBW3090E: The part ''{0}'' cannot be assigned to variable ''{1}'' because the data type does not match (process onEvent event {2}, parameter {3}).
- Explanation: The selected message-part and the variable are of incompatible types. Only compatible types can be assigned, for example from xsd:int to xsd:int.
- User Action: Ensure the types are compatible.
- CWWBW3091E: The XSD element ''{0}'' is not mapped to a parameter (process onEvent event {1}).
- Explanation: An element have been found in the wrapper which does not map to a parameter.
- User Action: Remove the element or map it to a parameter.
- CWWBW3092E: The message-part ''{0}'' is not mapped to a parameter (process onEvent event {1}).
- Explanation: A message-part have been found in the wrapper which does not map to a parameter.
- User Action: Remove the message-part or map it to a parameter.
- CWWBW3093E: The process partner name ''{0}'' is used already.
- Explanation: The name of a partner must be unique within its own scope.
- User Action: Use a different partner name.
- CWWBW3094E: The process correlation set name ''{0}'' is used already.
- Explanation: The name of a correlation set must be unique within its own scope.
- User Action: Use a different correlation set name.
- CWWBW3095E: The correlation set ''{0}'' is used already (process onEvent event {1}).
- Explanation: The correlation set can be used only once per event.
- User Action: Ensure the correlation set is used only once in the given event.
- CWWBW3100E: The variable ''{0}'' is not defined (activity ''{1}'').
- Explanation: The variable used in the activity is not defined.
- User Action: Check that the variable name is defined correctly.
- CWWBW3101E: The catch element does not specify a fault name, a fault variable with a type specification, or both (fault handler of activity ''{0}'', catchelement {1}).
- Explanation: For a catch element, the fault name, the fault variable with a type specification, or both must be set.
- User Action: Remove the catch element or define a fault name, a fault variable with a type specification, or both.
- CWWBW3102E: If the catch element has the fault variable set, it must also have a type specification set (fault handler of activity ''{0}'', catch element {1},fault variable ''{2}'').
- Explanation: If the fault variable is set on a catch element, the type specification must be set too.
- User Action: Specify a type for the catch element.
- CWWBW3103E: The catch element cannot have the fault message type and the fault type set (fault handler of activity ''{0}'', catch element {1}, fault messagetype ''{2}'', faultType ''{3}'').
- Explanation: Either the fault message type or the fault type can be set on the catch element.
- User Action: Remove either the fault message type or the fault type.
- CWWBW3104E: If the catch element has the fault message type set, it must also have a fault variable set (fault handler of activity ''{0}'', catch element {1},fault message type ''{2}'').
- Explanation: If the fault message type is set on the catch element, the fault variable must be set too.
- User Action: Define the fault variable.
- CWWBW3105E: If the catch element has the fault type set, it must also have a fault variable set (fault handler of activity ''{0}'', catch element {1},fault type ''{2}'').
- Explanation: If the fault type is set on the catch element, the fault variable must be set too.
- User Action: Specify a fault variable for the catch element.
- CWWBW3106E: The messageType ''{0}'' was not found (fault handler of activity ''{1}'', catch element {2}, fault variable ''{3}'').
- Explanation: The messageType referenced in the catch element is not defined in the WSDL interface.
- User Action: Check that the messageType is defined correctly in the WSDL interface.
- CWWBW3107E: The type ''{0}'' was not found (fault handler of activity ''{1}'', catch element {2}, fault variable ''{3}'').
- Explanation: The type referenced in the catch element is not defined in the WSDL interface.
- User Action: Check that the type is defined correctly in the WSDL interface.
- CWWBW3108E: The fault handler must contain a catch element or a catch all element (fault handler of activity ''{0}'').
- Explanation: A fault handler must have at least one catch element or one catch all element.
- User Action: Define a catch element or a catch all element, or remove the fault handler.
- CWWBW3109E: The variable ''{0}'' cannot be used here, because the variable messageType uses part-level messages (activity ''{1}'',messageType ''{2}'').
- Explanation: A variable that uses a messageType with one or more parts that reference message types can be used only as an input variable in invoke or transformactivities and in Java snippets.
- User Action: Use a different variable in this activity.
- CWWBW3110E: The messageType ''{0}'' cannot be used here, because it uses part-level message types (fault handler of activity ''{1}'', catchelement {2}, variable ''{3}'').
- Explanation: A variable that uses a messageType with one or more parts that reference message types can be used only as an input variable in invoke or transformactivities and in Java snippets.
- User Action: Use a different messageType for the fault variable.
- CWWBW3111E: The adminTask, expiration, script, and undo elements cannot be used in the activity ''{0}''. These elements are allowed not in invoke activities.
- Explanation: None.
- User Action: Remove the elements from the activity.
- CWWBW3112E: The custom activity element ''{0}'' cannot be used in the activity ''{1}''. This element is allowed only in invoke activities.
- Explanation: None.
- User Action: Remove the custom activity element from the activity.
- CWWBW3113E: The task element cannot be used in the activity ''{0}''.
- Explanation: This element is usually allowed only in invoke and receive activities. However, the task element is also allowed in receive choice activitiesin the receive element.
- User Action: Remove the task element from the activity.
- CWWBW3114E: The annotation element cannot be used in the activity ''{0}''. This element is allowed only in scope activities.
- Explanation: None.
- User Action: Remove the annotation element from the activity.
- CWWBW3115E: The timeout element cannot be used in the activity ''{0}''. This element is allowed only in wait activities.
- Explanation: None.
- User Action: Remove the timeout element from the activity.
- CWWBW3116E: The input element cannot be used in the activity ''{0}''. This element is allowed only in invoke and reply activities.
- Explanation: None.
- User Action: Remove the input element from the activity.
- CWWBW3117E: The output element cannot be used in the activity ''{0}''. This element is allowed only in invoke and receive activities.
- Explanation: The output element is also allowed in receive choice activities in the receive element.
- User Action: Remove the output element from the activity.
- CWWBW3118E: The continueOnError and transactionalBehavior attributes cannot be used in the activity ''{0}''. They are allowed only ininvoke activities.
- Explanation: None.
- User Action: Remove the attributes from the activity.
- CWWBW3119E: The fault attribute cannot be used in the activity ''{0}''. This attribute is allowed only in reply activities.
- Explanation: None.
- User Action: Remove the fault attribute from the activity.
- CWWBW3120E: The compensable attribute cannot be used in the activity ''{0}''. This attribute is allowed only in scope activities.
- Explanation: None.
- User Action: Remove the compensable attribute from the activity.
- CWWBW3121E: The script, task, and custom activity elements are mutually exclusive (invoke activity ''{0}'').
- Explanation: Invoke activities can be extended to a script activity using a script element, a human task activity using a task element, or a customactivity using an element from a different namespace. Combinations of these extension elements arenot allowed.
- User Action: Ensure that only one of the extension elements is used in the invoke activity.
- CWWBW3122E: The link ''{0}'' is not defined (referenced in the activity ''{1}'').
- Explanation: A link must be defined in a parallel activities activity before it can be referenced in a different activity. Additionally, this activity must be nestedin the parallel activities activity because links are visible only inside the defining parallel activities activity.
- User Action: Ensure that the referenced link is defined in one of the parent parallel activities activities.
- CWWBW3123E: The link ''{0}'' is parallel link-to-link ''{1}'' (from activity ''{2}'' to activity ''{3}''). Parallel links are not allowed.
- Explanation: Parallel links are links that connect the same activities.
- User Action: Remove one of the two parallel links.
- CWWBW3124E: The XSD-typed variable cannot be used here (activity ''{0}'', variable ''{1}'').
- Explanation: For this activity, only WSDL-typed variables are allowed.
- User Action: Use a WSDL-typed variable.
- CWWBW3125E: The undo action is not allowed (activity ''{0}'').
- Explanation: Undo actions are allowed only for invoke activities, but not for script, human task, or custom activities.
- User Action: Remove the undo action from the activity.
- CWWBW3126E: The expiration element is not allowed for the activity ''{0}''.
- Explanation: For the given activity, an expiration element is not allowed.
- User Action: Remove the expiration element.
- CWWBW3127W: The expiration element is set for the activity ''{0}''. Define an appropriate timeout fault handler.
- Explanation: When the activity expires a timeout fault is thrown. To handle this fault, set an appropriate timeout fault handler.
- User Action: Set an appropriate timeout fault handler.
- CWWBW3128E: The partner ''{0}'' was not found (activity ''{1}'').
- Explanation: The partner referenced in the activity is not defined.
- User Action: Ensure that the partner used is correct and that it is defined.
- CWWBW3129E: The partner ''{0}'' does not define the myRole role (activity ''{1}'').
- Explanation: Partners used in receive or reply activities must define the myRole role.
- User Action: Define the myRole role for the partner or use a different partner.
- CWWBW3130E: The portType ''{0}'' was not found (activity ''{1}'').
- Explanation: The portType referenced in the activity is not defined in the WSDL interface.
- User Action: Ensure that the portType used is correct and that it is defined in the WSDL interface.
- CWWBW3131E: The portType referenced in the activity ''{0}'' and in the role ''{1}'' must be the same (partner ''{2}'', partnerLinkType ''{3}'').
- Explanation: The portType attribute in activities is optional. If this attribute is set, it must be the same as the portType set for the role used in this activity in the partner.
- User Action: Ensure that the portType attributes are the same.
- CWWBW3132E: The operation ''{0}'' was not found (activity ''{1}'').
- Explanation: The operation referenced in the activity is not defined in the WSDL interface.
- User Action: Ensure that the operation used is correct and that it is defined in the WSDL interface.
- CWWBW3133E: The input element is not defined in the operation ''{0}'' (activity ''{1}'').
- Explanation: Operations used in this kind of activity must have an input element.
- User Action: Define an input element, or use a different operation.
- CWWBW3134E: The output element is not defined in the operation ''{0}'' (activity ''{1}'').
- Explanation: Operations used in this kind of activity must have an output element.
- User Action: Define an output element, or use a different operation.
- CWWBW3135E: The messageType is not set in the input element of the operation ''{0}'' (activity ''{1}'').
- Explanation: The input messageType must be set when the operation is used in this kind of activity.
- User Action: Set the input messageType, or use a different operation.
- CWWBW3136E: The messageType is not set in the output element of the operation ''{0}'' (activity ''{1}'').
- Explanation: The output messageType must be set when the operation is used in this kind of activity.
- User Action: Set the output messageType, or use a different operation.
- CWWBW3137E: The messageType is not set in the fault element of the operation ''{0}'' (activity ''{1}'').
- Explanation: The fault messageType must be set when the operation is used in this kind of activity.
- User Action: Set the fault messageType, or use a different operation.
- CWWBW3138E: The messageType ''{0}'' referenced in the operation ''{1}'' was not found (activity ''{2}'').
- Explanation: The messageType referenced must be defined when the operation is used in this kind of activity.
- User Action: Set the messageType, or use a different operation.
- CWWBW3139E: The messageType of the variable ''{0}'' and the input element of operation ''{1}'' must be the same (activity ''{2}'').
- Explanation: The messageType of the variable and the input element of the operation must be the same.
- User Action: Ensure that the variable and the input element have the same messageType.
- CWWBW3140E: The messageType of the variable ''{0}'' and the output element of operation ''{1}'' must be the same (activity ''{2}'').
- Explanation: The messageType of the variable and the output element of the operation must be the same.
- User Action: Ensure that the variable and the output element have the same messageType.
- CWWBW3141E: The messageType of the variable ''{0}'' and the fault ''{1}'' of the operation ''{2}'' must be the same (activity ''{3}'').
- Explanation: The messageType of the variable and the fault element of the operation must be the same.
- User Action: Ensure that the variable and the fault element have the same messageType.
- CWWBW3142E: The variable is not set (activity ''{0}'').
- Explanation: A mandatory variable for the activity is not defined.
- User Action: Define the mandatory variable.
- CWWBW3143E: The input variable is not set (activity ''{0}'').
- Explanation: A mandatory input variable for the activity is not defined. For invoke activities the input variable is mandatory.
- User Action: Define the mandatory input variable.
- CWWBW3144E: The output variable is not set (activity ''{0}'').
- Explanation: A mandatory output variable for the activity is not defined. The output variable is mandatory for synchronous invoke activities.
- User Action: Define the mandatory output variable.
- CWWBW3145E: The output variable ''{0}'' must not be set, because the operation is one-way (activity ''{1}'', operation ''{2}'').
- Explanation: A one-way operation does not return a message.
- User Action: Do not define an output variable or use a request-response operation instead of a one-way operation.
- CWWBW3146E: The correlation set ''{0}'' was not found (activity ''{1}'').
- Explanation: The correlation set used in the activity is not defined.
- User Action: Define the correlation set, or remove it from the activity.
- CWWBW3147E: The timeout event must specify at least a for expression, an until expression, or a repeatEvery expression (activity ''{0}'', timeout event {1}).
- Explanation: The for element defines the duration expression after which the timeout event is signaled. The until element specifieswhen the timeout event is fired. If the repeatEvery element is specified, the timeout eventwill be fired repeatedly once each time the duration period expires. One of these threeexpressions or a repeatEvery expression with a for expression or an until expressionmust occur in an timeout event.
- User Action: Specify a for expression, an until expression, or a repeatEvery expression.
- CWWBW3148E: The timeout event must specify at least a for expression, an until expression, a timeout expression, or a repeatEvery expression (activity ''{0}'', timeout event {1}).
- Explanation: The for element defines the duration expression after which the event is signaled. The until element specifieswhen the timeout event is fired. The timeout element specifies a timeout using acalendar supplied by the WebSphere Application Server scheduling service, or user-writtencalendars adhering to those conventions. If the repeatEvery element is specified, the timeout eventis fired repeatedly once each time the duration period expires. One of these fourexpressions or a repeatEvery expression with a for expression, an until expression, or atimeout expression must occur in an timeout event.
- User Action: Specify a for expression, an until expression, a timeout expression, or a repeatEvery expression.
- CWWBW3149E: The timeout event cannot specify a for expression and a timeout expression or an until expression and a timeout expression(activity ''{0}'', timeout event {1}).
- Explanation: The for element specifies the duration expression after which the event is signaled. The until element specifieswhen the timeout event is fired. The timeout element specifies a timeout using acalendar supplied by WebSphere Application Server scheduling service, or user-writtencalendars adhering to those conventions. If the repeatEvery element is specified, the timeout eventis fired repeatedly once each time the duration period expires. One of these fourexpressions or a repeatEvery expression with a for expression, an until expressionor a timeout expression must occur in an timeout event.
- User Action: Specify a for, until, timeout or repeatEvery expression.
- CWWBW3150E: The expression language ''{0}'' is not supported. It must be one of ''{1}'' (activity ''{2}'', timeout event {3}).
- Explanation: The specified expression language is unknown. Expressions specified in this expression language cannot be executed.
- User Action: Use one of the supported expression languages.
- CWWBW3151E: A matching propertyAlias definition was not found for the property ''{0}'' and messageType ''{1}'' (activity ''{2}'', correlation set ''{3}'').
- Explanation: A propertyAlias definition is needed to map the parts of a messageType to the correlation properties.
- User Action: Define the propertyAlias.
- CWWBW3152E: The part ''{0}'' referenced in the propertyAlias definition for the property ''{1}'' and messageType ''{2}'' was not found (activity ''{3}'', correlation set ''{4}'').
- Explanation: The part used must be defined for the messageType.
- User Action: Define the part or use an existing part in the propertyAlias definition.
- CWWBW3153E: The part ''{0}'' referenced in the propertyAlias definition for the property ''{1}'' and messageType ''{2}'' does not reference a valid XML schemasimple type (activity ''{3}'', correlation set ''{4}'').
- Explanation: The selected part of the messageType must be an XML schema simple type because a property can have only XML schema simple types.
- User Action: Select a part with an XML schema simple type.
- CWWBW3154E: The type of the part ''{0}'' of the messageType ''{1}'' and the type of the property ''{2}'' are not the same (activity ''{3}'', correlation set ''{4}'').
- Explanation: The selected part of the messageType in the propertyAlias is not of the same type as the type of the property.
- User Action: Select a part that has the same XML schema simple type as the property type.
- CWWBW3155E: Multiple propertyAlias definitions were found for the property ''{0}'' and the messageType ''{1}'' (activity ''{2}'', correlation set ''{3}'').
- Explanation: Every property-messageType pair can have only one propertyAlias definition.
- User Action: Ensure only one propertyAlias is available for the property-messageType pair. If more than one part of a messageType is needed as a property,create properties and propertyAlias definitions for other parts of the same messageType.
- CWWBW3156E: Because the receive choice or receive activity ''{0}'' creates a process instance, it cannot be placed after the activity or the activities ''{1}''.
- Explanation: A receive choice or receive activity that is preceded by any basic activity cannot create a process instance.
- User Action: Remove the preceding basic activities or change the receive choice or receive activity so that it does not create a process instance.
- CWWBW3157E: The activity ''{0}'' is the target of the link or links ''{1}'', but it can create a process instance or it contains activities that cancreate a process instance.
- Explanation: A receive choice or receive activity that is the target of one or more links cannot create a process instance. In addition, a complex activity that contains areceive choice or receive activity that can create a process instance must not have anyincoming links.
- User Action: Remove the incoming links or redefine the receive choice or receive activity so that it does not create a process instance.
- CWWBW3158W: The while loop activity ''{1}'' contains the receive choice or receive activity ''{0}'' that creates a process instance. If the condition of the while loop activityis false when the condition is evaluated for the first time, the process does not run correctly.
- Explanation: If the condition of the while loop activity is not true when it is evaluated the first time, the receive choice or receive activity cannot be navigated. The processdoes not run correctly in this case.
- User Action: Put the receive choice or receive activity outside of the while loop activity.
- CWWBW3159E: The receive choice or receive activity ''{0}'' that creates a process instance cannot be contained in a catch, catch all, receive, onEvent, timeout, compensation handler,case, or otherwise element.
- Explanation: Activities that create process instances are not reachable in catch, catch all, receive, onEvent, timeout, compensation handler, case, andotherwise elements.
- User Action: Move the receive choice or receive activity to a reachable position, or change the receive choice/receive activity so that it does not create a new process instance.
- CWWBW3160E: The parallel activities activity ''{0}'' contains one or more activities that can start processes, but it also contains the activity ''{1}'' which cannot start a process.
- Explanation: An activity that can start a process can be: 1.A receive choice or receive activity that can create a process instance; 2.A complex activity that containsa receive choice or receive activity that can create a process instance. If a parallel activities activity containsat least one these types of activity, all of the activities without incoming links must activitiesthat can start processes.
- User Action: Use only activities that can start processes as the starting points in the parallel activities activity or remove these activities from the parallel activities activity.
- CWWBW3161E: The activity ''{0}'' does not reference the partner ''null'' (used partner ''{1}'').
- Explanation: For a custom or script activity, the partner must be 'null'.
- User Action: Use the partner 'null' for the custom or script activity.
- CWWBW3162E: The activity ''{0}'' does not reference the portType ''wpc:null'' (used portType ''{1}'').
- Explanation: For a custom or script activity, the portType must be 'wpc:null'.
- User Action: Use the portType 'wpc:null' for the custom or script activity.
- CWWBW3163E: The activity ''{0}'' does not reference the operation ''null'' (used operation ''{1}'').
- Explanation: For a custom or script activity, the operation must be 'null'.
- User Action: Use the operation 'null' for the custom or script activity.
- CWWBW3164W: The variable attribute ''{0}'' is not needed (activity ''{1}'').
- Explanation: The variable attribute used in the custom or script activity will be ignored.
- User Action: Remove the variable attribute from the custom or script activity.
- CWWBW3165W: The input element is not needed (activity ''{0}'').
- Explanation: The input element used in the custom or script activity will be ignored.
- User Action: Remove the input element from the custom or script activity.
- CWWBW3166W: The output element is not needed (activity ''{0}'').
- Explanation: The output element used in the custom or script activity will be ignored.
- User Action: Remove the output element from the custom or script activity.
- CWWBW3167E: The output element must not be set, because the operation is one-way (activity ''{0}'', operation ''{1}'').
- Explanation: A one-way operation does not return a message.
- User Action: Do not define an output element or use a request-response operation instead of a one-way operation.
- CWWBW3168E: The inputVariable attribute must not be set because an input element is available (activity ''{0}'', inputVariable ''{1}'').
- Explanation: The data that is sent by this invoke or human task activity can be identified by the input variable attribute, which must be message-typed, or by one or more XSD-typedvariables specified in the input element.
- User Action: Remove the inputVariable attribute from the activity.
- CWWBW3169E: The outputVariable attribute must not be set because an output element is available (activity ''{0}'', outputVariable ''{1}'').
- Explanation: The data that is received by this invoke or human task activity can be stored in the outputVariable attribute, which must be message-typed, or in one or more XSD-typedvariables specified in the output element.
- User Action: Remove the outputVariable attribute from the activity.
- CWWBW3170E: The variable ''{0}'' is not defined (input or output element of activity ''{1}'', parameter {2}).
- Explanation: The variable used in the parameter extension is not defined.
- User Action: Check that the variable name is defined correctly.
- CWWBW3171E: The message-typed variable cannot be used here (input/output element of activity ''{0}'', parameter {1}, variable ''{2}'').
- Explanation: You can use only element-typed or type-typed variables in input and output elements.
- User Action: Use an XSD-typed variable.
- CWWBW3172E: The variable ''{0}'' cannot be used multiple times in the same input or output element (input or output element of activity ''{1}'', parameter {2}).
- Explanation: A variable can be used only once in an input or output element.
- User Action: Use another XSD-typed variable.
- CWWBW3173E: The referenced human task ''{0}'' cannot be found (activity ''{1}'').
- Explanation: The human task that is referenced in the given activity cannot be found.
- User Action: Remove the human task reference or ensure that the human task can be found.
- CWWBW3174E: The portType that is referenced in the activity ''{0}'' and in the referenced human task ''{1}'' must be the same.
- Explanation: The portTypes must be the same.
- User Action: Ensure that the portTypes are the same.
- CWWBW3175E: The operation that is referenced in the activity ''{0}'' and in the referenced human task ''{1}'' must be the same.
- Explanation: The operations must be the same.
- User Action: Ensure that the operations are the same.
- CWWBW3176E: The referenced human task ''{0}'' is not an administrative task (activity ''{1}'').
- Explanation: The human task that is referenced in the receive activity must be an administrative task.
- User Action: Reference an administrative task.
- CWWBW3177E: The part is not set in the propertyAlias definition for the property ''{0}'' and messageType ''{1}'' (activity ''{2}'', correlation set ''{3}'').
- Explanation: The part must be set in the propertyAlias.
- User Action: Set the part.
- CWWBW3178E: The query language ''{0}'' used in the propertyAlias is not supported. It must be one of ''{1}'' (activity ''{2}'', correlation set ''{3}'', propertyAliasfor the property ''{4}'' and the messageType ''{5}'').
- Explanation: The specified query language is unknown. Queries specified in this query language cannot be run.
- User Action: Use one of the supported query languages.
- CWWBW3179E: The expiration element must specify at least a for expression, an until expression, or a timeout expression (activity ''{0}'').
- Explanation: The for element defines the duration expression after which the expiration is signaled. The until element specifies when the expiration is fired.The timeout element specifies a timeout using a calendar supplied by the WebSphereApplication Server scheduling service, or user-written calendars adhering to thoseconventions. One of these three expressions must occur in an expiration element.
- User Action: Specify a for expression, an until expression, or a timeout expression.
- CWWBW3180E: The expression language ''{0}'' of the expiration element is not supported. It must be one of ''{1}'' (activity ''{2}'').
- Explanation: The specified expression language is unknown. Expressions specified in this expression language cannot be executed.
- User Action: Use one of the supported expression languages.
- CWWBW3181E: The expression language ''{0}'' of the transition condition is not supported. It must be one of ''{1}'' (activity ''{2}'', source element {3}, link ''{4}'').
- Explanation: The specified expression language is unknown. Expressions specified in this expression language cannot be executed.
- User Action: Use one of the supported expression languages.
- CWWBW3182E: The expression language ''{0}'' of the join condition is not supported. It must be one of ''{1}'' (activity ''{2}'').
- Explanation: The specified expression language is unknown. Expressions specified in this expression language cannot be executed.
- User Action: Use one of the supported expression languages.
- CWWBW3183E: The transition condition expression is invalid (activity ''{0}'', source element {1}, link ''{2}'', expression language ''{3}'').
- Explanation: The specified expression is not a valid expression for the given expression language or it is not valid in this context. For example, if you use the built-inexpression language in the transition condition, only the values 'wpc:true', 'wpc:false' and'wpc:otherwise' are allowed.
- User Action: Check the expression and the expression language.
- CWWBW3184E: The join condition expression is invalid (activity ''{0}'', expression language ''{1}'').
- Explanation: The specified expression is not a valid expression for the given expression language or it is not valid in this context. For example, if you use the built-inexpression language in the join condition, only the values 'wpc:true', 'wpc:false', 'wpc:all' or'wpc:any' are allowed.
- User Action: Check the expression and the expression language.
- CWWBW3185E: The parameter-extension cannot be used for the message ''{0}'' (activity ''{1}'').
- Explanation: The input or output message of the used operation of the activity cannot be used together with the parameter-extension. For example, the message contains an array, whichcannot be mapped to data-typed variables in the process.
- User Action: Either modify the message to be used with the parameter extension or use a message-type variable.
- CWWBW3186E: The parameter ''{0}'' is not mapped to an element or part (activity ''{1}'', parameter {2}).
- Explanation: A parameter have been found which does not map to an element in the wrapper or to a part in the message.
- User Action: Remove the parameter or map it to a valid element or part.
- CWWBW3187E: The XSD type definition ''{0}'' was not found (activity ''{1}'', parameter {2}, matching part or element ''{3}'').
- Explanation: The XSD type definition referenced in the matching part or element must be either a valid built-in XML schema simple type or it must be defined in-line in a WSDLinterface or in an XML schema.
- User Action: Check that the XSD type definition is correctly referenced and that it is defined correctly.
- CWWBW3188E: The XSD element declaration ''{0}'' was not found (activity ''{1}'', parameter {2}, matching part or element ''{3}'').
- Explanation: The XSD element declaration referenced in the matching part or element must be either defined in-line in a WSDL interface or in an XML schema.
- User Action: Check that the XSD element declaration is correctly referenced and that it is defined correctly.
- CWWBW3189E: The variable ''{0}'' cannot be assigned to element or part ''{1}'' because the data type does not match (activity ''{2}'', parameter {3}).
- Explanation: The selected element and the variable are of incompatible types. Only compatible types can be assigned, for example from xsd:string to xsd:string.
- User Action: Ensure the types are compatible.
- CWWBW3190E: The element or part ''{0}'' cannot be assigned to variable ''{1}'' because the data type does not match (activity ''{2}'', parameter {3}).
- Explanation: The selected element and the variable are of incompatible types. Only compatible types can be assigned, for example from xsd:string to xsd:string.
- User Action: Ensure the types are compatible.
- CWWBW3191E: The XSD element ''{0}'' is not mapped to a parameter (activity ''{1}'').
- Explanation: An element have been found in the wrapper which does not map to a parameter.
- User Action: Remove the element or map it to a parameter.
- CWWBW3192E: The message-part ''{0}'' is not mapped to a parameter (activity ''{1}'').
- Explanation: A message-part have been found in the wrapper which does not map to a parameter.
- User Action: Remove the message-part or map it to a parameter.
- CWWBW3193E: The correlation set ''{0}'' is used already (activity ''{1}'').
- Explanation: The correlation set can be used only once per activity.
- User Action: Ensure the correlation set is used only once in the given activity.
- CWWBW3300E: The from-specification is not allowed (assign activity ''{0}'', copy element {1}).
- Explanation: Only specific types of from-specifications are allowed.
- User Action: Use an allowed type of from-specification or remove the copy statement.
- CWWBW3301E: The to-specification is not allowed (assign activity ''{0}'', copy element {1}).
- Explanation: Only specific types of to-specifications are allowed.
- User Action: Use an allowed type of to-specification or remove the copy statement.
- CWWBW3302E: The from-to copy combination is not allowed (assign activity ''{0}'', copy element {1}).
- Explanation: Only specific types of copy specifications are allowed.
- User Action: Use an allowed type of copy specification or remove the copy statement.
- CWWBW3303E: The from-variable ''{0}'' is not defined (assign activity ''{1}'', copy element {2}).
- Explanation: The variable used in the assign activity is not defined.
- User Action: Check that the variable name is defined correctly.
- CWWBW3304E: The from-part ''{0}'' was not found (assign activity ''{1}'', copy element {2}, variable ''{3}'').
- Explanation: The part must be defined in the messageType.
- User Action: Define the part, or use an existing part.
- CWWBW3305E: The from-partner ''{0}'' was not found (assign activity ''{1}'', copy element {2}).
- Explanation: The partner referenced in the assign activity is not defined.
- User Action: Ensure that the partner used is correct and that it is defined.
- CWWBW3306E: The to-variable ''{0}'' is not defined (assign activity ''{1}'', copy element {2}).
- Explanation: The variable used in the assign activity is not defined.
- User Action: Check that the variable name is defined correctly.
- CWWBW3307E: The to-part ''{0}'' was not found (assign activity ''{1}'', copy element {2}, variable ''{3}'').
- Explanation: The part must be defined in the messageType.
- User Action: Define the part, or use an existing part.
- CWWBW3308E: The to-partner ''{0}'' was not found (assign activity ''{1}'', copy element {2}).
- Explanation: The partner referenced in the assign activity is not defined.
- User Action: Ensure that the partner is correct and that it is defined.
- CWWBW3309E: The to-partner ''{0}'' does not define the partnerRole role (assign activity ''{1}'', copy element {2}).
- Explanation: Partners used in to-specifications of assign activities must define the partnerRole role.
- User Action: Define the partnerRole role for the partner or use a different partner.
- CWWBW3310E: The messageType of the from-variable ''{0}'' and the to-variable ''{1}'' must be the same (assign activity ''{2}'', copy element {3}, from messageType ''{4}'', tomessageType ''{5}'').
- Explanation: The messageType of the two variables must be the same.
- User Action: Ensure that both variables have the same messageType.
- CWWBW3311E: The XSD type of the from-variable ''{0}'' and the to-variable ''{1}'' must be the same (assign activity ''{2}'', copy element {3}, from XSD type ''{4}'', toXSD type ''{5}'').
- Explanation: The XSD type of the two variables must be the same.
- User Action: Ensure that both variables have the same XSD type.
- CWWBW3312E: The XSD element of the from-variable ''{0}'' and the to-variable ''{1}'' must be the same (assign activity ''{2}'', copy element {3}, from XSD element''{4}'', to XSD element ''{5}'').
- Explanation: The XSD element of the two variables must be the same.
- User Action: Ensure that both variables have the same XSD element type.
- CWWBW3313E: The type of the from-part ''{0}'' and the to-part ''{1}'' must be the same (assign activity ''{2}'', copy element {3}).
- Explanation: The type of the two parts must be the same.
- User Action: Ensure that the parts have the same type.
- CWWBW3314E: The from-partner ''{0}'' does not define the myRole role (assign activity ''{1}'', copy element {2}).
- Explanation: Partners used in from specifications of assign activities must define the role defined by the endpointReference attribute.
- User Action: Define the myRole role for the partner, use a different partner, or define an endpointReference attribute.
- CWWBW3315E: The from-partner ''{0}'' does not define the partnerRole role (assign activity ''{1}'', copy element {2}).
- Explanation: Partners used in from-specifications of assign activities must define the role defined by the endpointReference attribute.
- User Action: Define the partnerRole role for the partner, use a different partner, or define an endpointReference attribute.
- CWWBW3316E: The portType of the from-role ''{0}'' and the to-role ''{1}'' are not the same (assign activity ''{2}'', copy element {3}, from partner ''{4}'', to partner ''{5}'').
- Explanation: The portType of the two roles must be the same.
- User Action: Change the portType of one of the roles, or use a different partner.
- CWWBW3317E: The message-typed from-variable ''{0}'' cannot be assigned to the type-typed or element-typed to-variable ''{1}'' (assign activity ''{2}'', copy element {3}, frommessageType ''{4}'', to type/element ''{5}'').
- Explanation: Message-typed variables can only be assigned to other message-typed variables of the same messageType.
- User Action: Ensure that both variables have the same messageType.
- CWWBW3318E: The type-typed from-variable ''{0}'' cannot be assigned to the message-typed to-variable ''{1}'' (assign activity ''{2}'', copy element {3}, fromtype ''{4}'', to messageType ''{5}'').
- Explanation: Type-typed variables can only be assigned to type-typed or element-typed variables of the same type.
- User Action: Ensure that both variables have the same type.
- CWWBW3319E: The element-typed from-variable ''{0}'' cannot be assigned to the messageType-typed to-variable ''{1}'' (assign activity ''{2}'', copy element {3}, fromelement ''{4}'', to messageType ''{5}'').
- Explanation: Element-typed variables can only be assigned to element-typed or type-typed variables of the same type.
- User Action: Ensure that both variables have the same type.
- CWWBW3320E: The literal type ''{0}:{1}'' is not allowed (assign activity ''{2}'', copy element {3}, from-specification).
- Explanation: This type of literal is not supported.
- User Action: Use another literal type.
- CWWBW3321E: A literal value is not defined (assign activity ''{0}'', copy element {1}, from-specification).
- Explanation: A definition of a literal value is expected in the given from-specification.
- User Action: Define a literal value of the selected type.
- CWWBW3322E: The literal type in the from element and the part type in the to element are not the same (assign activity ''{0}'', copy element {1}).
- Explanation: The literal type and the part type must be the same.
- User Action: Select another literal type or another part.
- CWWBW3323E: The literal value is not of the type ''{0}'' (assign activity ''{1}'', copy element {2}, from-specification).
- Explanation: The literal value must be of the type specified in the given from-specification.
- User Action: Select another literal type or ensure that the literal value is of the expected type.
- CWWBW3324E: The XSD type definition ''{0}'' was not found (assign activity ''{1}'', copy element {2}, base type ''{3}'', type referencing the type that was not found ''{4}'').
- Explanation: The XSD type definition that is referenced must be either a valid built-in XML schema simple type or it must be defined in-line in a WSDL interface or in an XML schema.
- User Action: Check that the XSD type definition is referenced correctly and that it is defined correctly.
- CWWBW3325E: The XSD type definition ''{0}'' is not valid (assign activity ''{1}'', copy element {2}).
- Explanation: The XSD type definition that is referenced in the assign activity cannot be used because it is not valid. For example, loops were found in the type hierarchy.
- User Action: Check that the XSD type definition is valid.
- CWWBW3326E: The query language ''{0}'' used in the propertyAlias is not supported. It must be one of ''{1}'' (assign activity ''{2}'', copy element {3}, propertyAliasfor the property ''{4}'' and the messageType ''{5}'').
- Explanation: The specified query language is unknown. Queries specified in this query language cannot be run.
- User Action: Use one of the supported query languages.
- CWWBW3327E: The part ''{0}'' referenced in the propertyAlias definition for the property ''{1}'' and messageType ''{2}'' does not reference a valid XML schemasimple type (assign activity ''{3}'', copy element {4}).
- Explanation: The selected part of the messageType must be an XML schema simple type because a property can have only XML schema simple types.
- User Action: Select a part with an XML schema simple type.
- CWWBW3328E: The type of the part ''{0}'' of the messageType ''{1}'' and the type of the property ''{2}'' are not the same (assign activity ''{3}'', copy element {4}).
- Explanation: The selected part of the messageType in the propertyAlias is not of the same type as the type of the property.
- User Action: Select a part that has the same XML schema simple type as the property type.
- CWWBW3329E: The query language ''{0}'' is not supported. It must be one of ''{1}'' (assign activity ''{2}'', copy element {3}, from-specification).
- Explanation: The specified query language is unknown. Queries specified in this query language cannot be run.
- User Action: Use one of the supported query languages.
- CWWBW3330E: The query language ''{0}'' is not supported. It must be one of ''{1}'' (assign activity ''{2}'', copy element {3}, to-specification).
- Explanation: The specified query language is unknown. Queries specified in this query language cannot be run.
- User Action: Use one of the supported query languages.
- CWWBW3331E: The expression language ''{0}'' of the expression element is not supported. It must be one of ''{1}'' (assign activity ''{2}'', copy element {3}).
- Explanation: The specified expression language is unknown. Expressions specified in this expression language cannot be run.
- User Action: Use one of the supported expression languages.
- CWWBW3332E: The XSD-typed variable ''{0}'' cannot be used in combination with a property specification (assign activity ''{1}'', copy element {2}).
- Explanation: Properties can be specified only for message-typed variables.
- User Action: Use a message-typed variable or remove the property specification.
- CWWBW3333E: The property ''{0}'' was not found (assign activity ''{1}'', copy element {2}).
- Explanation: The property used must be defined.
- User Action: Ensure the referenced property is defined or refer to another defined property.
- CWWBW3334E: A matching propertyAlias definition was not found for the property ''{0}'' and the messageType ''{1}'' (assign activity ''{2}'', copy element {3}).
- Explanation: A propertyAlias definition is needed to map the parts of a messageType to the property.
- User Action: Define the propertyAlias.
- CWWBW3335E: The part is not set in the propertyAlias for the property ''{0}'' and the messageType ''{1}'' (assign activity ''{2}'', copy element {3}).
- Explanation: The part must be set in the propertyAlias.
- User Action: Set the part.
- CWWBW3336E: The part ''{0}'' referenced in the propertyAlias for the property ''{1}'' and the messageType ''{2}'' was not found (assign activity ''{3}'',copy element {4}).
- Explanation: The part must be defined for the messageType.
- User Action: Define the part, or use an existing part in the propertyAlias.
- CWWBW3337E: Multiple propertyAlias definitions were found for the property ''{0}'' and the messageType ''{1}'' (assign activity ''{2}'',copy element {3}).
- Explanation: A property-messageType pair can have only one propertyAlias definition.
- User Action: Ensure that only one propertyAlias is available for the property-messageType pair. If you need more than one part of a messageType as a property,create properties and propertyAlias definitions for additional parts of the same messageType.
- CWWBW3338E: The XSD type definition ''{0}'' was not found (assign activity ''{1}'', copy element {2}, variable ''{3}'', part ''{4}'').
- Explanation: The XSD type definition that is referenced must be either a valid built-in XML schema simple type or it must be defined in-line in a WSDL interface or in an XML schema.
- User Action: Check that the XSD type definition is referenced correctly and that it is defined correctly.
- CWWBW3339E: The XSD element declaration ''{0}'' was not found (assign activity ''{1}'', copy element {2}, variable ''{3}'', part ''{4}'').
- Explanation: The XSD element declaration that is referenced must be defined in-line in a WSDL interface or in an XML schema.
- User Action: Check that the XSD element declaration is referenced correctly and that it is defined correctly.
- CWWBW3340E: The XSD-typed part ''{0}'' cannot be assigned to the message-typed to-variable ''{1}'' (assign activity ''{2}'', copy element {3}).
- Explanation: A XSD-typed part can only be assigned to XSD-typed variable.
- User Action: Either select only a message-typed variable on the from side, but not a part of this variable, or select a XSD-typed variable on the to side.
- CWWBW3341E: The message-typed from-variable ''{0}'' cannot be assigned to the XSD-typed part ''{1}'' (assign activity ''{2}'', copy element {3}).
- Explanation: A message-typed variable can only be assigned to another message-typed variable.
- User Action: Either select a message-typed variable and a XSD-typed part on the from side, or select a message-typed variable on the to side.
- CWWBW3342E: The XSD type definition ''{0}'' was not found (assign activity ''{1}'', copy element {2}, variable ''{3}'', element referencing the type that was not found ''{4}'').
- Explanation: The XSD type definition that is referenced must be either a valid built-in XML schema simple type or it must be defined in-line in a WSDL interface or in an XML schema.
- User Action: Check that the XSD type definition is referenced correctly and that it is defined correctly.
- CWWBW3343E: The type of the from-variable ''{0}'' and the to-variable ''{1}'' must be the same (assign activity ''{2}'', copy element {3}, from XSD type ''{4}'', toXSD element ''{5}'').
- Explanation: The type of the two variables must be the same.
- User Action: Ensure that both variables have the same type.
- CWWBW3344E: The type of the from-variable ''{0}'' and the to-variable ''{1}'' must be the same (assign activity ''{2}'', copy element {3}, from XSD element ''{4}'', toXSD type ''{5}'').
- Explanation: The type of the two variables must be the same.
- User Action: Ensure that both variables have the same type.
- CWWBW3345E: The XSD type of the from-part ''{0}'' and the to-variable ''{1}'' must be the same (assign activity ''{2}'', copy element {3}, from XSD type ''{4}'', toXSD type ''{5}'').
- Explanation: The XSD type of the part and the variable must be the same.
- User Action: Ensure that the part and the variable have the same type.
- CWWBW3346E: The XSD type of the from-variable ''{0}'' and the to-part ''{1}'' must be the same (assign activity ''{2}'', copy element {3}, from XSD type ''{4}'', toXSD type ''{5}'').
- Explanation: The XSD type of the variable and the part must be the same.
- User Action: Ensure that the variable and the part have the same type.
- CWWBW3347E: The XSD type of the from-part ''{0}'' and the to-part ''{1}'' must be the same (assign activity ''{2}'', copy element {3}, from XSD type ''{4}'', toXSD type ''{5}'').
- Explanation: The XSD type of the two parts must be the same.
- User Action: Ensure that the two parts have the same type.
- CWWBW3400E: The compensate activity can be used only inside a fault handler or a compensation handler (compensate activity ''{0}'').
- Explanation: Compensate activities are used to invoke the compensation handlers of scope activities that complete normally when a fault occurs. Thus, compensateactivities can be used only inside fault handlers or compensation handlers.
- User Action: Remove the compensate activity, or move it to a fault handler or a compensation handler.
- CWWBW3401E: The referenced scope or invoke activity ''{0}'' was not found (compensate activity ''{1}'').
- Explanation: The referenced scope or invoke activity must be defined in the process and it must be contained in this scope. This scope is the scope that defines a fault handleror compensation handler in which the compensate activity is contained. Additionally, the referencedscope or invoke activity must be immediately contained in this scope. For example if this scopeis Scope1 and it contains Scope2 which contains Scope3, Scope3 normally cannot be referenced. Scope3can be referenced only if Scope2 is not compensable. However, other structured activitiescan come between these scope activities. For example, Scope2 can be referenced from the compensate activityif Scope1 contains Flow1 which then contains Scope2.
- User Action: Ensure that the scope or invoke activity is immediately contained in this scope.
- CWWBW3402E: The compensate activity cannot be contained inside an invoke activity (compensate activity ''{0}'', invoke activity ''{1}'').
- Explanation: Although the invoke activity is a basic activity, it cannot contain any other scope or invoke activities which can be compensated. Therefore, do not placea compensate activity in the fault handler or compensation handler of the invoke activity.
- User Action: Remove the compensate activity from the invoke activity.
- CWWBW3403E: The referenced scope activity ''{0}'' cannot be compensated (compensate activity ''{1}'').
- Explanation: The referenced scope activity has the compensable attribute set to 'no'. Thus the scope activity cannot be compensated.
- User Action: Set the compensate attribute of the referenced scope activity to 'yes', or reference a different scope activity.
- CWWBW3404E: The referenced invoke activity ''{0}'' does not have a compensation handler set (compensate activity ''{1}'').
- Explanation: The referenced invoke activity has no compensation handler set. Therefore, an enclosing scope activity for the invoke activity willnot be generated. Thus the invoke activity cannot be compensated.
- User Action: Set a compensation handler for the referenced invoke activity, or reference a different scope or invoke activity.
- CWWBW3405E: The referenced invoke activity ''{0}'' does not have a compensation handler or an undo action set (compensate activity ''{1}'').
- Explanation: The referenced invoke activity has no compensation handler or undo action set. Therefore, an enclosing scope activity for the invoke activity willnot be generated. Thus the invoke activity cannot be compensated.
- User Action: Set a compensation handler or an undo action for the referenced invoke activity, or reference a different scope or an invoke activity.
- CWWBW3406E: The activity name ''{0}'' must be unique (referenced in compensate activity ''{1}'').
- Explanation: The compensate activity references activities which have to be compensated. This reference is done by name. Thus it must be clear which activityis referenced. As a result the activity name must be unique.
- User Action: Ensure the activity name is used only once.
- CWWBW3600E: The link ''{0}'' cannot cross the boundary of the while loop activity ''{1}'' (link defined in the parallel activities activity ''{2}'').
- Explanation: A link crosses the boundary of a while loop activity. This means that the source activity is nested in a while loop activity and the target activity is not, or viceversa. These links are not allowed.
- User Action: Remove the link or define another source or target activity for the link.
- CWWBW3601E: The link ''{0}'' cannot be used in the while loop activity ''{1}'', because it is defined outside of the while loop activity (link defined in the parallel activities activity ''{2}'').
- Explanation: A link is used in a while loop activity, but it is defined outside of this activity. These links are not allowed.
- User Action: Remove the link or define another source or target activity for the link.
- CWWBW3602E: The link ''{0}'' cannot cross the boundary of the compensation handler of the scope activity ''{1}'' (link defined in the parallel activities activity ''{2}'').
- Explanation: A link crosses the boundary of a compensation handler. This means that the source activity is nested in acompensation handler and the target activity is not, or vice versa. These links are not allowed.
- User Action: Remove the link or define another source or target activity for the link.
- CWWBW3603E: The link ''{0}'' cannot be used in the compensation handler of the scope activity ''{1}'', because it is defined outside of thescope activity (link defined in the parallel activities activity ''{2}'').
- Explanation: A link is used in a compensation handler of a scope activity, but it is defined outside of the scope activity. These links are not allowed.
- User Action: Remove the link or define another source or target activity for the link.
- CWWBW3604E: The link ''{0}'' cannot cross the boundary of the compensation handler of the invoke activity ''{1}'' (link defined in the parallel activities activity ''{2}'').
- Explanation: A link crosses the boundary of a compensation handler. This means that the source activity is nested in acompensation handler and the target activity is not, or vice versa. These links are not allowed.
- User Action: Remove the link or define another source or target activity for the link.
- CWWBW3605E: The link ''{0}'' cannot be used in the compensation handler of the invoke activity ''{1}'', because it is defined outside of theinvoke activity (link defined in the parallel activities activity ''{2}'').
- Explanation: A link is used in the compensation handler of an invoke activity , but it is defined outside of the invoke activity. These links are not allowed.
- User Action: Remove the link or define another source or target activity for the link.
- CWWBW3606E: The link ''{0}'' cannot cross the boundary of the event handler of the scope activity ''{1}'' (link defined in the parallel activities activity ''{2}'').
- Explanation: A link crosses the boundary of an event handler. This means that the source activity is nested in an event handler and the target activity is not, or vice versa.These links are not allowed.
- User Action: Remove the link or define another source or target activity for the link.
- CWWBW3607E: The link ''{0}'' cannot be used in the event handler of the scope activity ''{1}'', because it is defined outside of the scope activity(link defined in the parallel activities activity ''{2}'').
- Explanation: A link is used in an event handler of a scope activity, but it is defined outside of the scope activity. These links are not allowed.
- User Action: Remove the link or define another source or target activity for the link.
- CWWBW3608E: The inbound link ''{0}'' cannot cross the boundary of the fault handler of the scope activity ''{1}'' (link defined in the parallel activities activity ''{2}'').
- Explanation: An inbound link crosses the boundary of a fault handler. This means that the source activity is nested in a fault handler and the target activity is not,or vice versa. These links are not allowed.
- User Action: Remove the link or define another source or target activity for the link.
- CWWBW3609E: The link ''{0}'' cannot be used in the fault handler of the scope activity ''{1}'', because it is defined outside of the scope activity(link defined in the parallel activities activity ''{2}'').
- Explanation: A link is used in a fault handler of a scope activity, but it is defined outside of the scope activity. These links are not allowed.
- User Action: Remove the link or define another source or target activity for the link.
- CWWBW3610E: The target of the link ''{0}'' cannot be nested in the scope activity ''{1}'', because the source of the link is nested in the fault handler of the scope activity(link defined in the parallel activities activity ''{2}'').
- Explanation: An outbound link crosses the boundary of a fault handler, but not the boundary of the scope activity of the fault handler.These links are not allowed.
- User Action: Remove the link or define another source or target activity for the link.
- CWWBW3611E: The inbound link ''{0}'' cannot cross the boundary of the fault handler of the invoke activity ''{1}'' (link defined in the parallel activities activity ''{2}'').
- Explanation: An inbound link crosses the boundary of a fault handler. These links are not allowed.
- User Action: Remove the link or define another source or target activity for the link.
- CWWBW3612E: The link ''{0}'' cannot be used in the fault handler of the invoke activity ''{1}'', because it is defined outside of the invoke activity(link defined in the parallel activities activity ''{2}'').
- Explanation: A link is used in a fault handler, but it is defined outside of the invoke activity that defines the fault handler.These links are not allowed.
- User Action: Remove the link or define another source or target activity for the link.
- CWWBW3613E: The link ''{0}'' cannot cross the boundary of two serializable scope activities (source scope activity ''{1}'', targetscope activity ''{2}'', link defined in the parallel activities activity ''{3}'').
- Explanation: A link points from one serializable scope activity to another serializable scope activity. These links are not allowed.
- User Action: Remove the link or define another source or target activity for the link.
- CWWBW3614E: The activity ''{0}'' cannot be part of a cycle.
- Explanation: The cycle prevents the process from ending.
- User Action: Remove the cycle.
- CWWBW3615E: The link ''{0}'' cannot be part of a cycle.
- Explanation: The cycle prevents the process from ending.
- User Action: Remove the cycle.
- CWWBW3616E: The source activity is missing for the link ''{0}'' (link defined in the parallel activities activity ''{1}'', target activity ''{2}'').
- Explanation: A link cannot be navigated because the source activity is not defined.
- User Action: Use the link in the source element of an activity.
- CWWBW3617E: The target activity is missing for the link ''{0}'' (link defined in the parallel activities activity ''{1}'', source activity ''{2}'').
- Explanation: A link cannot be navigated because the target activity is not defined.
- User Action: Use the link in the target element of an activity.
- CWWBW3618E: The link ''{0}'' is not used (link defined in the parallel activities activity ''{1}'').
- Explanation: All of the links defined in a parallel activities activity must be used to connect one source activity to one target activity.
- User Action: Remove the link or use it to connect two activities.
- CWWBW3619E: The link ''{0}'' has more than one source activity: ''{1}'' (link defined in the parallel activities activity ''{2}'').
- Explanation: Only one activity can be defined as the source of a link.
- User Action: Use only one activity from the list as the source of the link.
- CWWBW3620E: The link ''{0}'' has more than one target activity: ''{1}'' (link defined in the parallel activities activity ''{2}'').
- Explanation: Only one activity can be defined as the target of a link.
- User Action: Use only one activity from the list as the target of a link.
- CWWBW3700E: The partner ''{0}'' referenced in the undo action was not found (invoke activity ''{1}'').
- Explanation: The partner referenced in the undo action of the invoke activity is not defined.
- User Action: Ensure that the partner is correct and that it is defined.
- CWWBW3701E: The portType ''{0}'' referenced in the undo action was not found (invoke activity ''{1}'').
- Explanation: The portType referenced in the undo action of the invoke activity is not defined in the WSDL interface.
- User Action: Ensure that the portType is correct and that it is defined in the WSDL interface.
- CWWBW3702E: The operation ''{0}'' referenced in the undo action was not found (invoke activity ''{1}'').
- Explanation: The operation referenced in the undo action of the invoke activity is not defined in the WSDL interface.
- User Action: Ensure that the operation is correct and that it is defined in the WSDL interface.
- CWWBW3703E: The input element is not defined in the undo action operation ''{0}'' (invoke activity ''{1}'').
- Explanation: Operations that are used in this kind of activity must have an input element.
- User Action: Define an input element or use a different operation.
- CWWBW3704E: The messageType is not set in the input element of the undo action operation ''{0}'' (invoke activity ''{1}'').
- Explanation: The messageType must be set when the operation is used in this kind of activity.
- User Action: Set the messageType or use a different operation.
- CWWBW3705E: The messageType ''{0}'' that is referenced in the input element of the undo action operation ''{1}'' is not defined (invoke activity ''{2}'').
- Explanation: The messageType must be defined when the operation is used in this kind of activity.
- User Action: Set the messageType or use a different operation.
- CWWBW3706E: The messageType of the variable ''{0}'' and the input element of the undo action operation ''{1}'' must be the same (invoke activity ''{2}'').
- Explanation: The messageType of the variable and the input element of the operation must be the same.
- User Action: Ensure that the variable and the input element have the same messageType.
- CWWBW3707E: The undo action variable ''{0}'' is not defined (invoke activity ''{1}'').
- Explanation: The variable used in the undo action of the invoke activity is not defined.
- User Action: Check that the variable name is defined correctly.
- CWWBW3708E: The XSD-typed variable cannot be used in the undo action (invoke activity ''{0}'', variable ''{1}'').
- Explanation: For this activity, only WSDL-typed variables are allowed.
- User Action: Use a WSDL-typed variable.
- CWWBW3709E: The variable ''{0}'' cannot be used in the undo action, because the variable messageType uses part-level messages (invoke activity ''{1}'',messageType ''{2}'').
- Explanation: A variable that uses a messageType with one or more parts that reference message types can be used only as an input variable in invoke or transformactivities, and in Java snippets.
- User Action: Use a different variable in this activity.
- CWWBW3710E: An expiration element cannot be set for the undo action (invoke activity ''{0}'').
- Explanation: An expiration element cannot be set for an undo action.
- User Action: Remove the expiration element.
- CWWBW3711E: The undo action partner ''{0}'' does not define the partnerRole role (invoke activity ''{1}'').
- Explanation: Partners used in invoke activities must define the partnerRole role.
- User Action: Define the partnerRole role for the partner or use a different partner.
- CWWBW3712E: The portType attribute referenced in the undo action of the invoke activity ''{0}'' and in the partnerRole role ''{1}'' must be the same (partner ''{2}'', partnerLinkType ''{3}'').
- Explanation: The portType attribute in the undo action is optional. When this attribute is set, it must be the same as the portType attribute set in thepartnerRole role in the partner.
- User Action: Ensure that the portType attributes are the same.
- CWWBW3713E: The partner ''{0}'' does not define the partnerRole role (invoke activity ''{1}'').
- Explanation: Partners used in invoke activities must define the partnerRole role.
- User Action: Define the partnerRole role for the partner or use a different partner.
- CWWBW3714E: The inputVariable attribute of the undo action must not be set because an undo action inputelement is available (invoke activity ''{0}'', undo action inputVariable ''{1}'').
- Explanation: The data that is sent by this undo action can be identified by the inputVariable attribute, which must be message-typed, or by one or more XSD-typedvariables specified in the input element.
- User Action: Remove the inputVariable attribute from the undo action.
- CWWBW3715E: The variable ''{0}'' used in the undo action is not defined (input element of the undo action of invoke activity ''{1}'', parameter {2}).
- Explanation: The variable used in the parameter extension is not defined.
- User Action: Check that the variable name is defined correctly.
- CWWBW3716E: The message-typed variable cannot be used here (input element of the undo action of invoke activity ''{0}'', parameter {1}, variable ''{2}'').
- Explanation: You can use only element-typed or type-typed variables in input elements.
- User Action: Use an XSD-typed variable.
- CWWBW3717E: The variable ''{0}'' cannot be used multiple times in the same input element (input element of the undo action of invoke activity ''{1}'',parameter {2}).
- Explanation: A variable can be used only once in an input element.
- User Action: Use another XSD-typed variable.
- CWWBW3718E: The invoke activity cannot contain both a compensation handler and an undo action (invoke activity ''{0}'').
- Explanation: For compensation, either a compensation handler or an undo action can be used.
- User Action: Remove either the compensation handler or the undo action.
- CWWBW3719E: The undo action does not specify a variable and the invoke activity specifies the variable by using the parameter extension. This combination is not allowed(invoke activity ''{0}'').
- Explanation: The variable in the undo action is optional only when the invoke activity references a message-typed variable.
- User Action: Specify a variable for the undo action.
- CWWBW3720E: The parameter-extension cannot be used for the message ''{0}'' (undo action of invoke activity ''{1}'').
- Explanation: The input message of the used operation in the undo action cannot be used together with the parameter-extension. For example, the message contains an array, whichcannot be mapped to data-typed variables in the process.
- User Action: Either modify the message to be used with the parameter extension or use a message-type variable.
- CWWBW3721E: The parameter ''{0}'' is not mapped to an element or part (undo action of invoke activity ''{1}'', parameter {2}).
- Explanation: A parameter have been found which does not map to an element in the wrapper or to a part in the message.
- User Action: Remove the parameter or map it to a valid element or part.
- CWWBW3722E: The XSD type definition ''{0}'' was not found (undo action of invoke activity ''{1}'', parameter {2}, matching part or element ''{3}'').
- Explanation: The XSD type definition referenced in the matching part or element must be either a valid built-in XML schema simple type or it must be defined in-line in a WSDLinterface or in an XML schema.
- User Action: Check that the XSD type definition is correctly referenced and that it is defined correctly.
- CWWBW3723E: The XSD element declaration ''{0}'' was not found (undo action of invoke activity ''{1}'', parameter {2}, matching part or element ''{3}'').
- Explanation: The XSD element declaration referenced in the matching part or element must be either defined in-line in a WSDL interface or in an XML schema.
- User Action: Check that the XSD element declaration is correctly referenced and that it is defined correctly.
- CWWBW3724E: The variable ''{0}'' cannot be assigned to element or part ''{1}'' because the data type does not match (undo action of invoke activity ''{2}'', parameter {3}).
- Explanation: The selected element and the variable are of incompatible types. Only compatible types can be assigned, for example from xsd:string to xsd:string.
- User Action: Ensure the types are compatible.
- CWWBW3725E: The XSD element ''{0}'' is not mapped to a parameter (undo action of invoke activity ''{1}'').
- Explanation: An element have been found in the wrapper which does not map to a parameter.
- User Action: Remove the element or map it to a parameter.
- CWWBW3726E: The message-part ''{0}'' is not mapped to a parameter (undo action of invoke activity ''{1}'').
- Explanation: A message-part have been found in the wrapper which does not map to a parameter.
- User Action: Remove the message-part or map it to a parameter.
- CWWBW3800E: The XSD-typed variable cannot be used here (receive choice activity ''{0}'', receive element {1}, variable ''{2}'').
- Explanation: Only WSDL-typed variables are allowed for receive choice activities.
- User Action: Use a WSDL-typed variable.
- CWWBW3801E: The partner ''{0}'' was not found (receive choice activity ''{1}'', receive element {2}).
- Explanation: The partner referenced in the activity is not defined.
- User Action: Ensure that the partner is correct and that it is defined.
- CWWBW3802E: The partner ''{0}'' does not define the myRole role (receive choice activity ''{1}'', receive element {2}).
- Explanation: Partners used in receive elements of a receive choice activity must define the myRole role.
- User Action: Define the myRole role for the partner or use a different partner.
- CWWBW3803E: The portType ''{0}'' was not found (receive choice activity ''{1}'', receive element {2}).
- Explanation: The portType referenced in the activity is not defined in the WSDL interface.
- User Action: Ensure that the portType is correct and that it is defined in the WSDL interface.
- CWWBW3804E: The portType referenced in the receive choice activity ''{0}'' and in the myRole role ''{1}'' must be the same (receive element {2}, partner ''{3}'',partnerLinkType ''{4}'').
- Explanation: The portType attribute in the receive element is optional. If this attribute is set, it must be the same as portType set in the myRole role in the partner.
- User Action: Ensure the port types are the same.
- CWWBW3805E: The operation ''{0}'' was not found (receive choice activity ''{1}'', receive element {2}).
- Explanation: The operation referenced in the activity is not defined in the WSDL interface.
- User Action: Ensure that the operation is correct and that it is defined in the WSDL interface.
- CWWBW3806E: The input element is not defined in the operation ''{0}'' (receive choice activity ''{1}'', receive element {2}).
- Explanation: Operations used in this kind of activity must have an input element.
- User Action: Define an input element or use a different operation.
- CWWBW3807E: The messageType is not set in the input element of the operation ''{0}'' (receive choice activity ''{1}'', receive element {2}).
- Explanation: The input messageType must be set when the operation is used in an receive element of a receive choice activity.
- User Action: Set the input messageType or use a different operation.
- CWWBW3808E: The messageType ''{0}'' referenced in the operation ''{1}'' was not found (receive choice activity ''{2}'', receive element {3}).
- Explanation: The messageType referenced must be defined when the operation is used in an receive element of a receive choice activity.
- User Action: Set the messageType or use a different operation.
- CWWBW3809E: The messageType of the variable ''{0}'' and of the input element of operation ''{1}'' must be the same (receive choice activity ''{2}'', receive element {3}).
- Explanation: The messageType of the variable and of the input element of the operation must be the same.
- User Action: Ensure that the messageType of the variable and the input operation are the same.
- CWWBW3810E: The variable is not set (receive choice activity ''{0}'', receive element {1}).
- Explanation: A mandatory variable for the receive choice activity is not defined.
- User Action: Define the mandatory variable.
- CWWBW3811E: The variable ''{0}'' is not defined (receive choice activity ''{1}'', receive element {2}).
- Explanation: The variable used in the receive choice activity is not defined.
- User Action: Check that the variable name is defined correctly.
- CWWBW3812E: The correlation set ''{0}'' was not found (receive choice activity ''{1}'', receive element {2}).
- Explanation: The correlation set used in the receive choice activity is not defined.
- User Action: Define the correlation set, or remove it from the receive element of the receive choice activity.
- CWWBW3813E: A matching propertyAlias definition was not found for the property ''{0}'' and messageType ''{1}'' (receive choice activity ''{2}'', receive element {3}, correlation set ''{4}'').
- Explanation: A propertyAlias definition is needed to map the parts of a messageType to the correlation properties.
- User Action: Define the propertyAlias.
- CWWBW3814E: The part ''{0}'' referenced in the propertyAlias for the property ''{1}'' and the messageType ''{2}'' was not found (receive choice activity ''{3}'', receive element {4},correlation set ''{5}'').
- Explanation: The part must be defined for the messageType.
- User Action: Define the part, or use an existing part in the propertyAlias.
- CWWBW3815E: The part ''{0}'' referenced in the propertyAlias for the property ''{1}'' and the messageType ''{2}'' does not reference a valid XML schema simple type(receive choice activity ''{3}'', receive element {4}, correlation set ''{5}'').
- Explanation: The selected part of the messageType must be an XML schema simple type because a property can have only XML schema simple types.
- User Action: Select a part that has an XML schema simple type.
- CWWBW3816E: The type of the part ''{0}'' of the messageType ''{1}'' and the property ''{2}'' is not the same (receive choice activity ''{3}'', receive element {4}, correlation set ''{5}'').
- Explanation: The selected part of the messageType in the propertyAlias does not have the same type as the property type.
- User Action: Select a part that has same XML schema simple type as the property type.
- CWWBW3817E: Multiple propertyAlias definitions were found for the property ''{0}'' and the messageType ''{1}'' (receive choice activity ''{2}'', receive element {3}, correlation set ''{4}'').
- Explanation: Every property-messageType pair can have only one propertyAlias definition.
- User Action: Ensure only one propertyAlias is available for the property-messageType pair. If more than one part of a messageType is needed as a property,create properties and propertyAlias definitions for additional parts of the same messageType.
- CWWBW3818E: The receive element {0} does not use a correlation set (receive choice activity ''{1}'').
- Explanation: If more than one receive choice or receive activity is used in a process model, all of the receive elements of a receive choice activity must use at least one correlation set.The correlation set ensures that the input messages can correlate with the process instance.
- User Action: Set at least one correlation set for the receive element.
- CWWBW3819E: A wrong set of correlation sets is used in the receive element {0} of the receive choice activity ''{1}''. The expected set of correlation sets, as used in the activity ''{2}'', is: ''{3}''.
- Explanation: All of the receive choice or receive activities that create process instances must use the same set of correlation sets.
- User Action: Ensure that all of the receive and receive choice activities that create process instances use the same set of correlation sets.
- CWWBW3820E: The variable ''{0}'' cannot be used here, because the variable messageType uses part-level messages (receive choice activity ''{1}'', receive element {2},messageType ''{3}'').
- Explanation: A variable that uses a messageType with one or more parts that reference message types can be used only as an input variable in invoke or transformactivities and in Java snippets.
- User Action: Use a different variable in this receive choice activity.
- CWWBW3821E: The receive choice activity ''{0}'' can create process instances but it has timeout events.
- Explanation: If the receive choice activity creates process instances, timeout events are not allowed.
- User Action: Remove the timeout events or redefine the receive choice activity so that it does not create process instances.
- CWWBW3822E: A reply activity was not found that matches the receive element {0} of the receive choice activity ''{1}''.
- Explanation: For each two-way operation receive element in a receive choice activity, the process must contain at least one reply activity with the same port type and operation.
- User Action: Add a reply activity to the process with the same port type and operation as the receive element of the receive choice activity.
- CWWBW3823E: The variable must not be set because an output element is available (receive choice activity ''{0}'', receive element {1}, variable ''{2}'').
- Explanation: The data that is received by this receive element can be stored in the activity variable, which must be message-typed, or in one or more XSD-typedvariables specified in the output element.
- User Action: Remove the variable attribute from the receive element.
- CWWBW3824E: The variable ''{0}'' is not defined (receive choice activity ''{1}'', output element of receive element {2}, parameter {3}).
- Explanation: The variable used in the parameter extension is not defined.
- User Action: Check that the variable name is defined correctly.
- CWWBW3825E: The message-typed variable cannot be used here (receive choice activity ''{0}'', output element of receive element {1}, parameter {2}, variable ''{3}'').
- Explanation: You can use only element-typed or type-typed variables in output elements.
- User Action: Use an XSD-typed variable.
- CWWBW3826E: The variable ''{0}'' cannot be used multiple times in the same output element (receive choice activity ''{1}'', output element of receive element {2}, parameter {3}).
- Explanation: A variable can be used only once in an output element.
- User Action: Use another XSD-typed variable.
- CWWBW3827E: The referenced human task ''{0}'' cannot be found (receive choice activity ''{1}'', receive element {2}).
- Explanation: The human task that is referenced in the receive element cannot be found.
- User Action: Remove the human task reference or ensure that the human task can be found.
- CWWBW3828E: The referenced human task ''{0}'' is not an originating task (receive choice activity ''{1}'', receive element {2}).
- Explanation: The human task that is referenced in the receive element must be an originating task.
- User Action: Reference an originating task.
- CWWBW3829E: The portType that is referenced in the receive element {0} and in the referenced human task ''{1}'' must be the same (receive choice activity ''{2}'').
- Explanation: The portTypes must be the same.
- User Action: Ensure that the portTypes are the same.
- CWWBW3830E: The operation that is referenced in the receive element {0} and in the referenced human task ''{1}'' must be the same (receive choice activity ''{2}'').
- Explanation: The operations must be the same.
- User Action: Ensure that the operations are the same.
- CWWBW3831E: The part is not set in the propertyAlias for the property ''{0}'' and the messageType ''{1}'' (receive choice activity ''{2}'', receive element {3},correlation set ''{4}'').
- Explanation: The part must be set in the propertyAlias.
- User Action: Set the part.
- CWWBW3832E: The query language ''{0}'' used in the propertyAlias is not supported. It must be one of ''{1}'' (receive choice activity ''{2}'', receive element {3},correlation set ''{4}'', propertyAlias for the property ''{5}'' and the messageType ''{6}'').
- Explanation: The specified query language is unknown. Queries specified in this query language cannot be run.
- User Action: Use one of the supported query languages.
- CWWBW3833E: The timeout event must specify at least a for expression, or an until expression (receive choice activity ''{0}'', timeout event {1}).
- Explanation: The for element defines the duration expression after which the event is signaled. The until element specifies when the alarm event isfired. One of these two expressions must occur in an timeout event.
- User Action: Specify a for expression, or an until expression.
- CWWBW3834E: The timeout event must specify at least a for expression, an until expression, or a timeout expression (receive choice activity ''{0}'', timeout event {1}).
- Explanation: The for element defines the duration expression after which the event is signaled. The until element specifies when the alarm event is fired.The timeout element specifies a timeout using a calendar supplied by the WebSphereApplication Server scheduling service, or user-written calendars adhering to thoseconventions. One of these three expressions must occur in an timeout event.
- User Action: Specify a for expression, an until expression, or a timeout expression.
- CWWBW3835E: The timeout event cannot specify a for expression and a timeout expression, or an until expression and a timeout expression(receive choice activity ''{0}'', timeout event {1}).
- Explanation: The for element defines the duration expression after which the event is signaled. The until element specifies when the alarm event is fired.The timeout element specifies a timeout using a calendar supplied by the WebSphereApplication Server scheduling service, or user-written calendars adhering to thoseconventions. One of these three expressions must occur in an timeout event.
- User Action: Specify a for expression, an until expression, or a timeout expression.
- CWWBW3836E: The repeatEvery expression is not allowed in receive choice activities (receive choice activity ''{0}'', timeout event {1}).
- Explanation: Syntactically the repeatEvery expression is allowed in receive choice activities, however, this expression is only useful in event handlers.
- User Action: Use the for expression instead.
- CWWBW3837E: The receive element {0} implements operation ''{1}'' of portType ''{2}'', which is already implemented in another receive element (receive choice activity ''{3}'').
- Explanation: The same portType and operation can be implemented only once in the same receive choice activity. In case a message is received for a specific portType and operationthe executing engine must know which receive element in that instance of the process have to beexecuted.
- User Action: Remove the receive element or change the operation.
- CWWBW3838E: The parameter-extension cannot be used for the message ''{0}'' (receive choice activity ''{1}'', receive element {2}).
- Explanation: The input message of the used operation of the receive element cannot be used together with the parameter-extension. For example, the message contains an array, whichcannot be mapped to data-typed variables in the process.
- User Action: Either modify the message to be used with the parameter extension or use a message-type variable.
- CWWBW3839E: The parameter ''{0}'' is not mapped to an element or part (receive choice activity ''{1}'', receive element {2}, parameter {3}).
- Explanation: A parameter have been found which does not map to an element in the wrapper or to a part in the message.
- User Action: Remove the parameter or map it to a valid element or part.
- CWWBW3840E: The XSD type definition ''{0}'' was not found (receive choice activity ''{1}'', receive element {2}, parameter {3}, matching part or element ''{4}'').
- Explanation: The XSD type definition referenced in the matching part or element must be either a valid built-in XML schema simple type or it must be defined in-line in a WSDLinterface or in an XML schema.
- User Action: Check that the XSD type definition is correctly referenced and that it is defined correctly.
- CWWBW3841E: The XSD element declaration ''{0}'' was not found (receive choice activity ''{1}'', receive element {2}, parameter {3}, matching part or element ''{4}'').
- Explanation: The XSD element declaration referenced in the matching part or element must be either defined in-line in a WSDL interface or in an XML schema.
- User Action: Check that the XSD element declaration is correctly referenced and that it is defined correctly.
- CWWBW3842E: The element or part ''{0}'' cannot be assigned to variable ''{1}'' because the data type does not match (receive choice activity ''{2}'', receive element {3}, parameter {4}).
- Explanation: The selected element and the variable are of incompatible types. Only compatible types can be assigned, for example from xsd:string to xsd:string.
- User Action: Ensure the types are compatible.
- CWWBW3843E: The XSD element ''{0}'' is not mapped to a parameter (receive choice activity ''{1}'', receive element {2}).
- Explanation: An element have been found in the wrapper which does not map to a parameter.
- User Action: Remove the element or map it to a parameter.
- CWWBW3844E: The message-part ''{0}'' is not mapped to a parameter (receive choice activity ''{1}'', receive element {2}).
- Explanation: A message-part have been found in the wrapper which does not map to a parameter.
- User Action: Remove the message-part or map it to a parameter.
- CWWBW3845E: The correlation set ''{0}'' is used already (receive choice activity ''{1}'', receive element {2}).
- Explanation: The correlation set can be used only once per receive element.
- User Action: Ensure the correlation set is used only once in the given receive element.
- CWWBW3900E: The receive activity ''{0}'' does not use a correlation set.
- Explanation: If more than one receive choice or receive activity is used in a process model, all of the receive activities must use at least one correlation set. The correlationset ensures that the input messages can correlate with the process instance.
- User Action: Set at least one correlation set for the receive activity.
- CWWBW3901E: A wrong set of correlation sets is used in the receive activity ''{0}''. The expected set of correlation sets, as used in activity ''{1}'', is: ''{2}''.
- Explanation: All of the receive choice or receive activities that create process instances must use the same set of correlation sets.
- User Action: Ensure that all of the receive and receive choice activities that create process instances use the same set of correlation sets.
- CWWBW3902E: A reply activity was not found that matches the receive activity ''{0}''.
- Explanation: For each two-way operation receive activity, the process must contain at least one reply activity with the same port type and operation.
- User Action: Add a reply activity to the process with the same port type and operation as the receive activity.
- CWWBW3903E: The variable must not be set because an output element is available (receive activity ''{0}'', variable ''{1}'').
- Explanation: The data that is received by this receive activity can be stored in the activity variable, which must be message-typed, or in one or more XSD-typedvariables specified in the output element.
- User Action: Remove the variable attribute from the receive activity.
- CWWBW3904E: The referenced human task ''{0}'' is not an originating task (receive activity ''{1}'').
- Explanation: The human task that is referenced in the receive activity must be an originating task.
- User Action: Reference an originating task.
- CWWBW4000E: The fault ''{0}'' was not found in the operation ''{1}'' (activity ''{2}'').
- Explanation: The fault used in the activity is not defined.
- User Action: Check that the fault name is correct and that it is defined.
- CWWBW4001E: The process is triggered by a one-way operation, but it contains the reply activity ''{0}''.
- Explanation: A process that is triggered by a one-way operation invocation must not have a reply activity.
- User Action: Remove the reply activity.
- CWWBW4002E: No receive choice activity, receive activity, or onEvent event found to match the reply activity ''{0}''.
- Explanation: For each two-way operation reply activity, the process must contain at least one receive choice activity, receive activity, or onEvent event with the same porttype and operation.
- User Action: Add a receive choice activity, receive activity, or onEvent event to the process with the same port type and operation type as the reply activity.
- CWWBW4003E: The variable must not be set because an input element is available (reply activity ''{0}'', variable ''{1}'').
- Explanation: The data that is sent by this reply activity can be identified by the variable, which must be message-typed, or by one or more XSD-typedvariables specified in the input element.
- User Action: Remove the variable attribute from the reply activity.
- CWWBW4100E: The rethrow activity ''{0}'' cannot be used outside of a fault handler.
- Explanation: With a rethrow activity, the faults caught in a fault handler can be rethrown. Therefore, rethrow activities can be used only inside a fault handler.
- User Action: Move the rethrow activity to a fault handler or remove it.
- CWWBW4200E: The serializable scope activity ''{0}'' must not be nested in the serializable scope activity ''{1}''.
- Explanation: A serializable scope activity must not contain other serializable scope activities.
- User Action: Set the isolated attribute on one of the scope activities to 'no'.
- CWWBW4201E: There are too many variable type definitions set for the scope variable ''{0}'' (scope activity ''{1}'', messageType ''{2}'', type ''{3}'', element ''{4}'').
- Explanation: The messageType, type, or element attributes are used to specify the type of a variable. Exactly one of them must be set.
- User Action: Ensure that there is only one variable type definition set for the scope variable.
- CWWBW4202E: The scope variable ''{0}'' must have a variable type definition (scope activity ''{1}'').
- Explanation: The messageType, type, or element attributes are used to specify the type of a variable. Exactly one of them must be set.
- User Action: Provide a variable type definition for the variable.
- CWWBW4203E: The messageType definition ''{0}'' was not found (scope activity ''{1}'', scope variable ''{2}'').
- Explanation: The messageType definition referenced in the scope variable must be defined in a WSDL interface.
- User Action: Check that the messageType definition is referenced correctly and that it is defined correctly in an accessible WSDL interface.
- CWWBW4204E: The XSD type definition ''{0}'' was not found (scope activity ''{1}'', scope variable ''{2}'').
- Explanation: The XSD type definition referenced in the scope variable must be a valid built-in XML schema simple type, or it must be definedin a WSDL interface or in an XML schema.
- User Action: Check that the XSD type definition is referenced correctly and that it is defined correctly.
- CWWBW4205E: The XSD element declaration ''{0}'' was not found (scope activity ''{1}'', scope variable ''{2}'').
- Explanation: The XSD element declaration referenced in the scope variable must be either defined in a WSDL interface or in an XML schema.
- User Action: Check that the XSD element declaration is referenced correctly and that it is defined correctly.
- CWWBW4206E: The scope variable name ''{0}'' is already used (scope activity ''{1}'').
- Explanation: The name of a variable must be unique in its own scope.
- User Action: Use a different variable name.
- CWWBW4207E: The event handler of the scope activity must contain an onEvent event or an timeout event (scope activity ''{0}'').
- Explanation: An event handler must have at least one onEvent event or one timeout event.
- User Action: Define an onEvent event or an timeout event, or remove the event handler.
- CWWBW4208E: The partner ''{0}'' was not found (scope activity ''{1}'', onEvent event {2}).
- Explanation: The partner referenced in the onEvent event is not defined.
- User Action: Ensure that the partner is correct and that it is defined.
- CWWBW4209E: The partner ''{0}'' does not define the myRole role (scope activity ''{1}'', onEvent event {2}).
- Explanation: Partners used in onEvent events must define the myRole role.
- User Action: Define the myRole role for the partner or use a different partner.
- CWWBW4210E: The portType ''{0}'' was not found (scope activity ''{1}'', onEvent event {2}).
- Explanation: The portType referenced in the onEvent event is not defined in the WSDL interface.
- User Action: Ensure that the portType used is correct and that it is defined in the WSDL interface.
- CWWBW4211E: The portType referenced in the onEvent event {0} and in myRole role ''{1}'' must be the same (scope activity ''{2}'', partner ''{3}'', partnerLinkType ''{4}'').
- Explanation: The portType attribute in the onEvent event is optional. When this attribute is set, it must be the same as the portType set in the myRole role in the partner.
- User Action: Ensure that the port types are the same.
- CWWBW4212E: The operation ''{0}'' was not found (scope activity ''{1}'', onEvent event {2}).
- Explanation: The operation referenced in the onEvent event is not defined in the WSDL interface.
- User Action: Ensure that the operation used is correct and that it is defined in the WSDL interface.
- CWWBW4213E: The input element is not defined in the operation ''{0}'' (scope activity ''{1}'', onEvent event {2}).
- Explanation: The operation referenced in the onEvent event must have an input element.
- User Action: Define an input element or use a different operation.
- CWWBW4214E: The messageType is not set in the input element of the operation ''{0}'' (scope activity ''{1}'', onEvent event {2}).
- Explanation: The input messageType must be set if the operation is used in this onEvent event.
- User Action: Set the input messageType or use a different operation.
- CWWBW4215E: The messageType ''{0}'' referenced in the operation ''{1}'' was not found (scope activity ''{2}'', onEvent event {3}).
- Explanation: The messageType referenced must be defined if the operation is used in this onEvent event.
- User Action: Set the messageType or use a different operation.
- CWWBW4216E: The messageType of the variable ''{0}'' and the messageType of the input element of the operation ''{1}'' must be the same (scope activity ''{2}'', onEvent event {3}).
- Explanation: The messageType of the variable and the of the input element of the operation must be the same.
- User Action: Ensure that the variable and the input element have the same messageType.
- CWWBW4217E: The variable is not set (scope activity ''{0}'', onEvent event {1}).
- Explanation: A mandatory variable for the onEvent event is not defined.
- User Action: Define the mandatory variable.
- CWWBW4218E: The messageType is not set (scope activity ''{0}'', onEvent event {1}).
- Explanation: A mandatory messageType for the onEvent event is not defined.
- User Action: Define the mandatory messageType.
- CWWBW4219E: The messageType ''{0}'' was not found (scope activity ''{1}'', onEvent event {2}).
- Explanation: The messageType referenced in the onEvent event is not defined in the WSDL interface.
- User Action: Check that the messageType is defined correctly in the WSDL interface.
- CWWBW4220E: The correlation set ''{0}'' was not found (scope activity ''{1}'', onEvent event {2}).
- Explanation: The correlation set used in the onEvent event is not defined.
- User Action: Define the correlation set, or remove it from the onEvent event.
- CWWBW4221E: The variable must not be set because an output element is available (scope activity ''{0}'', onEvent event {1}, variable ''{2}'').
- Explanation: The data that is received by this onEvent event can be stored in the onEvent variable, which must be message-typed, or in one or more XSD-typedvariables specified in the output element.
- User Action: Remove the variable attribute from the onEvent event.
- CWWBW4222E: The scope activity has a compensation handler, but the compensable attribute of the scope activity is set to ''no'' (scope activity ''{0}'').
- Explanation: If the compensable attribute of a scope activity is set to 'no', the scope activity cannot be compensated. Thus, it cannot have a compensation handler.
- User Action: Remove the compensation handler, or set the compensable attribute to 'yes'.
- CWWBW4223E: The parameter-extension cannot be used for the message ''{0}'' (scope activity ''{1}'', onEvent event {2}).
- Explanation: The input message of the used operation in the onEvent event cannot be used together with the parameter-extension. For example, the message contains an array, whichcannot be mapped to data-typed variables in the process.
- User Action: Either modify the message to be used with the parameter extension or use a message-type variable.
- CWWBW4224E: The parameter ''{0}'' is not mapped to an element or part (scope activity ''{1}'', onEvent event {2}, parameter {3}).
- Explanation: A parameter have been found which does not map to an element in the wrapper or to a part in the message.
- User Action: Remove the parameter or map it to a valid element or part.
- CWWBW4225E: The variable name ''{0}'' is used already in the same onEvent event (scope activity ''{1}'', output element of onEvent event {2}, parameter {3}).
- Explanation: A variable name can be used only once in an output element.
- User Action: Use another variable name.
- CWWBW4226E: A matching propertyAlias definition was not found for the property ''{0}'' and messageType ''{1}'' (scope activity ''{2}'', onEvent event {3},correlation set ''{4}'').
- Explanation: A propertyAlias definition is needed to map the parts of a messageType to the correlation properties.
- User Action: Define the propertyAlias.
- CWWBW4227E: The part ''{0}'' that is referenced in the propertyAlias for the property ''{1}'' and the messageType ''{2}'' was not found (scope activity ''{3}'',onEvent event {4}, correlation set ''{5}'').
- Explanation: The part must be defined for the messageType.
- User Action: Define the part, or use an existing part in the propertyAlias.
- CWWBW4228E: The part ''{0}'' that is referenced in the propertyAlias for the property ''{1}'' and the messageType ''{2}'' does not reference a valid XMLschema simple type (scope activity ''{3}'', onEvent event {4}, correlation set ''{5}'').
- Explanation: The selected part of the messageType must be an XML schema simple type because a property can only have XML schema simple types.
- User Action: Select a part that has an XML schema simple type.
- CWWBW4229E: The type of the part ''{0}'' of the messageType ''{1}'' and the type of the property ''{2}'' are not the same (scope activity ''{3}'', onEvent event {4},correlation set ''{5}'').
- Explanation: The selected part of the messageType in the propertyAlias does not have the same type as the property type.
- User Action: Select a part that has same XML schema simple type as the property type.
- CWWBW4230E: Multiple propertyAlias definitions were found for the property ''{0}'' and the messageType ''{1}'' (scope activity ''{2}'', onEvent event {3},correlation set ''{4}'').
- Explanation: A property-messageType pair can have only one propertyAlias definition.
- User Action: Ensure that only one propertyAlias is available for the property-messageType pair. If you need more than one part of a messageType as a property,create properties and propertyAlias definitions for the additional parts of the same messageType.
- CWWBW4231E: The referenced human task ''{0}'' cannot be found (scope activity ''{1}'', onEvent event {2}).
- Explanation: The human task that is referenced in the scope activity onEvent event cannot be found.
- User Action: Remove the human task reference or ensure that the human task can be found.
- CWWBW4232E: The referenced human task ''{0}'' is not an originating task (scope activity ''{1}'', onEvent event {2}).
- Explanation: The human task referenced in the scope activity onEvent event must be an originating task.
- User Action: Reference an originating task.
- CWWBW4233E: The portType referenced in the onEvent event {0} and in the referenced human task ''{1}'' must be the same (scope activity ''{2}'').
- Explanation: The portTypes must be the same.
- User Action: Ensure that the portTypes are the same.
- CWWBW4234E: The operation that is referenced in the onEvent event {0} and in the referenced human task ''{1}'' must be the same (scope activity ''{2}'').
- Explanation: The operations must be the same.
- User Action: Ensure that the operations are the same.
- CWWBW4235E: The part is not set in the propertyAlias for the property ''{0}'' and the messageType ''{1}'' (scope activity ''{2}'',onEvent event {3}, correlation set ''{4}'').
- Explanation: The part must be set in the propertyAlias.
- User Action: Set the part.
- CWWBW4236E: The query language ''{0}'' used in the propertyAlias is not supported. It must be one of ''{1}'' (scope activity ''{2}'', onEvent event {3},correlation set ''{4}'', propertyAlias for the property ''{5}'' and the messageType ''{6}'').
- Explanation: The specified query language is unknown. Queries specified in this query language cannot be run.
- User Action: Use one of the supported query languages.
- CWWBW4237E: A reply activity was not found that matches the onEvent event {0} of the scope activity ''{1}''.
- Explanation: For each two-way operation onEvent event in a scope activity, the process must contain at least one reply activity with the same port type and operation.
- User Action: Add a reply activity to the process with the same port type and operation as the onEvent event of the scope activity.
- CWWBW4238E: The expression is not valid (scope activity ''{0}'', timeout event {1}, expression language ''{2}'').
- Explanation: The specified expression is not a valid expression for the given expression language.
- User Action: Check the expression and the expression language.
- CWWBW4239E: There are too many variable type definitions set for the variable ''{0}'' (scope activity ''{1}'', onEvent event {2}, parameter {3}, type ''{4}'', element ''{5}'').
- Explanation: The type, or element attributes define the type of a variable. Exactly one of these attributes must be set.
- User Action: Ensure that there is only one variable type definition set for the variable.
- CWWBW4240E: The XSD element declaration ''{0}'' was not found (scope activity ''{1}'', onEvent event {2}, parameter {3}, variable ''{4}'').
- Explanation: The XSD element declaration referenced in the variable must be either defined in-line in a WSDL interface or in an XML schema.
- User Action: Check that the XSD element declaration is correctly referenced and that it is defined correctly.
- CWWBW4241E: The XSD type definition ''{0}'' was not found (scope activity ''{1}'', onEvent event {2}, parameter {3}, variable ''{4}'').
- Explanation: The XSD type definition referenced in the variable must be either a valid built-in XML schema simple type or it must be defined in-line in a WSDLinterface or in an XML schema.
- User Action: Check that the XSD type definition is correctly referenced and that it is defined correctly.
- CWWBW4242E: The variable ''{0}'' must have a variable type definition (scope activity ''{1}'', onEvent event {2}, parameter {3}).
- Explanation: The type, or element attributes are used to specify the type of a variable. Exactly one of these attributes must be set.
- User Action: Provide a variable type definition for the variable.
- CWWBW4243E: The XSD type definition ''{0}'' was not found (scope activity ''{1}'', onEvent event {2}, parameter {3}, matching part or element ''{4}'').
- Explanation: The XSD type definition referenced in the matching part or element must be either a valid built-in XML schema simple type or it must be defined in-line in a WSDLinterface or in an XML schema.
- User Action: Check that the XSD type definition is correctly referenced and that it is defined correctly.
- CWWBW4244E: The XSD element declaration ''{0}'' was not found (scope activity ''{1}'', onEvent event {2}, parameter {3}, matching part or element ''{4}'').
- Explanation: The XSD element declaration referenced in the matching part or element must be either defined in-line in a WSDL interface or in an XML schema.
- User Action: Check that the XSD element declaration is correctly referenced and that it is defined correctly.
- CWWBW4245E: The element ''{0}'' cannot be assigned to variable ''{1}'' because the data type does not match (scope activity ''{2}'', onEvent event {3}, parameter {4}).
- Explanation: The selected element and the variable are of incompatible types. Only compatible types can be assigned, for example from xsd:string to xsd:string.
- User Action: Ensure the types are compatible.
- CWWBW4246E: The part ''{0}'' cannot be assigned to variable ''{1}'' because the data type does not match (scope activity ''{2}'', onEvent event {3}, parameter {4}).
- Explanation: The selected message-part and the variable are of incompatible types. Only compatible types can be assigned, for example from xsd:int to xsd:int.
- User Action: Ensure the types are compatible.
- CWWBW4247E: The XSD element ''{0}'' is not mapped to a parameter (scope activity ''{1}'', onEvent event {2}).
- Explanation: An element have been found in the wrapper which does not map to a parameter.
- User Action: Remove the element or map it to a parameter.
- CWWBW4248E: The message-part ''{0}'' is not mapped to a parameter (scope activity ''{1}'', onEvent event {2}).
- Explanation: A message-part have been found in the wrapper which does not map to a parameter.
- User Action: Remove the message-part or map it to a parameter.
- CWWBW4249E: The correlation set ''{0}'' is used already (scope activity ''{1}'', onEvent event {2}).
- Explanation: The correlation set can be used only once per event.
- User Action: Ensure the correlation set is used only once in the given event.
- CWWBW4400E: The expression language ''{0}'' of the condition element is not supported. It must be one of ''{1}'' (choice activity ''{2}'', case element {3}).
- Explanation: The specified expression language is unknown. Expressions specified in this expression language cannot be executed.
- User Action: Use one of the supported expression languages.
- CWWBW4401E: The condition expression is not valid (choice activity ''{0}'', case element {1}, expression language ''{2}'').
- Explanation: The specified expression is not a valid expression for the given expression language or it is not valid in this context. For example, if you use the built-inexpression language in the case condition, only the values 'wpc:true' and 'wpc:false' areallowed.
- User Action: Check the expression and the expression language.
- CWWBW4500E: The fault variable ''{0}'' is not defined (throw activity ''{1}'').
- Explanation: The fault variable used in the throw activity is not defined.
- User Action: Check that the fault variable name is defined correctly.
- CWWBW4600E: The wait activity must specify a for-expression or an until-expression (wait activity ''{0}'').
- Explanation: The for-expression specifies the duration expression after which the event is signaled. The until-expression specifieswhen the timeout event is fired. One of these expressions must occur in a wait activity.
- User Action: Specify a for-expression or an until-expression.
- CWWBW4601E: The wait activity specifies a for-expression and an until-expression (wait activity ''{0}'').
- Explanation: The for-expression specifies the duration expression after which the event is signaled. The until-expression specifieswhen the timeout event is fired. Only one of these expressions can occur in a wait activity.
- User Action: Remove either the for-expression or the until-expression.
- CWWBW4602E: The wait activity must specify a for expression, an until expression or a timeout expression (wait activity ''{0}'').
- Explanation: The for expression specifies the duration expression after which the event is signaled. The until expression specifies when the alarm event is fired.The timeout expression specifies a timeout using a calendar supplied by the WebSphereApplication Server scheduling service, or user-written calendars adhering to those conventions.One of these expressions must occur in a wait activity.
- User Action: Specify a for expression, an until expression, or a timeout expression.
- CWWBW4603E: The wait activity specifies more than one expression (wait activity ''{0}'').
- Explanation: The for expression specifies the duration expression after which the event is signaled. The until expression specifies when the alarm event is fired.The timeout-expression specifies a timeout using a calendar supplied by the WebSphereApplication Server scheduling service, or user-written calendars adhering to those conventions.One of these expressions must occur in a wait activity.
- User Action: Specify a for expression, an until expression, or a timeout expression.
- CWWBW4604E: The expression language ''{0}'' is not supported. It must be one of ''{1}'' (wait activity ''{2}'').
- Explanation: The specified expression language is unknown. Expressions specified in this expression language cannot be executed.
- User Action: Use one of the supported expression languages.
- CWWBW4700E: The expression language ''{0}'' of the condition element is not supported. It must be one of ''{1}'' (while loop activity ''{2}'').
- Explanation: The specified expression language is unknown. Expressions specified in this expression language cannot be executed.
- User Action: Use one of the supported expression languages.
- CWWBW4701E: The condition expression is not valid (while loop activity ''{0}'', expression language ''{1}'').
- Explanation: The specified expression is not a valid expression for the given expression language or it is not valid in this context. For example, if you use the built-inexpression language in the while loop condition, only the values 'wpc:true' and 'wpc:false' areallowed.
- User Action: Check the expression and the expression language.
- CWWBW4800E: The namespace of the custom activity ''{0}'' is not valid: ''http://'' is missing or ''http:///'' is used (used namespace ''{1}'',element name ''{2}'').
- Explanation: The namespace of the custom activity must start with 'http://', but not with 'http:///'.
- User Action: Ensure that the namespace starts with 'http://'.
- CWWBW4801E: The plug-in found for the custom activity ''{0}'' does not implement the expected interface (found plug-in ''{1}'').
- Explanation: The plug-in must implement the correct interface.
- User Action: Ensure that the plug-in implements the correct interface.
- CWWBW4802E: An exception occurred when the plug-in for the custom activity ''{0}'' was loaded (exception ''{1}'').
- Explanation: The plug-in could not be instantiated.
- User Action: Ensure that the plug-in is in the class path and that it is accessible.
- CWWBW4803E: {0} (custom activity ''{1}'', plug-in ''{2}'').
- Explanation: The plug-in for the custom activity reported the given error.
- User Action: Fix the reported error.
- CWWBW4804W: {0} (custom activity ''{1}'', plug-in ''{2}'').
- Explanation: The plug-in for the custom activity reported the given warning.
- User Action: Fix the reported warning.
- CWWBW4805I: {0} (custom activity ''{1}'', plug-in ''{2}'').
- Explanation: The plug-in for the custom activity reported the given informational message.
- User Action: None.
- CWWBW4806E: The result returned from the plug-in validation is not valid: {0} (custom activity ''{1}'', plug-in ''{2}'').
- Explanation: None.
- User Action: Contact the plug-in owner.
- CWWBW4900E: The portType must be set (human task activity ''{0}'').
- Explanation: The portType is needed to access the operations.
- User Action: Ensure that the portType is set.
- CWWBW4901E: The adminTask element is not allowed (human task activity ''{0}'').
- Explanation: AdminTask elements are allowed only for normal invoke, script, and custom activities, but not for human task activities.
- User Action: Remove the adminTask element from the human task activity.
- CWWBW4902E: The referenced human task ''{0}'' is not a participating task (human task activity ''{1}'').
- Explanation: The human task that is referenced in the human task activity must be a participating task.
- User Action: Reference a participating task.
- CWWBW4903E: The name of the human task activity and the referenced participating human task must be the same (human task activity ''{0}'', participating human task ''{1}'').
- Explanation: The names need to be the same.
- User Action: Either rename the human task activity or the participating human task so that the names are the same.
- CWWBW4904E: The operation must be a request-response operation (human task activity ''{0}'', operation ''{1}'').
- Explanation: Human task activities must invoke a request-response participating task. Request-response operations specify an input and an output message.The used operation does not specify the output message.
- User Action: Specify the output message for the used operation or use another request-response operation.
- CWWBW9000I: Validated the process component model ''{0}'' successfully: {1} information, {2} warnings, {3} errors.
- Explanation: Summary of the successful validation of the process component model.
- User Action: None.
- CWWBW9001I: Validated the process component model ''{0}'' with findings: {1} information, {2} warnings, {3} errors.
- Explanation: This is a summary of the failed validation of the process component model.
- User Action: Update the process component model to solve the problems.
- CWWBW9002I: Validated the process component model ''{0}'' with findings: {1} information, {2} warnings, {3} errors: {4}
- Explanation: This is a summary of the failed validation of the process component model.
- User Action: Update the process component model to solve the problems.
- CWWBW9050E: Process component validation error: ''{0}''. Error parameters: {1}.
- Explanation: This is a general-purpose message for use when the product is in service and a new error message is needed.
- User Action: Check the error message for a description of the error.
- CWWBW9051W: Process component validation warning: ''{0}''. Warning parameters: {1}.
- Explanation: This is a general-purpose message for use when the product is in service and a new warning message is needed.
- User Action: Check the warning message for a description of the warning.
- CWWBW9052I: Process component validation information: ''{0}''. Information parameters: {1}.
- Explanation: This is a general-purpose message for use when the product is in service and a new information message is needed.
- User Action: None.
- CWWBW9100E: The process component file ''{0}'' contains at least one interface of the wrong type. Be sure to use only WSDL port type interfaces.
- Explanation: The process component file contains at least one interface that is of a type other than the WSDL port type. Process component files support only interfaces of the WSDL port type.
- User Action: Correct the process component file so that it contains only WSDL port types.
- CWWBW9101E: The process component file ''{0}'' contains a reference ''{1}'' without an interface.
- Explanation: A reference in a process component file must always have an interface associated with it.
- User Action: Correct the process component file so that all of the references have exactly one interface.
- CWWBW9102E: The process component file ''{0}'' contains a reference ''{1}'' with more than one interface.
- Explanation: A reference in a process component file can have exactly one interface associated with it.
- User Action: Correct the process component file so that all of the references have exactly one interface.
- CWWBW9103E: The process component file ''{0}'' contains a reference ''{1}'' with at least one interface of the wrong type. Be sure to use only WSDL port type interfaces.
- Explanation: The process component file contains a reference with at least one interface that is of a type other than the WSDL port type. Process component files support only interfaces of the WSDL port type.
- User Action: Correct the process component file so that it contains WSDL port types only.
- CWWBW9104E: The process component file ''{0}'' contains a reference ''{1}'' that specifies an interface different to the one specified in the process implementation file.
- Explanation: The process component file contains a reference with the same name as an outbound partner in the process implementation file. The interface specified by this reference is different to the port type of theport type.
- User Action: Correct the process component file or the process implementation file so that they both contain the same interface for matching references to outbound partners.
- CWWBW9105E: The process component file ''{0}'' contains an interface ''{1}'' that does not have a corresponding partner in the process implementation file.
- Explanation: The process component file contains an interface with a signature that was not found in the process implementation file.
- User Action: Correct the process component file or the process implementation file so that they both contain an interface and an inbound partner which match.
- CWWBW9106E: The process component file ''{0}'' contains a reference ''{1}'' that does not have a corresponding partner in the process implementation file.
- Explanation: The process component file contains a reference with an interface signature that was not found in the process implementation file.
- User Action: Correct the process component file or the process implementation file so that they both contain a reference and an outbound partner which match.
- CWWBW9107E: The process component file ''{0}'' does not contain an interface that corresponds to the inbound partner ''{1}'' in the process implementation file.
- Explanation: The process component file does not contain an interface that matches the signature of the inbound partner ''{1}'' in the process implementation file.
- User Action: Add an interface to the process component file that matches the signature of the partner.
- CWWBW9108E: The process component file ''{0}'' does not contain a reference that corresponds to the outbound partner ''{1}'' in the process implementation file.
- Explanation: The process component file does not contain a reference that matches the signature of the outbound partner ''{1}'' in the process implementation file.
- User Action: Add a reference to the process component file that matches the signature of the partner.
- CWWBW9200E: The interface ''{1}'' in the process component file ''{0}'' needs the preferredInteractionStyle attribute with a value of ''async''.
- Explanation: The indicated interface in the process component file does not contain the specified attribute. This attribute with a value of 'async' is mandatory for long-running processes.
- User Action: Add the preferredInteractionStyle attribute with a value 'async' to the interface in the process component file.
- CWWBW9201E: The process component file ''{0}'' requires either the Transaction or the ActivitySession implementation qualifier.
- Explanation: A process component file must specify whether a global transaction or an activity session is to be used.
- User Action: Add either the Transaction or the ActivitySession implementation qualifier to the process component file. For long-running processes, onlythe Transaction implementation qualifier is allowed.
- CWWBW9202E: The interface ''{1}'' in the process component file ''{0}'' does not specify the mandatory JoinTransaction interface qualifier.
- Explanation: Process component files that run in a global transaction must specify the JoinTransaction interface qualifier.
- User Action: Add the JoinTransaction interface qualifier to the interface.
- CWWBW9203E: The operation ''{2}'' of the interface ''{1}'' in the process component file ''{0}'' does not specify the mandatory JoinTransaction interface qualifier.
- Explanation: Process component files that run in a global transaction must specify the JoinTransaction interface qualifier.
- User Action: Add the JoinTransaction interface qualifier to the interface.
- CWWBW9204E: The interface ''{1}'' in the process component file ''{0}'' does not contain the JoinTransaction interface qualifier with a value of ''false''.
- Explanation: Process component files that run in a global transaction and do not specify a long-running process must contain the JoinTransaction interface qualifierwith a value of 'false'.
- User Action: Change the value of the JoinTransaction interface qualifier to 'false'.
- CWWBW9205E: The operation ''{2}'' of the interface ''{1}'' in the process component file ''{0}'' does not contain the JoinTransaction interface qualifier with a value of ''false''.
- Explanation: Process component files that run in a global transaction and do not specify a long-running process must contain the JoinTransaction interface qualifierwith a value of 'false'.
- User Action: Change the value of the JoinTransaction interface qualifier to 'false'.
- CWWBW9206E: The interface ''{1}'' in the process component file ''{0}'' does not contain the JoinTransaction interface qualifier with a value of ''true''.
- Explanation: Process component files that run in a global transaction and specify a long-running process must contain the JoinTransaction interface qualifierwith value of 'true'.
- User Action: Change the value of the JoinTransaction interface qualifier to 'true'.
- CWWBW9207E: The operation ''{2}'' of the interface ''{1}'' in the process component file ''{0}'' does not contain the JoinTransaction interface qualifier with a value of ''true''.
- Explanation: Process component files that run in a global transaction and specify a long-running process must contain the JoinTransaction interface qualifierwith a value of 'true'.
- User Action: Change the value of the JoinTransaction interface qualifier to 'true'.
- CWWBW9208E: The interface ''{1}'' in the process component file ''{0}'' specifies the JoinTransaction interface qualifier although it is not allowed in processesrunning in an activity session.
- Explanation: Process component files that run in an activity session cannot use the JoinTransaction interface qualifier.
- User Action: Remove the JoinTransaction interface qualifier from the interface.
- CWWBW9209E: The operation ''{2}'' of the interface ''{1}'' in the process component file ''{0}'' specifies the JoinTransaction interface qualifier although it is not allowedin processes running in an activity session.
- Explanation: Process component files that run in an activity session cannot use the JoinTransaction interface qualifier.
- User Action: Remove the JoinTransaction interface qualifier from the interface.
- CWWBW9210E: The reference ''{1}'' in the process component file ''{0}'' specifies the SuspendTransaction reference qualifier although this qualifier is not allowed in processes that run in anactivity session.
- Explanation: Process component files that run in an activity session cannot use the SuspendTransaction reference qualifier.
- User Action: Remove the SuspendTransaction reference qualifier from the reference.
- CWWBW9211E: The process component file ''{0}'' must contain the Transaction implementation qualifier with a value of ''global''.
- Explanation: Process component files that run in a global transaction must contain the Transaction implementation qualifier with a value of 'global'.
- User Action: Add the implementation qualifier.
- CWWBW9212E: The process component file ''{0}'' must contain the Transaction implementation qualifier with a value of ''global''.
- Explanation: Process component files that run in a global transaction must contain the Transaction implementation qualifier with a value of 'global'.
- User Action: Change the implementation qualifier so that it is set to 'global'.
- CWWBW9213E: The process component file ''{0}'' must specify the implementation qualifier ''Transaction'' with a value of ''local'' and the local transaction boundarywith a value of ''activity session''.
- Explanation: For process component files which run in an activity session, you must set the value of the implementation qualifier 'Transaction' to 'local' and the value of the localtransaction boundary to 'activity session'.
- User Action: Add the indicated implementation qualifier.
- CWWBW9214E: The process component file ''{0}'' must specify the implementation qualifier ''Transaction'' with a value of ''local'' and the local transaction boundarywith a value of ''activity session''.
- Explanation: For process component files which run in an activity session, you must set the value of the implementation qualifier 'Transaction' to 'local' and the value of the localtransaction boundary to 'activity session'.
- User Action: Change the indicated implementation qualifier.
- CWWBW9215E: The interface ''{1}'' in the process component file ''{0}'' specifies the JoinActivitySession interface qualifier although it is not allowed in long-running processes.
- Explanation: Process component files that specify long-running processes cannot use the JoinActivitySession interface qualifier.
- User Action: Remove the JoinActivitySession interface qualifier from the interface.
- CWWBW9216E: The interface ''{1}'' in the process component file ''{0}'' specifies the JoinActivitySession interface qualifier although it is not allowed in processesthat run in a transaction.
- Explanation: Process component files that run in a transaction cannot use the JoinActivitySession interface qualifier.
- User Action: Remove the JoinActivitySession interface qualifier from the interface.
- CWWBW9217E: The interface ''{1}'' in the process component file ''{0}'' does not specify the mandatory JoinActivitySession interface qualifier.
- Explanation: Process component files that run in an activity session must specify JoinActivitySession interface qualifier.
- User Action: Add the JoinActivitySession interface qualifier to the interface.
- CWWBW9218E: The interface ''{1}'' in the process component file ''{0}'' does not contain the JoinActivitySession interface qualifier with a value of ''true''.
- Explanation: Process component files that run in an activity session must contain a JoinActivitySession interface qualifier with a value of 'true'.
- User Action: Change the value of the JoinActivitySession interface qualifier to 'true'.
- CWWBW9219E: The operation ''{2}'' of the interface ''{1}'' in the process component file ''{0}'' specifies the JoinActivitySession interface qualifier although it is notallowed for processes that run in a transaction.
- Explanation: Process component files that run in a transaction cannot use the JoinActivitySession interface qualifier.
- User Action: Remove the JoinActivitySession interface qualifier from the operation and the interface.
- CWWBW9220E: The operation ''{2}'' of the interface ''{1}'' in the process component file ''{0}'' specifies the JoinActivitySession interface qualifier although it is notallowed in long-running processes.
- Explanation: Process component files that specify long-running processes cannot use the JoinActivitySession interface qualifier.
- User Action: Remove the JoinActivitySession interface qualifier from the interface.
- CWWBW9221E: The operation ''{2}'' of the interface ''{1}'' in the process component file ''{0}'' does not specify the mandatory JoinActivitySession interface qualifier.
- Explanation: Process component files that run in an activity session must specify the JoinActivitySession interface qualifier.
- User Action: Add the JoinActivitySession interface qualifier to the operation and interface.
- CWWBW9222E: The operation ''{2}'' of the interface ''{1}'' in the process component file ''{0}'' does not contain the JoinActivitySession interface qualifier with a value of ''true''.
- Explanation: Process component files that run in an activity session must contain a JoinActivitySession interface qualifier with a value of 'true'.
- User Action: Change the value of the JoinActivitySession interface qualifier to 'true'.
- CWWBW9223E: The reference ''{1}'' in the process component file ''{0}'' specifies the SuspendActivitySession reference qualifier although this qualifier is not allowed in processes that run in atransaction.
- Explanation: Process component files that run in a transaction cannot use the SuspendActivitySession reference qualifier.
- User Action: Remove the SuspendActivitySession reference qualifier from the reference.
- CWWBW9224E: The process component file ''{0}'' specifies the ActivitySession implementation qualifier although it is not allowed in long-running processes.
- Explanation: Process component files that specify long-running processes cannot use the ActivitySession implementation qualifier.
- User Action: Remove the ActivitySession implementation qualifier.
- CWWBW9225E: The process component file ''{0}'' specifies the ActivitySession implementation qualifier although it is not allowed in processes that run in a transaction.
- Explanation: Process component files that run in a transaction cannot use the ActivitySession implementation qualifier.
- User Action: Remove the ActivitySession implementation qualifier.
- CWWBW9226E: The process component file ''{0}'' does not specify the mandatory ActivitySession implementation qualifier.
- Explanation: Process component files that run in an activity session must specify the ActivitySession implementation qualifier.
- User Action: Add the ActivitySession implementation qualifier to the interface.
- CWWBW9227E: The process component file ''{0}'' does not contain an ActivitySession implementation qualifier with a value of ''true''.
- Explanation: Process component files that run in an activity session must contain an ActivitySession implementation qualifier with value of 'true'.
- User Action: Change the value of the ActivitySession implementation qualifier to 'true'.
- CWWBW9228E: The interface ''{1}'' of the process component file ''{0}'' specifies the interface qualifier ''{2}'' more than once.
- Explanation: Interface qualifiers must not be specified more than once for each interface.
- User Action: Ensure that there is only one occurrence of the interface qualifier.
- CWWBW9229E: The reference ''{1}'' of the process component file ''{0}'' specifies the reference qualifier ''{2}'' more than once.
- Explanation: Reference qualifiers must not be specified more than once for each reference.
- User Action: Ensure that there is only one occurrence of the reference qualifier.
- CWWBW9230E: The process component file ''{0}'' specifies the implementation qualifier ''{1}'' more than once.
- Explanation: Implementation qualifiers must not be specified more than once.
- User Action: Ensure that there is only one occurrence of the implementation qualifier.
- CWWBW9231E: The reference ''{1}'' in the process component file ''{0}'' needs the reference qualifier ''Asynchronous Invocation'' with a value of ''commit''.
- Explanation: The indicated reference in the task component file does not contain the specified reference qualifier with the correct value. This is mandatory forlong-running processes.
- User Action: Add the indicated reference qualifier to the reference in the process component file.
- CWWBW9232E: The reference ''{1}'' in the process component file ''{0}'' specifies a multiplicity other than ''1..1''. This is not supported for process component files.
- Explanation: Process component files allow a multiplicity of '1..1' only.
- User Action: Select a multiplicity of '1..1' for the reference.
- CWWBW9300E: The process implementation file ''{1}'' referenced by the process component file ''{0}'' was not found.
- Explanation: The process component file contains a reference to a process implementation file. This reference is present, but the referenced file cannotbe found.
- User Action: Correct the process component file so it points to an existing process implementation file.
- CWWBW9301W: The reference ''{1}'' in the process component file ''{0}'' is wired to another component, but this component is ignored because the correspondingpartner has a process template specified.
- Explanation: The partner in the process implementation file specifies a process template. Therefore, the specified partner is chosen during runtime and thewired component is ignored.
- User Action: Remove the wire from the indicated reference to avoid confusion for other users who read the assembly. Alternatively, if you like to explicitly wirethe components, remove the process template specification from the partner in the processimplementation file.