- CWWBV0001I: 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.
- CWWBV0002E: 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 the application was created with the corresponding tool, ensure that the release levels of the tool and of the run time are compatible. If the application is installed in an ND environment, ensure that all of the servers are at the same release level.
- CWWBV0003E: 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 the application was created with the corresponding tool, ensure that the release levels of the tool and of the run time are compatible. If the application is installed in an ND environment, ensure that all of the servers are at the same release level.
- CWWBV0004E: 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.
- CWWBV0005W: 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.
- CWWBV0006E: 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, the resource cannot be loaded. If no other errors are reported, contact IBM Software Support.
- CWWBV0007E: 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.
- CWWBV0050E: 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.
- CWWBV0051W: 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.
- CWWBV0052I: BPEL validation information: {0}.
- Explanation: General purpose message used when the product is in service and a new message is needed.
- User Action: No action is required.
- CWWBV0101E: 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 flow activity, or a sequence activity. The structured activities can contain basic and structured activities, for example, receive activities, reply activities, assign activities, and scope activities.
- CWWBV0102E: The catch element must contain an activity (process fault handler, catch element number {0}).
- Explanation: An empty catch element cannot be executed.
- User Action: Add an activity to the catch element or remove the element.
- CWWBV0103E: The catchAll element must contain an activity (process fault handler).
- Explanation: An empty catchAll element cannot be executed.
- User Action: Add an activity to the catchAll element or remove the element.
- CWWBV0104E: The onEvent event must contain an activity (process event handler, onEvent event number {0}).
- Explanation: An empty onEvent event cannot be executed.
- User Action: Add an activity to the onEvent event or remove the event.
- CWWBV0105E: The onAlarm event must contain an activity (process event handler, onAlarm event {0}).
- Explanation: An empty onAlarm event cannot be executed.
- User Action: Add an activity to the onAlarm event or remove the event.
- CWWBV0106E: The partnerLinkType must be set (process partnerLink ''{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.
- CWWBV0107E: The partnerLink attribute for onEvent event number {0} is missing.
- Explanation: For an onEvent event, the partnerLink attribute must be specified.
- User Action: In WebSphere Integration Developer, double-click the error message. Right-click the start node and open the event handler. Select the onEvent specified. In the Properties, on the Details tab, browse for and then select a PartnerLink.
- CWWBV0108E: The operation attribute must be set (process event handler, onEvent event number {0}).
- Explanation: The operation attribute must be set for an onEvent event.
- User Action: Set the operation attribute.
- CWWBV0109E: The parameter variable must be set (process event handler, input/output element of onEvent event number {0}, parameter number {1}, parameter name ''{2}'').
- Explanation: The parameter variable must be set.
- User Action: Set the parameter variable.
- CWWBV0110E: The correlation set must refer to at least one property (correlation set ''{0}'').
- Explanation: Correlation sets must contain at least one property.
- User Action: In the correlation set, either refer to an existing property or create a new one.
- CWWBV0111E: 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.
- CWWBV0112E: The name attribute must be set (process event handler, onEvent event number {0}, task element).
- Explanation: The name attribute must be set for all of the task elements.
- User Action: Set the name attribute.
- CWWBV0113E: The duration attribute on the timeout element must be set (process onAlarm event {0}).
- Explanation: A timeout element on an onAlarm event must define a duration.
- User Action: Set the duration attribute on the timeout element.
- CWWBV0114E: The correlation ''set'' attribute must be set (process event handler, onEvent event number {0}, correlation element number {1}).
- Explanation: The correlation set attribute must be set for all of the correlation elements.
- User Action: Set the correlation set attribute.
- CWWBV0200E: The catch element must contain an activity (fault handler of activity ''{0}'', catch element number {1}).
- Explanation: An empty catch element cannot be executed.
- User Action: Add an activity to the catch element or remove the element.
- CWWBV0201E: The catchAll element must contain an activity (fault handler of activity ''{0}'').
- Explanation: An empty catchAll element cannot be executed.
- User Action: Add an activity to the catchAll element or remove the element.
- CWWBV0202E: 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.
- CWWBV0203E: The partnerLink attribute must be set (activity ''{0}'').
- Explanation: For invoke, receive, and reply activities, the partnerLink attribute must be set.
- User Action: Set the partnerLink attribute.
- CWWBV0204E: The operation for the ''{0}'' activity is missing.
- Explanation: For invoke, receive, and reply activities, the operation attribute must be specified.
- User Action: In WebSphere Integration Developer, double-click the error message and select the specified activity. In the Properties view, on the Details tab, browse for and select an operation.
- CWWBV0205E: The duration attribute of the timeout element must be set (activity ''{0}'').
- Explanation: A timeout element on an Expiration must define a duration.
- User Action: Set the duration attribute of the timeout element.
- CWWBV0206E: The parameter variable must be set (input/output element of activity ''{0}'', parameter number {1}, parameter name ''{2}'').
- Explanation: A mandatory parameter variable for the activity is not defined.
- User Action: Set the parameter variable.
- CWWBV0207E: 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.
- CWWBV0208E: 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.
- CWWBV0209E: The correlation ''set'' attribute must be set (activity ''{0}'', correlation element number {1}).
- Explanation: The correlation set attribute must be set for all of the correlation elements.
- User Action: Set the correlation set attribute.
- CWWBV0210E: An exception occurred when using the The XML Path Language (XPath) plug-in for the {0} XPAth expression on the {1} activity (exception {2}).
- Explanation: The plug-in cannot be used.
- User Action: Check the technical information databases on the WebSphere Process Server support site at http://www.ibm.com/software/integration/wps/support/. If you cannot find the information that you need to solve the problem, contact your technical support provider or again refer to the WebSphere Process Server support site for information about IBM Software Support and Services.
- CWWBV0211E: The toVariable or fromVariable attribute in the fromPart or toPart element must be set ({0} activity, fromPart or toPart number {1}).
- Explanation: A mandatory fromPart or toPart attribute is not defined.
- User Action: Set the toVariable or fromVariable attribute.
- CWWBV0212E: The part attribute in the fromPart or toPart element must be set ({0} activity, fromPart or toPart number {1}).
- Explanation: A mandatory fromPart or toPart attribute is not defined.
- User Action: Set the part attribute.
- CWWBV0300E: 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.
- CWWBV0301E: The copy element must contain a from-element (assign activity ''{0}'', copy element number {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.
- CWWBV0302E: The copy element must contain a to-element (assign activity ''{0}'', copy element number {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.
- CWWBV0303E: The reference-scheme attribute must be set (assign activity ''{0}'', copy element number {1}, from-spec, serviceRef element).
- Explanation: The service reference element must define a reference-scheme.
- User Action: Set the reference-scheme attribute.
- CWWBV0304E: The serviceRef element cannot be empty (assign activity ''{0}'', copy element number {1}, from-spec, serviceRef element).
- Explanation: The serviceRef element must contain an element.
- User Action: Set any of the allowed elements.
- CWWBV0400E: The target attribute must be set ({0} compensateScope activity).
- Explanation: The compensateScope elements must define a target.
- User Action: Set the target attribute.
- CWWBV0600E: The ''{0}'' Flow activity does not contain an activity.
- Explanation: An empty Flow activity cannot run.
- User Action: In WebSphere Integration Developer, double-click the error message. In the business process editor, add an activity to the Flow activity by selecting an activity from the palette and droping it onto the Flow activity. Alternatively, remove the Flow activity by right-clicking this activity and selecting Delete.
- CWWBV0650E: The generalized flow activity must contain an activity. Add an activity to it (generalized flow activity ''{0}'').
- Explanation: An empty generalized flow activity cannot be executed.
- User Action: Remove the generalized flow activity, or add an activity to it.
- CWWBV0700E: The partnerLink attribute of the undo action must be set (invoke activity ''{0}'').
- Explanation: For an undo action in an invoke activity, the partnerLink attribute must be set.
- User Action: Set the partnerLink attribute.
- CWWBV0701E: 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.
- CWWBV0702E: The parameter variable for the undo action must be set (input/output element of invoke activity ''{0}'', parameter number {1}, parameter name ''{2}'').
- Explanation: A mandatory parameter variable for the undo action is not defined.
- User Action: Set the parameter variable for the undo action.
- CWWBV0800E: The pick activity must contain an onMessage element (pick activity ''{0}'').
- Explanation: An empty pick activity cannot be executed.
- User Action: Add an onMessage element to the pick activity or remove the activity.
- CWWBV0801E: The onMessage element, number {1}, in pick activity ''{0}'' is missing an activity.
- Explanation: An empty onMessage element cannot run.
- User Action: In WebSphere Integration Developer, double-click the error message and add an activity to the OnMessage (On Message) element by selecting the activity from the palette and droping it onto the OnMessage (On Message) element. Alternatively, remove the OnMessage element by right-clicking it and selecting Delete.
- CWWBV0802E: The onAlarm event must contain an activity (pick activity ''{0}'', onAlarm event {1}).
- Explanation: An empty onAlarm event cannot be executed.
- User Action: Add an activity to the onAlarm event or remove the event.
- CWWBV0803E: The partnerLink attribute for OnMessage element number {1} in pick activity ''{0}'' is missing.
- Explanation: The PartnerLink attribute must be specified for an OnMessage element.
- User Action: In WebSphere Integration Developer, double-click the error message and select the specified OnMessage element. In the Properties view, on the Details tab, browse for and select a PartnerLink.
- CWWBV0804E: The operation attribute for OnMessage element number {1} in pick activity ''{0}'' is missing.
- Explanation: The operation attribute must be specified for an OnMessage element.
- User Action: In WebSphere Integration Developer, double-click the error message and select the specified OnMessage element. In the Properties view, on the Details tab, select an operation.
- CWWBV0805E: The parameter variable must be set (pick activity ''{0}'', input/output element of onMessage element number {1}, parameter number {2}, parameter name ''{3}'').
- Explanation: A mandatory parameter variable for the onMessage element on a pick is not defined.
- User Action: Set the parameter variable.
- CWWBV0806E: The name attribute must be set (pick activity ''{0}'', onMessage element number {1}, task element).
- Explanation: The name attribute must be set for all of the task elements.
- User Action: Set the name attribute.
- CWWBV0807E: The duration attribute on the timeout element must be set (pick activity ''{0}'', onAlarm event {1}).
- Explanation: A timeout element on an onAlarm event must define a duration.
- User Action: Set the duration attribute on the timeout element.
- CWWBV0808E: The correlation ''set'' attribute must be set (pick activity ''{0}'', onMessage element number {1}, correlation element number {2}).
- Explanation: The correlation set attribute must be set for all of the correlation elements.
- User Action: Set the correlation set attribute.
- CWWBV1200E: The ''{0}'' scope activity must contain an activity.
- Explanation: An empty scope activity cannot run.
- User Action: Remove the scope activity, or add an activity to it. In WebSphere Integration Developer, double-click the error message and add an activity to the specified scope activity by selecting the activity from the palette and droping it onto the scope element. Alternatively, remove the scope activity by right-clicking it and selecting Delete.
- CWWBV1201E: The onEvent event must contain an activity (event handler of scope activity ''{0}'', onEvent event number {1}).
- Explanation: An empty onEvent event cannot be executed.
- User Action: Add an activity to the onEvent event, or remove the event.
- CWWBV1202E: The onAlarm event must contain an activity (event handler of scope activity ''{0}'', onAlarm event {1}).
- Explanation: An empty onAlarm event cannot be executed.
- User Action: Add an activity to the onAlarm event, or remove the event.
- CWWBV1203E: The partnerLink attribute must be set (scope activity ''{0}'', onEvent event number {1}).
- Explanation: For an onEvent event, the partnerLink attribute must be set.
- User Action: Set the partnerLink attribute.
- CWWBV1204E: The operation attribute must be set (scope activity ''{0}'', onEvent event number {1}).
- Explanation: For an onEvent event, the operation attribute must be set.
- User Action: Set the operation attribute.
- CWWBV1205E: The parameter variable must be set (scope activity ''{0}'', input/output element of onEvent event number {1}, parameter number {2}, parameter name ''{3}'').
- Explanation: A mandatory parameter variable for the onEvent element on a scope is not defined.
- User Action: Set the parameter variable.
- CWWBV1206E: 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.
- CWWBV1207E: The duration attribute on the timeout element must be set (scope activity ''{0}'', onAlarm event {1}).
- Explanation: A timeout element on an onAlarm event must define a duration.
- User Action: Set the duration attribute on the timeout element.
- CWWBV1208E: The correlation ''set'' attribute must be set (scope event handler, of scope activity ''{0}'', onEvent event number {1}, correlation element number {2}).
- Explanation: The correlation set attribute must be set for all of the correlation elements.
- User Action: Set the correlation set attribute.
- CWWBV1300E: 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.
- CWWBV1400E: The switch activity must contain a case element (switch activity ''{0}'').
- Explanation: An empty switch activity cannot be executed.
- User Action: Add a case element to the switch activity, or remove the activity.
- CWWBV1401E: Case element number {1} in Switch activity ''{0}'' does not specify a condition.
- Explanation: The condition defines which case branch runs. The value of the condition is either true or false when it runs.
- User Action: Specify the case condition. In WebSphere Integration Developer, double-click the error message and select the specified case element. In the Properties view, on the Details tab, specify a condition.
- CWWBV1402E: Case element number {1} in Switch activity ''{0}'' does not contain an activity.
- Explanation: An empty case element cannot run.
- User Action: Add an activity to the case element, or remove the element. In WebSphere Integration Developer, double-click the error message and add an activity to the specified case element. Alternatively, remove the case element by right-clicking it and selecting Delete.
- CWWBV1403E: The otherwise element must contain an activity (switch activity ''{0}'').
- Explanation: An empty otherwise element cannot be executed.
- User Action: Add an activity to the otherwise element, or remove the element.
- CWWBV1500E: 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.
- CWWBV1700E: The ''{0}'' While activity does not specify a condition.
- Explanation: The condition specifies whether the activity will run again. When the condition runs, it holds either true or false.
- User Action: Specify a condition for the While activity. In WebSphere Integration Developer, select the specified While activity. In the Properties view, on the Details tab, and specify a condition.
- CWWBV1701E: The ''{0}'' While activity does not contain an activity.
- Explanation: An empty While activity cannot run.
- User Action: Remove the While activity, or add an activity to it. In WebSphere Integration Developer, double-click the error message and add an the activity to the specified While activity. Alternatively, remove the While activity by right-clicking it and selecting Delete.
- CWWBV1950E: The forEach activity requires a counterName attribute (forEach activity ''{0}'').
- Explanation: The counterName attribute must be set for a forEach activity.
- User Action: Set the counterName attribute.
- CWWBV1951E: The forEach activity must contain a startCounterValue element (forEach activity ''{0}'').
- Explanation: A forEach activity must specify a startCounterValue element inside the iterator element.
- User Action: Remove the forEach activity, or ensure it specifies a startCounterValue element.
- CWWBV1952E: The forEach activity must contain a finalCounterValue element (forEach activity ''{0}'').
- Explanation: A forEach activity must specify a finalCounterValue element inside the iterator element.
- User Action: Remove the forEach activity, or ensure it specifies a finalCounterValue element.
- CWWBV1953E: The forEach activity must contain a scope activity (forEach activity ''{0}'').
- Explanation: A forEach activity is allowed to directly contain a scope activity only.
- User Action: Remove the forEach activity, or ensure it directly contains a scope activity.
- CWWBV2000E: The {0} RepeatUntil activity does not specify a condition.
- Explanation: The condition specifies whether the activity will run again. When the condition runs, it holds either true or false.
- User Action: Specify a condition for the RepeatUntil activity. In WebSphere Integration Developer, select the specified While activity. In the Properties view, on the Details tab, specify a condition.
- CWWBV2001E: The {0} RepeatUntil activity does not contain an activity.
- Explanation: An empty RepeatUntil activity cannot run.
- User Action: Remove the RepeatUntil activity or add an activity to it. In WebSphere Integration Developer, double-click the error message and add an activity to the specified While activity. Alternatively, remove the While activity by right-clicking it and selecting Delete.
- CWWBV3000E: 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.
- CWWBV3001E: 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.
- CWWBV3002E: The partnerLinkType ''{0}'' was not found (process partnerLink ''{1}'').
- Explanation: The partnerLinkType referenced in the process partnerLink is not defined in the WSDL interface.
- User Action: Check that the partnerLinkType is defined correctly in the WSDL interface.
- CWWBV3003E: The myRole role ''{0}'' was not found (process partnerLink ''{1}'', partnerLinkType ''{2}'').
- Explanation: The role referenced in the partnerLink is not defined in the partnerLinkType.
- User Action: Check that the role is defined correctly in the partnerLinkType.
- CWWBV3004E: The portType in the role ''{0}'' is not set (process partnerLink ''{1}'', partnerLinkType ''{2}'').
- Explanation: The portType in the role is needed to access the operations.
- User Action: Ensure that the portType is set.
- CWWBV3005E: The portType ''{0}'' was not found (process partnerLink ''{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.
- CWWBV3006E: The partnerRole role ''{0}'' was not found (process partnerLink ''{1}'', partnerLinkType ''{2}'').
- Explanation: The role referenced in the partnerLink is not defined in the partnerLinkType.
- User Action: Check that the role is defined correctly in the partnerLinkType.
- CWWBV3007E: Either the myRole role, the partnerRole role, or both must be defined (process partnerLink ''{0}'').
- Explanation: A partnerLink must have a definition for the myRole role, the partnerRole role, or both.
- User Action: Define the roles for the partnerLink.
- CWWBV3008E: 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.
- CWWBV3009E: 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.
- CWWBV3010E: 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.
- CWWBV3011E: 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 inline in a WSDL interface or in an XML schema.
- User Action: Check that the XSD type definition is correctly referenced and that it is defined correctly.
- CWWBV3012E: 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 inline 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.
- CWWBV3013E: 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.
- CWWBV3014E: 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 number {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.
- CWWBV3015E: If the catch element has the fault variable set, it must also have a type specification set (process fault handler, catch element number {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.
- CWWBV3016E: The catch element cannot have the fault message type and the fault type set (process fault handler, catch element number {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.
- CWWBV3017E: If the catch element has the fault message type set, it must also have a fault variable set (process fault handler, catch element number {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.
- CWWBV3018E: If the catch element has the fault type set, it must also have a fault variable set (process fault handler, catch element number {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.
- CWWBV3019E: The messageType ''{0}'' was not found (process fault handler, catch element number {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.
- CWWBV3020E: The type ''{0}'' was not found (process fault handler, catch element number {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.
- CWWBV3021E: The process fault handler must contain a catch element or a catchAll element.
- Explanation: A fault handler must have at least one catch element or one catchAll element.
- User Action: Define a catch element, or a catchAll element, or remove the fault handler.
- CWWBV3023E: 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.
- CWWBV3024W: 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.
- CWWBV3025W: 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.
- CWWBV3026E: The process event handler must contain an onEvent event or an onAlarm event.
- Explanation: An event handler must have at least one onEvent event or one onAlarm event.
- User Action: Define an onEvent event, or an onAlarm event, or remove the event handler.
- CWWBV3027E: The partnerLink ''{0}'' was not found (process onEvent event {1}).
- Explanation: The partnerLink referenced in the onEvent event is not defined.
- User Action: Ensure that the partnerLink is correct and that it is defined.
- CWWBV3028E: The partnerLink ''{0}'' does not define the myRole role (process onEvent event number {1}).
- Explanation: PartnerLinks must define the myRole role if these links are used in onEvent events.
- User Action: Define the myRole role for the partnerLink or use a different partnerLink.
- CWWBV3029E: 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.
- CWWBV3030E: The portType referenced in process onEvent event number {0} and in the myRole role ''{1}'' must be the same (partnerLink ''{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 partnerLink.
- User Action: Ensure that the port types are the same.
- CWWBV3031E: 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.
- CWWBV3032E: The input element is not defined in the operation ''{0}'' (process onEvent event number {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.
- CWWBV3033E: The messageType is not set in the input element of the operation ''{0}'' (process onEvent event number {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.
- CWWBV3034E: The messageType ''{0}'' referenced in the operation ''{1}'' was not found (process onEvent event number {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.
- CWWBV3035E: The messageType of variable ''{0}'' and the input element of the operation ''{1}'' must be the same (process onEvent event number {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.
- CWWBV3036E: The variable is not set (process onEvent event number {0}).
- Explanation: A mandatory variable for the onEvent event is not defined.
- User Action: Define the mandatory variable.
- CWWBV3037E: The messageType or element attribute is not set (process onEvent event number {0}).
- Explanation: A mandatory attribute (messageType or element) for the onEvent event is not defined.
- User Action: Define either the messageType or the element attribute.
- CWWBV3038E: 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.
- CWWBV3039E: 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.
- CWWBV3040E: The process onAlarm event must specify at least a for expression, an until expression, or a repeatEvery expression (process onAlarm event {0}).
- Explanation: The for element defines the duration expression after which the event is signaled. The until element specifies when the alarm event is fired. If the repeatEvery element is specified, the alarm event is fired repeatedly once each time the duration period expires. One of these three expressions or a repeatEvery expression with a for expression or an until expression must occur in an onAlarm event.
- User Action: Specify a for expression, an until expression, or a repeatEvery expression.
- CWWBV3041E: The process onAlarm event must specify at least a for expression, an until expression, a timeout expression, or a repeatEvery expression (process onAlarm event {0}).
- 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 WebSphere Application Server scheduling service, or user-written calendars adhering to those conventions. If the repeatEvery element is specified, the alarm event is fired repeatedly once each time the duration period expires. One of these four expressions or a repeatEvery expression with a for expression, an until expression, or a timeout expression must occur in an onAlarm event.
- User Action: Specify a for expression, an until expression, a timeout expression, or a repeatEvery expression.
- CWWBV3042E: The process onAlarm event cannot specify a for expression and a timeout expression or an until expression and a timeout expression (process onAlarm event {0}).
- 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 WebSphere Application Server scheduling service, or user-written calendars adhering to those conventions. If the repeatEvery element is specified, the alarm event is fired repeatedly once each time the duration period expires. One of these four expressions or a repeatEvery expression with a for expression, an until expression or a timeout expression must occur in an onAlarm event.
- User Action: Specify a for expression, an until expression, a timeout expression, or a repeatEvery expression.
- CWWBV3043E: The expression language ''{0}'' is not supported. It must be one of ''{1}'' (process onAlarm 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.
- CWWBV3044E: 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.
- CWWBV3045E: 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.
- CWWBV3046E: 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.
- CWWBV3047E: 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.
- CWWBV3048E: 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 schema primitive simple types and all simple types derived by restriction from a primitive simple type.
- User Action: Select an allowed XML schema simple type.
- CWWBV3049I: 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.
- CWWBV3050E: 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.
- CWWBV3051E: A task activity cannot be used in a microflow (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.
- CWWBV3052E: A wait activity cannot be used in a microflow (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.
- CWWBV3053E: An onAlarm event in a pick activity cannot be used in a microflow (non-interruptible process). The pick activity name is ''{0}''.
- Explanation: Pick activities in microflows (non-interruptible processes) cannot have onAlarm events.
- User Action: Remove the onAlarm events, or define the process as long-running.
- CWWBV3054E: A process that is not long-running must not contain more than one pick or receive activity: ''{0}''.
- Explanation: Microflows (non-interruptible processes) can have only one start point.
- User Action: Define only one pick or receive activity, or define the process as long-running. In WebSphere Integration Developer, double-click the error message. To make the process long running, click somewhere in the whitespace of your canvas. In the Properties view, on the Detailstab, select Process is long-running. To define only one pick or receive activity, delete all of the specified pick and receive activities.
- CWWBV3055E: 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 pick 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.
- CWWBV3056E: The process is not startable. No pick 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 pick or receive activity is available that creates a new process instance and when this activity is not the target of any links or has any preceding basic activities.
- User Action: Ensure that all of the pick and receive activities are defined correctly, or add a pick or receive activity that can create a process instance.
- CWWBV3057E: The variable must not be set because an output element is available (process onEvent event number {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-typed variables specified in the output element.
- User Action: Remove the variable attribute from the onEvent event.
- CWWBV3058E: 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.
- CWWBV3059E: The parameter-extension cannot be used for the message ''{0}''. Modify the message or use a message-type variable (process onEvent event number {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, which cannot 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.
- CWWBV3060E: The parameter ''{0}'' is not mapped to an element or part. Map it to a valid element or part (process onEvent event number {1}, parameter number {2}).
- Explanation: A parameter has been found that 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.
- CWWBV3061E: The variable name ''{0}'' is used already in the same onEvent event. Use another variable name (output element of process onEvent event number {1}, parameter number {2}).
- Explanation: A variable name can be used only once in an output element.
- User Action: Use another variable name.
- CWWBV3062E: A matching propertyAlias definition was not found for the property ''{0}'' and the messageType ''{1}'' (process onEvent event number {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.
- CWWBV3063E: The part ''{0}'' referenced in the propertyAlias for the property ''{1}'' and the messageType ''{2}'' was not found (process onEvent event number {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.
- CWWBV3064E: The part ''{0}'' referenced in the propertyAlias for the property ''{1}'' and the messageType ''{2}'' does not reference a valid XML schema simple type (process onEvent event number {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.
- CWWBV3065E: The type of the part ''{0}'' of the messageType ''{1}'' and the type of the property ''{2}'' are not the same (process onEvent event number {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.
- CWWBV3066E: Multiple propertyAlias definitions were found for the property ''{0}'' and the messageType ''{1}'' (process onEvent event number {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.
- CWWBV3067E: The 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.
- CWWBV3068E: The human task ''{0}'' is not an administration task (process adminTask or activityAdminTask element).
- Explanation: The human task referenced in the process adminTask or the activityAdminTask element must be an administration task.
- User Action: Reference an administration task.
- CWWBV3069E: The human task ''{0}'' cannot be found (process onEvent event number {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.
- CWWBV3070E: The human task ''{0}'' is not an invocation task (process onEvent event number {1}).
- Explanation: The human task referenced in the process onEvent event must be an invocation task.
- User Action: Reference an invocation task.
- CWWBV3071E: The portType referenced in process onEvent event number {0} and in the human task ''{1}'' must be the same.
- Explanation: The portTypes must be the same.
- User Action: Ensure that the portTypes are the same.
- CWWBV3072E: The operation referenced in process onEvent event number {0} and in the human task ''{1}'' must be the same.
- Explanation: The operations must be the same.
- User Action: Ensure that the operations are the same.
- CWWBV3073E: The part is not set in the propertyAlias for the property ''{0}'' and the messageType ''{1}'' (process onEvent event number {2}, correlation set ''{3}'').
- Explanation: The part must be set in the propertyAlias.
- User Action: Set the part.
- CWWBV3074E: The query language ''{0}'' used in the propertyAlias is not supported. It must be one of ''{1}'' (process onEvent event number {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.
- CWWBV3075E: The expression is not valid (process onAlarm 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.
- CWWBV3076E: A reply activity was not found that matches process onEvent event number {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.
- CWWBV3077E: An event handler cannot be used in a microflow (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.
- CWWBV3078E: An event handler cannot be used in a microflow (non-interruptible process). The scope activity name is ''{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.
- CWWBV3079E: A compensation handler cannot be used in a microflow (non-interruptible process). The activity name is ''{0}''.
- Explanation: Microflows (non-interruptible processes) must not contain compensation handlers, neither on scope activities nor on invoke activities. However, you can use an undo action on invoke activities within microflows.
- User Action: Define the process as a long-running process or remove the compensation handler.
- CWWBV3080E: An expiration element cannot be used in a microflow (non-interruptible process). The activity name is ''{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.
- CWWBV3081E: A compensate activity cannot be used in a microflow (non-interruptible process). The compensate activity name is ''{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.
- CWWBV3082W: The one-way process cannot specify the autonomy 'child'. The attribute will be ignored.
- Explanation: For a 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'.
- CWWBV3083E: More than one variable type definition is set for the variable ''{0}''. Set only one (process onEvent event number {1}, parameter number {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.
- CWWBV3084E: The XSD element declaration ''{0}'' was not found (process onEvent event number {1}, parameter number {2}, variable ''{3}'').
- Explanation: The XSD element declaration referenced in the variable must be either defined inline 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.
- CWWBV3085E: The XSD type definition ''{0}'' was not found (process onEvent event number {1}, parameter number {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 inline in a WSDL interface or in an XML schema.
- User Action: Check that the XSD type definition is correctly referenced and that it is defined correctly.
- CWWBV3086E: The variable ''{0}'' must have a variable type definition (process onEvent event number {1}, parameter number {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.
- CWWBV3087E: The XSD type definition ''{0}'' was not found (process onEvent event number {1}, parameter number {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 inline in a WSDL interface or in an XML schema.
- User Action: Check that the XSD type definition is correctly referenced and that it is defined correctly.
- CWWBV3088E: The XSD element declaration ''{0}'' was not found (process onEvent event number {1}, parameter number {2}, matching part or element ''{3}'').
- Explanation: The XSD element declaration referenced in the matching part or element must be either defined inline 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.
- CWWBV3089E: The element ''{0}'' cannot be assigned to variable ''{1}'' because the data type does not match (process onEvent event number {2}, parameter number {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.
- CWWBV3090E: The part ''{0}'' cannot be assigned to variable ''{1}'' because the data type does not match (process onEvent event number {2}, parameter number {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.
- CWWBV3091E: The XSD element ''{0}'' must be mapped to a parameter (process onEvent event number {1}).
- Explanation: An element has been found in the wrapper that does not map to a parameter.
- User Action: Remove the element or map it to a parameter.
- CWWBV3092E: The message-part ''{0}'' must be mapped to a parameter (process onEvent event number {1}).
- Explanation: A message-part has been found in the wrapper that does not map to a parameter.
- User Action: Remove the message-part or map it to a parameter.
- CWWBV3093E: The process partnerLink name ''{0}'' is used already. Use a unique name.
- Explanation: The name of a partnerLink must be unique within its own scope.
- User Action: Use a different partnerLink name.
- CWWBV3094E: The process correlation set name ''{0}'' is used already. Use a unique name.
- Explanation: The name of a correlation set must be unique within its own scope.
- User Action: Use a different correlation set name.
- CWWBV3095E: The correlation set ''{0}'' is used already. It can only be used once (process onEvent event number {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.
- CWWBV3096E: The process custom property name ''{0}'' has been used already. Provide a unique name.
- Explanation: The custom property names for the process element must be unique.
- User Action: Ensure the name of each process custom property is unique.
- CWWBV3097E: Process onEvent event number {0} implements operation ''{1}'' of portType ''{2}'', which is already implemented in another process onEvent event.
- Explanation: The same portType and operation can be implemented only once in the same event handler. In case a message is received for a specific portType and operation, the executing engine must know which onEvent event in that instance of the process has to be executed.
- User Action: Remove the onEvent event or change the operation.
- CWWBV3098E: Process onEvent event number {0} must use at least one correlation set.
- Explanation: If an onEvent event is used in a process model, it 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 onEvent event.
- CWWBV3099E: The referenced property ''{0}'' was not found (process variable ''{1}'', queryProperty element number {2}).
- Explanation: The referenced property must be defined.
- User Action: Define the referenced property, or remove the queryProperty element from the variable.
- CWWBV3100E: 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.
- CWWBV3101E: The catch element does not specify a fault name, a fault variable with a type specification, or both (fault handler of activity ''{0}'', catch element number {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.
- CWWBV3102E: If the catch element has the fault variable set, it must also have a type specification set (fault handler of activity ''{0}'', catch element number {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.
- CWWBV3103E: The catch element cannot have the fault message type and the fault type set (fault handler of activity ''{0}'', catch element number {1}, fault message type ''{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.
- CWWBV3104E: 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 number {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.
- CWWBV3105E: If the catch element has the fault type set, it must also have a fault variable set (fault handler of activity ''{0}'', catch element number {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.
- CWWBV3106E: The messageType ''{0}'' was not found (fault handler of activity ''{1}'', catch element number {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.
- CWWBV3107E: The type ''{0}'' was not found (fault handler of activity ''{1}'', catch element number {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.
- CWWBV3108E: The fault handler must contain a catch element or a catchAll element (fault handler of activity ''{0}'').
- Explanation: A fault handler must have at least one catch element or one catchAll element.
- User Action: Define a catch element or a catchAll element, or remove the fault handler.
- CWWBV3109E: The correlations element is not allowed (activity ''{0}'').
- Explanation: The correlations element is only allowed for invoke activities, but not for script, human task, or custom activities.
- User Action: Remove the correlations element from the activity.
- CWWBV3110E: Fault handlers are not allowed (activity ''{0}'').
- Explanation: Fault handlers are only allowed for invoke activities, but not for script, human task, or custom activities.
- User Action: Remove the fault handlers from the activity.
- CWWBV3111E: The expiration, script, and undo elements cannot be used in the activity ''{0}''. These elements are only allowed in invoke activities.
- Explanation: Expiration, script and undo elements are only allowed in invoke activities.
- User Action: Remove the elements from the activity.
- CWWBV3112E: The custom activity element ''{0}'' cannot be used in the activity ''{1}''. This element is only allowed in invoke activities.
- Explanation: The custom activity element is only allowed in invoke activities.
- User Action: Remove the custom activity element from the activity.
- CWWBV3113E: The task element cannot be used in the activity ''{0}''.
- Explanation: This element is normally only allowed in invoke and receive activities. However, the task element is also allowed in pick activities in the onMessage element.
- User Action: Remove the task element from the activity.
- CWWBV3114E: The annotation element cannot be used in the activity ''{0}''. This element is only allowed in scope activities.
- Explanation: The annotation element is only allowed in scope activities.
- User Action: Remove the annotation element from the activity.
- CWWBV3115E: The timeout element cannot be used in the activity ''{0}''. This element is only allowed in wait activities.
- Explanation: The timeout element is only allowed in wait activities.
- User Action: Remove the timeout element from the activity.
- CWWBV3116E: The input element cannot be used in the activity ''{0}''. This element is only allowed in invoke and reply activities.
- Explanation: The input element is only allowed in invoke and reply activities.
- User Action: Remove the input element from the activity.
- CWWBV3117E: The output element cannot be used in the activity ''{0}''. This element is only allowed in invoke and receive activities.
- Explanation: The output element is also allowed in pick activities in the onMessage element.
- User Action: Remove the output element from the activity.
- CWWBV3118E: The continueOnError attribute cannot be used in the ''{0}'' activity. It is allowed only in invoke activities.
- Explanation: The continueOnError attribute is allowed only in invoke activities.
- User Action: Remove the attribute from the activity.
- CWWBV3120E: The compensable attribute cannot be used in the activity ''{0}''. This attribute is only allowed in scope activities.
- Explanation: The compensable attribute is only allowed in scope activities.
- User Action: Remove the compensable attribute from the activity.
- CWWBV3121E: 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 custom activity using an element from a different namespace. Combinations of these extension elements are not allowed.
- User Action: Ensure that only one of the extension elements is used in the invoke activity.
- CWWBV3122E: The link ''{0}'' is not defined (referenced in the activity ''{1}'').
- Explanation: A link must be defined in a flow activity before it can be referenced in a different activity. Additionally, this activity must be nested in the flow activity because links are visible only inside the defining flow activity.
- User Action: Ensure that the referenced link is defined in one of the parent flow activities.
- CWWBV3123E: 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.
- CWWBV3124E: 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.
- CWWBV3125E: The undo action is not allowed (activity ''{0}'').
- Explanation: Undo actions are only allowed for invoke activities, but not for script, human task, or custom activities.
- User Action: Remove the undo action from the activity.
- CWWBV3126E: 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.
- CWWBV3127W: 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.
- CWWBV3128E: The partnerLink ''{0}'' was not found (activity ''{1}'').
- Explanation: The partnerLink referenced in the activity is not defined.
- User Action: Ensure that the partnerLink used is correct and that it is defined.
- CWWBV3129E: The partnerLink ''{0}'' does not define the myRole role (activity ''{1}'').
- Explanation: PartnerLinks used in receive or reply activities must define the myRole role.
- User Action: Define the myRole role for the partnerLink or use a different partnerLink.
- CWWBV3130E: 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.
- CWWBV3131E: The portType referenced in the activity ''{0}'' and in the role ''{1}'' must be the same (partnerLink ''{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 partnerLink.
- User Action: Ensure that the portType attributes are the same.
- CWWBV3132E: 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.
- CWWBV3133E: 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.
- CWWBV3134E: 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.
- CWWBV3135E: 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.
- CWWBV3136E: 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.
- CWWBV3137E: 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.
- CWWBV3138E: 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.
- CWWBV3139E: 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.
- CWWBV3140E: 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.
- CWWBV3141E: 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.
- CWWBV3142E: The variable is not set (activity ''{0}'').
- Explanation: A mandatory variable for the activity is not defined.
- User Action: Define the mandatory variable.
- CWWBV3143E: The input variable for the ''{0}'' activity is not specified.
- Explanation: For some activities, the input variable is mandatory.
- User Action: Define the input variable. In WebSphere Integration Developer, double-click the error message and select the specified activity. In the Properties view, on the Details tab, specify an input variable.
- CWWBV3144E: 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.
- CWWBV3145E: 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.
- CWWBV3146E: 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.
- CWWBV3147E: The onAlarm event must specify at least a for expression, an until expression, or a repeatEvery expression (activity ''{0}'', onAlarm event {1}).
- Explanation: The for element defines the duration expression after which the alarm event is signaled. The until element specifies when the alarm event is fired. If the repeatEvery element is specified, the alarm event will be fired repeatedly once each time the duration period expires. One of these three expressions or a repeatEvery expression with a for expression or an until expression must occur in an onAlarm event.
- User Action: Specify a for expression, an until expression, or a repeatEvery expression.
- CWWBV3148E: The onAlarm event must specify at least a for expression, an until expression, a timeout expression, or a repeatEvery expression (activity ''{0}'', onAlarm 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 WebSphere Application Server scheduling service, or user-written calendars adhering to those conventions. If the repeatEvery element is specified, the alarm event is fired repeatedly once each time the duration period expires. One of these four expressions or a repeatEvery expression with a for expression, an until expression, or a timeout expression must occur in an onAlarm event.
- User Action: Specify a for expression, an until expression, a timeout expression, or a repeatEvery expression.
- CWWBV3149E: The onAlarm event cannot specify a for expression and a timeout expression or an until expression and a timeout expression (activity ''{0}'', onAlarm event {1}).
- Explanation: The for element specifies 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 WebSphere Application Server scheduling service, or user-written calendars adhering to those conventions. If the repeatEvery element is specified, the alarm event is fired repeatedly once each time the duration period expires. One of these four expressions or a repeatEvery expression with a for expression, an until expression or a timeout expression must occur in an onAlarm event.
- User Action: Specify a for, until, timeout or repeatEvery expression.
- CWWBV3150E: The expression language ''{0}'' is not supported. It must be one of ''{1}'' (activity ''{2}'', onAlarm 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.
- CWWBV3151E: 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.
- CWWBV3152E: 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.
- CWWBV3153E: The part ''{0}'' referenced in the propertyAlias definition for the property ''{1}'' and messageType ''{2}'' does not reference a valid XML schema simple 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.
- CWWBV3154E: 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.
- CWWBV3155E: 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.
- CWWBV3156E: Because the pick or receive activity ''{0}'' creates a process instance, it cannot be placed after the activity or the activities ''{1}''.
- Explanation: A pick 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 pick or receive activity so that it does not create a process instance.
- CWWBV3157E: The activity ''{0}'' is the target of the link or links ''{1}'', but it can create a process instance or it contains activities that can create a process instance.
- Explanation: A pick or receive activity that is the target of one or more links cannot create a process instance. In addition, a complex activity that contains a pick or receive activity that can create a process instance must not have any incoming links.
- User Action: Remove the incoming links or redefine the pick or receive activity so that it does not create a process instance.
- CWWBV3158W: The while activity ''{1}'' contains the pick or receive activity ''{0}'' that creates a process instance. If the condition of the while activity is false when the condition is evaluated for the first time, the process does not run correctly.
- Explanation: If the condition of the while activity is not true when it is evaluated the first time, the pick or receive activity cannot be navigated. The process does not run correctly in this case.
- User Action: Put the pick or receive activity outside of the while activity.
- CWWBV3159E: The pick or receive activity ''{0}'' that creates a process instance cannot be contained in a catch, catchAll, onMessage, onEvent, onAlarm, compensation handler, case, or otherwise element.
- Explanation: Activities that create process instances are not reachable in catch, catchAll, onMessage, onEvent, onAlarm, compensation handler, case, and otherwise elements.
- User Action: Move the pick or receive activity to a reachable position, or change the pick/receive activity so that it does not create a new process instance.
- CWWBV3160E: The flow 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 pick or receive activity that can create a process instance; 2.A complex activity that contains a pick or receive activity that can create a process instance. If a flow activity contains at least one these types of activity, all of the activities without incoming links must activities that can start processes.
- User Action: Use only activities that can start processes as the starting points in the flow activity or remove these activities from the flow activity.
- CWWBV3161E: The activity ''{0}'' does not reference the partnerLink ''null'' (used partnerLink ''{1}'').
- Explanation: For a custom or script activity, the partnerLink must be 'null'.
- User Action: Use the partnerLink 'null' for the custom or script activity.
- CWWBV3162E: 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.
- CWWBV3163E: 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.
- CWWBV3164W: 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.
- CWWBV3165W: 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.
- CWWBV3166W: 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.
- CWWBV3167E: 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.
- CWWBV3168E: 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-typed variables specified in the input element.
- User Action: Remove the inputVariable attribute from the activity.
- CWWBV3169E: 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-typed variables specified in the output element.
- User Action: Remove the outputVariable attribute from the activity.
- CWWBV3170E: The variable ''{0}'' is not defined (input or output element of activity ''{1}'', parameter number {2}).
- Explanation: The variable used in the parameter extension is not defined.
- User Action: Check that the variable name is defined correctly.
- CWWBV3171E: The message-typed variable cannot be used here (input/output element of activity ''{0}'', parameter number {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.
- CWWBV3172E: The variable ''{0}'' cannot be used multiple times in the same input or output element (input or output element of activity ''{1}'', parameter number {2}).
- Explanation: A variable can be used only once in an input or output element.
- User Action: Use another XSD-typed variable.
- CWWBV3173E: The 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.
- CWWBV3174E: The portType that is referenced in the activity ''{0}'' and in the human task ''{1}'' must be the same.
- Explanation: The portTypes must be the same.
- User Action: Ensure that the portTypes are the same.
- CWWBV3175E: The operation that is referenced in the activity ''{0}'' and in the human task ''{1}'' must be the same.
- Explanation: The operations must be the same.
- User Action: Ensure that the operations are the same.
- CWWBV3176E: The human task ''{0}'' is not an administration task (activity ''{1}'').
- Explanation: The human task that is referenced in the receive activity must be an administration task.
- User Action: Reference an administration task.
- CWWBV3177E: 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.
- CWWBV3178E: The query language ''{0}'' used in the propertyAlias is not supported. It must be one of ''{1}'' (activity ''{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.
- CWWBV3179E: 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 WebSphere Application Server scheduling service, or user-written calendars adhering to those conventions. One of these three expressions must occur in an expiration element.
- User Action: Specify a for expression, an until expression, or a timeout expression.
- CWWBV3180E: 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.
- CWWBV3181E: The expression language ''{0}'' of the transition condition is not supported. It must be one of ''{1}'' (activity ''{2}'', source element number {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.
- CWWBV3182E: 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.
- CWWBV3183E: The transition condition expression is invalid (activity ''{0}'', source element number {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-in expression 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.
- CWWBV3184E: 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-in expression 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.
- CWWBV3185E: 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, which cannot 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.
- CWWBV3186E: The parameter ''{0}'' must be removed or mapped to an element or part (activity ''{1}'', parameter number {2}).
- Explanation: A parameter have been found that 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.
- CWWBV3187E: The XSD type definition ''{0}'' was not found (activity ''{1}'', parameter number {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 inline in a WSDL interface or in an XML schema.
- User Action: Check that the XSD type definition is correctly referenced and that it is defined correctly.
- CWWBV3188E: The XSD element declaration ''{0}'' was not found (activity ''{1}'', parameter number {2}, matching part or element ''{3}'').
- Explanation: The XSD element declaration referenced in the matching part or element must be either defined inline 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.
- CWWBV3189E: The variable ''{0}'' cannot be assigned to element or part ''{1}'' because the data type does not match (activity ''{2}'', parameter number {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.
- CWWBV3190E: The element or part ''{0}'' cannot be assigned to variable ''{1}'' because the data type does not match (activity ''{2}'', parameter number {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.
- CWWBV3191E: 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.
- CWWBV3192E: The message-part ''{0}'' is not mapped to a parameter (activity ''{1}'').
- Explanation: A message-part have been found in the wrapper that does not map to a parameter.
- User Action: Remove the message-part or map it to a parameter.
- CWWBV3193E: The correlation set ''{0}'' is used already. It can only be used once (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.
- CWWBV3194E: The custom property name ''{0}'' is used already. The name can only be used once (activity ''{1}'').
- Explanation: The custom property names per activity must be unique.
- User Action: Ensure the names of all custom properties of the activity are unique.
- CWWBV3195E: The forEach activity ''{1}'' must not contain the pick or receive activity ''{0}'' that can create a process instance.
- Explanation: If at run time the finalCounterValue is less than the startCounterValue, no branch in the forEach activity will be executed and the pick or receive activity cannot be navigated. The process will not run correctly in this case.
- User Action: Put the pick or receive activity outside the forEach activity.
- CWWBV3196E: The compensation handler is not allowed (activity ''{0}'').
- Explanation: Compensation handlers are only allowed for invoke activities, but not for script, human task, or custom activities.
- User Action: Remove the compensation handler from the activity.
- CWWBV3197E: The XPath transition condition is not valid: {0} (activity ''{1}'', source element number {2}, link ''{3}'').
- Explanation: The given XPath transition condition is not syntactically valid.
- User Action: Ensure that the XPath transition condition is valid.
- CWWBV3198E: The XPath join condition is not valid: {0} (activity ''{1}'').
- Explanation: The given XPath join condition is not syntactically valid.
- User Action: Ensure that the XPath join condition is valid.
- CWWBV3199E: The XPath correlation set property propertyAlias query is not valid: {0} (activity ''{1}'', correlation set ''{2}'', propertyAlias for the property ''{3}'' and the messageType ''{4}'').
- Explanation: The given XPath query in the correlation set property propertyAlias is not syntactically valid.
- User Action: Ensure that the XPath query in the correlation set property propertyAlias is valid.
- CWWBV3200E: The XPath for- or until-expiration-expression is invalid: {0} (activity ''{1}'').
- Explanation: The given XPath for- or until-expiration-expression is not syntactically valid.
- User Action: Ensure that the XPath for- or until-expiration-expression is valid.
- CWWBV3201W: The correlation set property propertyAlias query must not be empty (activity ''{0}'', correlation set ''{1}'', propertyAlias for the property ''{2}'' and the messageType ''{3}'').
- Explanation: The given XPath query in the correlation set property propertyAlias is syntactical invalid.
- User Action: Ensure that the XPath query in the correlation set property propertyAlias is valid. Either add a query construct or remove the query element.
- CWWBV3202W: Assigning the ''{0}'' xsd:anyType typed element or the part to the {1} xsd:anySimpleType typed variable might result in a runtime error (activity {2}, parameter number {3}).
- Explanation: If the xsd:anyType and the xsd:anySimpleType do not match, a runtime error might occur.
- User Action: Edit the types so that they are compatible at runtime.
- CWWBV3203W: Assigning the ''{0}'' xsd:anyType typed variable to the ''{1}'' xsd:anySimpleType typed element or part might result in a runtime error (activity ''{2}'', parameter number {3}).
- Explanation: If the xsd:anyType and the element or part of type xsd:anySimpleType do not match, a runtime error might occur.
- User Action: Edit the types so that they are compatible at runtime.
- CWWBV3204W: The XPath in the for-expiration expression or until-expiration expression for the ''{1}'' activity is not valid: ''{0}''
- Explanation: The specified XPath expression is not supported.
- User Action: Edit the XPath for-expiration expression or until-expiration expression so that it is valid. In WebSphere Integration Developer, in the assembly editor, select the specified activity. In the Properties view, select the Expiration tab and correct the XPath expression.
- CWWBV3207W: The XPath in the for- or until-expiration-expression for ''{1}'' activity is not valid because the ''$'' notation used to refer to a variable in the ''{0}'' XPath expression or query is not supported.
- Explanation: The '$' notation to reference a variable is not supported in this XPath expression.
- User Action: Edit the XPath for-expiration expression or until-expiration-expression so that it is valid. In WebSphere Integration Developer, in the assembly editor, select the specified activity. In the Properties view, select the Expiration tab and correct the XPath expression without using the "$" notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBV3208W: The XPath join condition in the ''{1}'' activity is not valid: ''{0}''
- Explanation: The specified XPath expression is not supported.
- User Action: Ensure that the XPath join condition is valid. In WebSphere Integration Developer, in the assembly editor, select the specified activity. In the Properties view, select the Join Behaviour tab and correct the XPath expression.
- CWWBV3211W: The XPath join condition for the activity ''{1}'' is not valid because the ''$'' notation used to refer to a variable in the ''{0}'' XPath expression or query is not supported.
- Explanation: The '$' notation to reference a variable is not supported in this XPath expression.
- User Action: Edit the XPath join condition so that it is valid. In WebSphere Integration Developer, in the assembly editor, select the specified activity. In the Properties view, select the Join Behaviour tab and correct the XPath expression without using the "$" notation to refer to a variable. Instead, use the bpws:getVariableData() function
- CWWBV3212W: The XML Path Language (XPath) transition condition for the {3} link, starting from source element number {2} in the {1} activity, is not valid. The error is: {0}
- Explanation: The specified XPath expression is not supported.
- User Action: Edit the XPath transition condition so that it is valid. In WebSphere Integration Developer, in the assembly editor, select the specified link. In the Properties view, click the Details tab and correct the XPath expression.
- CWWBV3215W: The XPath transition condition for the link ''{3}'', starting from source element number {2} in activity ''{1}'', is not valid because the ''$'' notation used to refer to a variable in the ''{0}'' XPath expression or query is not supported.
- Explanation: The '$' notation to reference a variable is not supported in this XPath expression.
- User Action: Edit the XPath transition condition so that it is valid. In WebSphere Integration Developer, in the assembly editor, select the specified link. In the Properties view, select the Details tab and correct the XPath expression without using "$" notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBV3216W: The XPath correlation set property propertyAlias query is not valid: ''{0}'' (activity ''{1}'', correlation set ''{2}'', propertyAlias for the property ''{3}'' and the messageType ''{4}'').
- Explanation: The specified XPath expression is not supported.
- User Action: Edit the XPath query in the propertyAlias element so that it is valid. In WebSphere Integration Developer, in the assembly editor, in the tray on the right side of the process, select the specified correlation property. In the Properties view, correct the XPath expression by selecting the appropriate row in the table and clicking Edit.
- CWWBV3219W: The XPath correlation set property propertyAlias query is not valid: The ''$'' notation to reference a variable in the XPath expression or query ''{0}'' is not supported. (activity ''{1}'', correlation set ''{2}'', propertyAlias for the property ''{3}'' and the messageType ''{4}'').
- Explanation: The '$' notation to reference a variable is not supported in this XPath expression.
- User Action: Edit the XPath query propertyAlias element so that it is valid. In WebSphere Integration Developer, in the assembly editor, in the tray on the right side of the process, select the specified correlation property. In the Properties view, correct the XPath expression by selecting the appropriate row in the table and clicking Edit. Correct the XPath expression without using the "$" notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBV3220E: The adminTask elements cannot be used in the activity ''{0}''. These elements are only allowed in invoke and scope activities.
- Explanation: The adminTask element is only allowed in invoke and scope activities.
- User Action: Remove the adminTask elements from the activity.
- CWWBV3221W: Deprecation: The {0} expression or query language is deprecated. Use {1} instead (resource {2}).
- Explanation: The specified expression or query language is deprecated. Because the explanation simply repeats the message and doesn't add any new information, it can be deleted.
- User Action: Use the new expression or query language.
- CWWBV3222W: Deprecation: The {0} value of the pattern attribute in the correlation element {1} is deprecated. Use one of the following pattern values: {2} ({3} invoke activity).
- Explanation: The specified pattern of the correlation is deprecated. Because the explanation simply repeats the message and doesn't add any new information, it can be deleted.
- User Action: Use the new values of the pattern attribute.
- CWWBV3223E: The pattern attribute in the {0} correlation element of the {1} invoke activity cannot be used for one-way operations.
- Explanation: The pattern attribute of invoke is allowed only for request-response operations; it is not allowed when a one-way operation is invoked.
- User Action: Remove the pattern attribute.
- CWWBV3224E: The {0} variable is not defined ({1} activity, fromPart or toPart number {2}).
- Explanation: The variable that is used in the fromPart or toPart element is not defined. Because the explanation simply repeats the message and doesn't add any new information, it can be deleted.
- User Action: Correct the variable name if it is not defined correctly.
- CWWBV3225E: The message-typed variable cannot be used here ({0} activity, fromPart or toPart number {1}, {2} variable).
- Explanation: You can use only element-typed or type-typed variables in fromPart and toPart elements.
- User Action: Use an XSD-typed variable.
- CWWBV3226E: The {0} variable cannot be used multiple times in the same fromParts or toParts element ({1} activity, fromPart or toPart number {2}).
- Explanation: A variable can be used only once in a fromParts or toParts element.
- User Action: Use another XSD-typed variable.
- CWWBV3227E: The {0} message part is not mapped to a fromPart or toPart element ({1} activity).
- Explanation: A message part was found that does not map to a fromPart or toPart element.
- User Action: Remove the message part or map it to an existing fromPart or toPart.
- CWWBV3228E: The {0} fromPart or toPart must be removed or mapped to an existing message-part ({1} activity, fromPart or toPart number {2}).
- Explanation: A fromPart or toPart was found that does not map to a message part.
- User Action: Remove the fromPart or toPart or map it to a valid message part.
- CWWBV3229E: The fromParts or toParts element cannot be used for the {0} message ({1} activity).
- Explanation: The input or output message of the specified operation of the activity does not contain any message parts. Therefore, it cannot be used with the fromParts or toParts element.
- User Action: Either modify the message or use a message-type variable.
- CWWBV3230W: Assigning the {0} xsd:anyType typed message part to the {1} xsd:anySimpleType typed variable might result in a runtime error ({2} activity, fromPart/toPart number {3}).
- Explanation: If the xsd:anyType and the xsd:anySimpleType do not match, a runtime error might occur.
- User Action: Edit the types so that they are compatible at run time.
- CWWBV3231E: The {0} message part cannot be assigned to the {1} variable because the data type does not match ({2} activity, fromPart or toPart number {3}).
- Explanation: The type of the selected part and the variable are incompatible. Only compatible types can be assigned, for example, from xsd:string to xsd:string.
- User Action: Ensure that the types are compatible.
- CWWBV3232E: The {0} activity uses the parameter extension and the fromParts or toParts element. This is not supported.
- Explanation: Using the Business Process Execution Language (BPEL) fromParts or toParts element and the parameter extension on the same activity is not supported.
- User Action: Remove either the fromParts or toParts element or the parameter extension.
- CWWBV3233E: The inputVariable attribute must not be set because a toParts element is available ({0} activity, {1} inputVariable).
- Explanation: The data that is sent by this invoke or human-task activity can be identified by the input variable attribute or the toParts elements. It is only allowed to use either the input variable attribute or the toParts element.
- User Action: Remove the inputVariable attribute from the activity.
- CWWBV3234E: The outputVariable attribute must not be set because a fromParts element is available ({0} activity, {1} outputVariable).
- Explanation: The data that is received by this invoke or human-task activity can be stored in the output variable attribute or the fromParts elements. It is only allowed to use either the output variable attribute or the fromParts element.
- User Action: Remove the output variable attribute from the activity.
- CWWBV3235E: The variable must not be set because a fromParts element is available (process onEvent event number {0}, {1} variable).
- Explanation: The data that is received by this onEvent event can be stored in the onEvent variable or the fromParts elements. It is only allowed to use either the onEvent variable variable attribute or the fromParts element.
- User Action: Remove the variable attribute from the onEvent event.
- CWWBV3236E: The fromParts element must not be set because this is a one-way operation ({0} activity, {1} operation).
- Explanation: A one-way operation does not return a message.
- User Action: Do not define a fromParts element, or use a request-response operation instead of a one-way operation.
- CWWBV3237E: The transition condition is not allowed on the {0} source activity with the ''fork'' source type (source element number {1}, {2} link).
- Explanation: A source link of type 'fork' must not have set a transition condition.
- User Action: Remove the transition condition.
- CWWBV3238E: The transactionalBehavior attribute cannot be used in the ''{0}'' activity. It is allowed only in invoke, receive, and pick activities.
- Explanation: The transactionalBehavior attribute is allowed only in invoke, receive, and pick activities.
- User Action: Remove the attribute from the activity.
- CWWBV3239E: The exit 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-in expression language in the exit condition, only the values 'wpc:true', 'wpc:false' and 'wpc:otherwise' are allowed.
- User Action: Check the expression and the expression language.
- CWWBV3240E: The expression language ''{0}'' of the exit 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.
- CWWBV3241W: The XML Path Language (XPath) exit condition for the {1} activity, is not valid. The error is: {0}
- Explanation: The specified XPath expression is not supported.
- User Action: Edit the XPath exit condition so that it is valid. In WebSphere Integration Developer, in the assembly editor, select the specified action. In the Properties view, click the Details tab and correct the XPath expression.
- CWWBV3242E: The XPath exit condition is not valid: {0} (activity ''{1}'').
- Explanation: The given XPath exit condition is not syntactically valid.
- User Action: Ensure that the XPath transition condition is valid.
- CWWBV3243E: The value of the executeAt attribute on an exit condition must not be BOTH or ENTRY on initiating receives (receive ''{0}'').
- Explanation: Exit conditions witch are executed at the entry are not allowed for initiating receives.
- User Action: Ensure that a initiating receive does not define a entry condition.
- CWWBV3244E: The executeAt attribute must be set for an exit condition (activity ''{0}'').
- Explanation: Exit conditions need the executeAt to be set.
- User Action: Set the executeAt attribute
- CWWBV3245E: The otherwise transition condition expression is invalid in this context (activity ''{0}'', source element number {1}, link ''{2}'').
- Explanation: In sequential regions the otherwise transition condition only is allowed for the last link
- User Action: Either change the transition condition or move the link to the last position.
- CWWBV3246W: A variable in a XPath expression must not contain the ''.'' character. (variable ''{0}'', activity ''{1}'').
- Explanation: The usage of $ notation for variables that contain a '.' in its name is not supported and the behavior is undefined.
- User Action: Remove the '.' character from the variable name.
- CWWBV3300E: The from-specification is not allowed (assign activity ''{0}'', copy element number {1}).
- Explanation: Only specific types of from-specifications are allowed.
- User Action: Use an allowed type of from-specification or remove the copy statement.
- CWWBV3301E: The to-specification is not allowed (assign activity ''{0}'', copy element number {1}).
- Explanation: Only specific types of to-specifications are allowed.
- User Action: Use an allowed type of to-specification or remove the copy statement.
- CWWBV3302E: The from-to copy combination is not allowed (assign activity ''{0}'', copy element number {1}).
- Explanation: Only specific types of copy specifications are allowed.
- User Action: Use an allowed type of copy specification or remove the copy statement.
- CWWBV3303E: The from-variable ''{0}'' is not defined (assign activity ''{1}'', copy element number {2}).
- Explanation: The variable used in the assign activity is not defined.
- User Action: Check that the variable name is defined correctly.
- CWWBV3304E: The from-part ''{0}'' was not found (assign activity ''{1}'', copy element number {2}, variable ''{3}'').
- Explanation: The part must be defined in the messageType.
- User Action: Define the part, or use an existing part.
- CWWBV3305E: The from-partnerLink ''{0}'' was not found (assign activity ''{1}'', copy element number {2}).
- Explanation: The partnerLink referenced in the assign activity is not defined.
- User Action: Ensure that the partnerLink used is correct and that it is defined.
- CWWBV3306E: The to-variable ''{0}'' is not defined (assign activity ''{1}'', copy element number {2}).
- Explanation: The variable used in the assign activity is not defined.
- User Action: Check that the variable name is defined correctly.
- CWWBV3307E: The to-part ''{0}'' was not found (assign activity ''{1}'', copy element number {2}, variable ''{3}'').
- Explanation: The part must be defined in the messageType.
- User Action: Define the part, or use an existing part.
- CWWBV3308E: The to-partnerLink ''{0}'' was not found (assign activity ''{1}'', copy element number {2}).
- Explanation: The partnerLink referenced in the assign activity is not defined.
- User Action: Ensure that the partnerLink is correct and that it is defined.
- CWWBV3309E: The to-partnerLink ''{0}'' does not define the partnerRole role (assign activity ''{1}'', copy element number {2}).
- Explanation: PartnerLinks used in to-specifications of assign activities must define the partnerRole role.
- User Action: Define the partnerRole role for the partnerLink or use a different partnerLink.
- CWWBV3310E: The messageType of the from-variable ''{0}'' and the to-variable ''{1}'' must be the same (assign activity ''{2}'', copy element number {3}, from messageType ''{4}'', to messageType ''{5}'').
- Explanation: The messageType of the two variables must be the same.
- User Action: Ensure that both variables have the same messageType.
- CWWBV3311E: The XSD type of the from-variable ''{0}'' and the to-variable ''{1}'' must be the same (assign activity ''{2}'', copy element number {3}, from XSD type ''{4}'', to XSD 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.
- CWWBV3312E: The XSD element of the from-variable ''{0}'' and the to-variable ''{1}'' must be the same (assign activity ''{2}'', copy element number {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.
- CWWBV3313E: The type of the from-part ''{0}'' and the to-part ''{1}'' must be the same (assign activity ''{2}'', copy element number {3}).
- Explanation: The type of the two parts must be the same.
- User Action: Ensure that the parts have the same type.
- CWWBV3314E: The from-partnerLink ''{0}'' does not define the myRole role (assign activity ''{1}'', copy element number {2}).
- Explanation: PartnerLinks used in from specifications of assign activities must define the role defined by the endpointReference attribute.
- User Action: Define the myRole role for the partnerLink, use a different partnerLink, or define an endpointReference attribute.
- CWWBV3315E: The from-partnerLink ''{0}'' does not define the partnerRole role (assign activity ''{1}'', copy element number {2}).
- Explanation: PartnerLinks used in from-specifications of assign activities must define the role defined by the endpointReference attribute.
- User Action: Define the partnerRole role for the partnerLink, use a different partnerLink, or define an endpointReference attribute.
- CWWBV3316E: The portType of the from-role ''{0}'' and the to-role ''{1}'' are not the same (assign activity ''{2}'', copy element number {3}, from partnerLink ''{4}'', to partnerLink ''{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 partnerLink.
- CWWBV3317E: The message-typed from-variable ''{0}'' cannot be assigned to the type-typed or element-typed to-variable ''{1}'' (assign activity ''{2}'', copy element number {3}, from messageType ''{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.
- CWWBV3318E: The type-typed from-variable ''{0}'' cannot be assigned to the message-typed to-variable ''{1}'' (assign activity ''{2}'', copy element number {3}, from type ''{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.
- CWWBV3319E: The element-typed from-variable ''{0}'' cannot be assigned to the messageType-typed to-variable ''{1}'' (assign activity ''{2}'', copy element number {3}, from element ''{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.
- CWWBV3320E: The literal type ''{0}:{1}'' is not allowed (assign activity ''{2}'', copy element number {3}, from-specification).
- Explanation: This type of literal is not supported.
- User Action: Use another literal type.
- CWWBV3321E: A literal value is not defined (assign activity ''{0}'', copy element number {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.
- CWWBV3322E: The literal type in the from element and the part type in the to element are not the same (assign activity ''{0}'', copy element number {1}).
- Explanation: The literal type and the part type must be the same.
- User Action: Select another literal type or another part.
- CWWBV3323E: The literal value is not of the type ''{0}'' (assign activity ''{1}'', copy element number {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.
- CWWBV3324E: The XSD type definition ''{0}'' was not found (assign activity ''{1}'', copy element number {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 inline 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.
- CWWBV3325E: The XSD type definition ''{0}'' is not valid (assign activity ''{1}'', copy element number {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.
- CWWBV3326E: The query language ''{0}'' used in the propertyAlias is not supported. It must be one of ''{1}'' (assign activity ''{2}'', copy element number {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.
- CWWBV3327E: Part ''{0}'' referenced in the propertyAlias definition for property ''{1}'' and messageType ''{2}'' must reference a valid XML schema simple type (assign activity ''{3}'', copy element number {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.
- CWWBV3328E: The type of part ''{0}'' of messageType ''{1}'' and the type of the property ''{2}'' must be the same XML schema type (assign activity ''{3}'', copy element number {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.
- CWWBV3329E: The query language ''{0}'' is not supported. It must be one of ''{1}'' (assign activity ''{2}'', copy element number {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.
- CWWBV3330E: The query language ''{0}'' is not supported. It must be one of ''{1}'' (assign activity ''{2}'', copy element number {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.
- CWWBV3331E: The expression language ''{0}'' of the expression element is not supported. It must be one of ''{1}'' (assign activity ''{2}'', copy element number {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.
- CWWBV3332E: The XSD-typed variable ''{0}'' cannot be used in combination with a property specification. Use a message-typed variable (assign activity ''{1}'', copy element number {2}).
- Explanation: Properties can be specified only for message-typed variables.
- User Action: Use a message-typed variable or remove the property specification.
- CWWBV3333E: The property ''{0}'' was not found (assign activity ''{1}'', copy element number {2}).
- Explanation: The property used must be defined.
- User Action: Ensure the referenced property is defined or refer to another defined property.
- CWWBV3334E: A matching propertyAlias definition is needed for the property ''{0}'' and the messageType ''{1}'' (assign activity ''{2}'', copy element number {3}).
- Explanation: A propertyAlias definition is needed to map the parts of a messageType to the property.
- User Action: Define the propertyAlias.
- CWWBV3335E: The part must be set in the propertyAlias for the property ''{0}'' and the messageType ''{1}'' (assign activity ''{2}'', copy element number {3}).
- Explanation: The part must be set in the propertyAlias.
- User Action: Set the part.
- CWWBV3336E: The part ''{0}'' referenced in the propertyAlias for the property ''{1}'' and the messageType ''{2}'' was not found (assign activity ''{3}'', copy element number {4}).
- Explanation: The part must be defined for the messageType.
- User Action: Define the part, or use an existing part in the propertyAlias.
- CWWBV3337E: Multiple propertyAlias definitions were found for the property ''{0}'' and the messageType ''{1}'' (assign activity ''{2}'', copy element number {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.
- CWWBV3338E: The XSD type definition ''{0}'' was not found (assign activity ''{1}'', copy element number {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 inline 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.
- CWWBV3339E: The XSD element declaration ''{0}'' was not found (assign activity ''{1}'', copy element number {2}, variable ''{3}'', part ''{4}'').
- Explanation: The XSD element declaration that is referenced must be defined inline 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.
- CWWBV3340E: The XSD-typed part ''{0}'' cannot be assigned to the message-typed to-variable ''{1}'' (assign activity ''{2}'', copy element number {3}).
- Explanation: An XSD-typed part can only be assigned to an 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 an XSD-typed variable on the to side.
- CWWBV3341E: The message-typed from-variable ''{0}'' cannot be assigned to the XSD-typed part ''{1}'' (assign activity ''{2}'', copy element number {3}).
- Explanation: A message-typed variable can only be assigned to another message-typed variable.
- User Action: Either select a message-typed variable and an XSD-typed part on the from side, or select a message-typed variable on the to side.
- CWWBV3342E: The XSD type definition ''{0}'' was not found (assign activity ''{1}'', copy element number {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 inline 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.
- CWWBV3343E: The type of the from-variable ''{0}'' and the to-variable ''{1}'' must be the same (assign activity ''{2}'', copy element number {3}, from XSD type ''{4}'', to XSD element ''{5}'').
- Explanation: The type of the two variables must be the same.
- User Action: Ensure that both variables have the same type.
- CWWBV3344E: The type of the from-variable ''{0}'' and the to-variable ''{1}'' must be the same (assign activity ''{2}'', copy element number {3}, from XSD element ''{4}'', to XSD type ''{5}'').
- Explanation: The type of the two variables must be the same.
- User Action: Ensure that both variables have the same type.
- CWWBV3345E: The XSD type of the from-part ''{0}'' and the to-variable ''{1}'' must be the same (assign activity ''{2}'', copy element number {3}, from XSD type ''{4}'', to XSD 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.
- CWWBV3346E: The XSD type of the from-variable ''{0}'' and the to-part ''{1}'' must be the same (assign activity ''{2}'', copy element number {3}, from XSD type ''{4}'', to XSD 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.
- CWWBV3347E: The XSD type of the from-part ''{0}'' and the to-part ''{1}'' must be the same (assign activity ''{2}'', copy element number {3}, from XSD type ''{4}'', to XSD 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.
- CWWBV3348E: The from-query is not valid: {0} (assign activity ''{1}'', copy element number {2}).
- Explanation: The given XPath from-query is not syntactically valid.
- User Action: Ensure that the XPath from-query is valid.
- CWWBV3349E: The to-query is not valid: {0} (assign activity ''{1}'', copy element number {2}).
- Explanation: The given XPath to-query is not syntactically valid.
- User Action: Ensure that the XPath to-query is valid.
- CWWBV3350E: The from property propertyAlias query is not valid: {0} (assign activity ''{1}'', copy element number {2}, propertyAlias for the property ''{3}'' and the messageType ''{4}'').
- Explanation: The given XPath query in the from property propertyAlias is not syntactically valid.
- User Action: Ensure that the XPath query in the from property propertyAlias is valid.
- CWWBV3351E: The to property propertyAlias query is not valid: {0} (assign activity ''{1}'', copy element number {2}, propertyAlias for the property ''{3}'' and the messageType ''{4}'').
- Explanation: The given XPath query in the to property propertyAlias is not syntactically valid.
- User Action: Ensure that the XPath query in the to property propertyAlias is valid.
- CWWBV3352E: The from-expression is not valid: {0} (assign activity ''{1}'', copy element number {2}).
- Explanation: The given XPath from-expression is not syntactically valid.
- User Action: Ensure that the XPath from-expression is valid.
- CWWBV3353W: The from property propertyAlias query must not be empty (assign activity ''{0}'', copy element number {1}, propertyAlias for the property ''{2}'' and the messageType ''{3}'').
- Explanation: The given XPath query in the from property propertyAlias is not syntactically valid.
- User Action: Ensure that the XPath query in the from property propertyAlias is valid. Either add a query construct or remove the query element.
- CWWBV3354W: The to property propertyAlias query must not be empty (assign activity ''{0}'', copy element number {1}, propertyAlias for the property ''{2}'' and the messageType ''{3}'').
- Explanation: The given XPath query in the to property propertyAlias is not syntactically valid.
- User Action: Ensure that the XPath query in the to property propertyAlias is valid. Either add a query construct or remove the query element.
- CWWBV3355W: Assigning the xsd:anyType typed from-variable ''{0}'' to the xsd:anySimpleType typed to-variable ''{1}'' might result in a runtime error (assign activity ''{2}'', copy element number {3}, from XSD type ''{4}'', to XSD type ''{5}'').
- Explanation: Assigning an xsd:anyType typed variable to an xsd:anySimpleType typed variable might result in a runtime error.
- User Action: Ensure that both variables have a compatible XSD type.
- CWWBV3356W: In assign activity ''{1}'', the from-expiration expression in copy element number {2} is not valid: ''{0}''
- Explanation: The specified XPath expression is not supported.
- User Action: Edit the XPath from-expression so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified activity. In the Properties view, select the Details tab. In the table, select the from-expiration expression in the specified copy element and, from the drop-down menu, select XPath Expression. Correct the XPath expression.
- CWWBV3359W: In the ''{1}'' assign activity, copy element number {2}, the from-expression is not valid: The ''$'' notation that is used to refer to a variable in the ''{0}'' XPath expression or query is not supported. (assign activity ''{1}'', copy element number {2})
- Explanation: The '$' notation to reference a variable is not supported in this XPath expression.
- User Action: Edit the XPath from-expression so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified activity. In the Properties view, select the Details tab. In the table, select the from-expiration expression in the specified copy element and, from the drop-down menu, select XPath Expression. Correct the XPath expression without using the "$" notation to refer to a variable. Instead, use the bpws:getVariableData()XPath function.
- CWWBV3360W: In the ''{1}'' assign activity, copy element number {2}, the XPath query used in the assign from property ''{3}'' is not valid: ''{0}'' (messageType {4}).
- Explanation: The specified XPath expression is not supported.
- User Action: Ensure that the XPath query in the from property propertyAlias is valid. In WebSphere Integration Developer, in the business process editor, select the specified assign activity. In the Properties view, select the Details tab. In the table, right-click the from-expression in the specified copy element and select Edit Query. Correct the XPath expression.
- CWWBV3363W: In the ''{2}'' assign activity, copy element number {3}, the XPath query used in the assign from property ''{4}'' is not valid because the ''$'' notation that is used to refer to a variable in the ''{0}'' XPath expression or query is not supported. (assign activity ''{1}'', copy element number {2}, propertyAlias for the property ''{3}'' and the messageType ''{4}'').
- Explanation: The '$' notation to reference a variable is not supported in this XPath expression.
- User Action: Ensure that the XPath query in the from property propertyAlias is valid. In WebSphere Integration Developer, in the business process editor, select the specified assign activity. In the Properties view, select the Details tab. In the table, right-click the specified copy element and select Edit Query. Correct the XPath expression without using the "$" notation to refer to a variable. Instead, use the bpws:getVariableData()XPath function.
- CWWBV3364W: In the ''{1}'' assign activity, copy element number {2}, the from query is not valid: ''{0}''
- Explanation: The specified XPath expression is not supported.
- User Action: Ensure that the XPath from-query is valid. In WebSphere Integration Developer, in the business process editor, select the specified activity. In the Properties view, select the Details tab. In the table, right-click the from-expression in the specified copy element and select Edit Query. Correct the XPath expression.
- CWWBV3367W: In the ''{1}'' assign activity, copy element number {2}, the from query is not valid because the ''$'' notation that is used to refer to a variable in the ''{0}'' XPath expression or query is not supported. (assign activity ''{1}'', copy element number {2}).
- Explanation: The '$' notation to reference a variable is not supported in this XPath expression.
- User Action: Ensure that the XPath from-query is valid. In WebSphere Integration Developer, in the business process editor, select the specified assign activity. In the Properties view, select the Details tab. In the table, right-click the from-expression in the specified copy element and select Edit Query. Correct the XPath query without using the "$" notation to refer to a variable. Instead, use the bpws:getVariableData()XPath function.
- CWWBV3368W: In the ''{1}'' assign activity, copy element number {2}, the XPath query used in the ''{3}'' assign-to property of a variable is not valid: ''{0}'' messageType ''{4}'').
- Explanation: The specified XPath expression is not supported.
- User Action: Ensure that the XPath query in the to property propertyAlias is valid. In WebSphere Integration Developer, in the business process editor, select the specified assign activity. In the Properties view, select the Details tab. In the table, right-click the to-expression in the specified copy element and select Edit Query. Correct the XPath expression.
- CWWBV3371W: In the ''{2}'' assign activity, copy element number {3}, the XPath query used in the ''{4}'' assign-to property of a variable is not valid because the ''$'' notation that is used to refer to a variable in the {0} XPath expression or query is not supported. (assign activity ''{1}'', copy element number {2}, propertyAlias for the property ''{3}'' and the messageType ''{4}'').
- Explanation: The '$' notation to reference a variable is not supported in this XPath expression.
- User Action: Edit the XPath query in the assign-to property propertyAlias so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified assign activity. In the Properties view, select the Details tab. In the table, right-click the to-expression in the specified copy element and select Edit Query. Correct the XPath query without using the "$" notation to refer to a variable. Instead, use the bpws:getVariableData()XPath function.
- CWWBV3372W: In the ''{1}'' assign activity, copy element number {2}, the to query is not valid: ''{0}''
- Explanation: The specified XPath expression is not supported.
- User Action: Edit the XPath to query so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified assign activity. In the Properties view and select the Details tab. In the table, right-click the to-expression in the specified copy element and select Edit Query. Correct the XPath expression.
- CWWBV3375W: In the ''{1}'' assign activity, copy element number {2}, the to query is not valid because the ''$'' notation that is used to refer to a variable in the ''{0}'' XPath expression or query is not supported.
- Explanation: The '$' notation to reference a variable is not supported in this XPath expression.
- User Action: Edit that the XPath to query so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified assign activity. In the Properties view, select the Details tab. In the table, right-click the to-expression in the specified copy element and select Edit Query. Correct the XPath query without using the "$" notation to refer to a variable. Instead, use the bpws:getVariableData()XPath function.
- CWWBV3376W: Deprecation: In the {0} assign activity, copy element number {1}, the ''from'' element uses the deprecated schema for literal values.
- Explanation: The 'Assign from a literal' value requires a wrapper element called 'literal'.
- User Action: Add a 'literal' element to the 'from' element.
- CWWBV3378E: In the ''{0}'' assign activity, copy element number {1}, the from element uses both schemas for literal values. This is not supported.
- Explanation: The Assign from a literal requires only a wrapper element called literal.
- User Action: Remove the literal value, which is not wrapped by a literal element.
- CWWBV3400E: 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 completed normally when a fault occurs. Thus, compensate activities 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.
- CWWBV3401E: The referenced scope or invoke activity ''{0}'' was not found or can not be referenced. It must be defined in the process and contained in the scope (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 handler or compensation handler in which the compensate activity is contained. Additionally, the referenced scope or invoke activity must be immediately contained in this scope. For example, suppose this scope is Scope1 and it contains Scope2, which contains Scope3. Scope3 normally cannot be referenced. Scope3 can be referenced only if Scope2 is not compensable. However, other structured activities can come between these scope activities. For example, Scope2 can be referenced from the compensate activity if Scope1 contains Flow1, which then contains Scope2.
- User Action: Ensure that the scope or invoke activity is immediately contained in this scope and is defined in the process.
- CWWBV3402E: 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 place a compensate activity in the fault handler or compensation handler of the invoke activity.
- User Action: Remove the compensate activity from the invoke activity.
- CWWBV3403E: 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.
- CWWBV3404E: The referenced invoke activity ''{0}'' does not have a fault or compensation handler set (compensate activity ''{1}'').
- Explanation: The referenced invoke activity has no fault or compensation handler set. Therefore, an enclosing scope activity for the invoke activity will not be generated. Thus the invoke activity cannot be compensated.
- User Action: Set a fault or compensation handler for the referenced invoke activity, or reference a different scope or invoke activity.
- CWWBV3405E: The referenced invoke activity ''{0}'' does not have a fault or compensation handler or an undo action set (compensate activity ''{1}'').
- Explanation: The referenced invoke activity has no fault or compensation handler or undo action set. Therefore, an enclosing scope activity for the invoke activity will not be generated. Thus the invoke activity cannot be compensated.
- User Action: Set a fault or compensation handler or an undo action for the referenced invoke activity, or reference a different scope or invoke activity.
- CWWBV3406E: The activity name ''{0}'' must be unique (referenced in compensate activity ''{1}'').
- Explanation: The compensate activity references activities that have to be compensated. This reference is done by name, so it must be clear which activity is referenced. The activity name must be unique.
- User Action: Ensure that the activity name is used only once.
- CWWBV3407E: The compensate activity cannot be contained inside the fault handler of a non-compensable scope activity (compensate activity ''{0}'', scope activity ''{1}'').
- Explanation: The given scope activity has set the compensable attribute to 'no'. The given compensate activity is contained in the fault handler of that scope activity. Because the scope activity is not compensable, it is invisible for compensation. Therefore, a compensate activity must not be contained in the fault handler of the scope activity.
- User Action: Remove the compensate activity from the non-compensable scope activity.
- CWWBV3408W: Deprecation: The use of the scope attribute on the {0} compensate activity is deprecated. Use the compensateScope activity instead.
- Explanation: The compensateScope activity replaces the scope attribute of the compensate activity.
- User Action: Replace the compensate activity with the compensateScope activity.
- CWWBV3409E: The compensateScope activity can be used only inside a fault handler or a compensation handler ({0} compensate activity).
- Explanation: compensateScope activities are used to invoke the compensation handlers of scope activities that completed normally when a fault occurs. Therefore, compensateScope activities can be used only inside fault handlers or compensation handlers.
- User Action: Remove the compensateScope activity, or move it to a fault handler or a compensation handler.
- CWWBV3410E: The {0} referenced scope or invoke activity was not found or cannot be referenced. It must be defined in the process and contained in the scope ({1} compensateScope activity).
- 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 one that defines a fault handler or compensation handler in which the compensateScope activity is contained. Additionally, the referenced scope or invoke activity must be immediately contained in this scope. For example, if this scope is Scope1 and it contains Scope2, which contains Scope3, Scope3 normally cannot be referenced. Scope3 can be referenced only if Scope2 is not compensable. However, other structured activities can come between these scope activities. For example, Scope2 can be referenced from the compensateScope activity if Scope1 contains Flow1, which then contains Scope2.
- User Action: Ensure that the scope or invoke activity is immediately contained in this scope and is defined in the process.
- CWWBV3411E: The compensateScope activity cannot be contained inside an invoke activity ({0} compensateScope activity, {1} invoke activity).
- Explanation: Although the invoke activity is a basic activity, it cannot contain other scope or invoke activities that can be compensated. Therefore, do not place a compensateScope activity in the fault handler or compensation handler of the invoke activity.
- User Action: Remove the compensateScope activity from the invoke activity.
- CWWBV3412E: The {0} referenced scope activity cannot be compensated ({1} compensateScope activity).
- Explanation: The compensable attribute of the referenced scope activity is set to 'no'. Therefore, the scope activity cannot be compensated.
- User Action: Set the compensate attribute of the referenced scope activity to 'yes', or reference another scope activity.
- CWWBV3413E: No fault or compensation handler is set on the {0} referenced invoke activity ({1} compensateScope activity).
- Explanation: Without a fault or compensation handler set on the referenced invoke activity, an enclosing scope activity for the invoke activity is not generated. Therefore, the invoke activity cannot be compensated.
- User Action: Set a fault or compensation handler for the referenced invoke activity, or reference another scope or invoke activity.
- CWWBV3414E: No fault or compensation handler or undo action is set on the {0} referenced invoke activity ({1} compensateScope activity).
- Explanation: Without a fault or compensation handler or undo action set on the referenced invoke activity, an enclosing scope activity for the invoke activity is not generated. Therefore, the invoke activity cannot be compensated.
- User Action: Set a fault or compensation handler or an undo action for the referenced invoke activity, or reference another scope or invoke activity.
- CWWBV3415E: The activity name {0} must be unique (referenced in the {1} compensateScope activity).
- Explanation: The compensateScope activity references activities that must be compensated. This reference is done by name, so it must be clear which activity is referenced. The activity name must be unique.
- User Action: Ensure that the activity name is used only once.
- CWWBV3416E: The compensateScope activity cannot be contained in the fault handler of a non-compensable scope activity ({0} compensateScope activity, {1} scope activity).
- Explanation: The specified scope activity set the compensable attribute to 'no'. The specified compensate activity is contained in the fault handler of that scope activity. Because the scope activity is not compensable, it is invisible for compensation. Therefore, a compensate activity must not be contained in the fault handler of the scope activity.
- User Action: Remove the compensateScope activity from the non-compensable scope activity.
- CWWBV3600E: The link ''{0}'' cannot cross the boundary of the while activity ''{1}'' (link defined in the flow activity ''{2}'').
- Explanation: A link crosses the boundary of a while activity. This means that the source activity is nested in a while activity 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.
- CWWBV3601E: The link ''{0}'' cannot be used in the while activity ''{1}'', because it is defined outside of the while activity (link defined in the flow activity ''{2}'').
- Explanation: A link is used in a while 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.
- CWWBV3602E: The link ''{0}'' cannot cross the boundary of the compensation handler of the scope activity ''{1}'' (link defined in the flow activity ''{2}'').
- Explanation: A link crosses the boundary of a compensation handler. This means that the source activity is nested in a compensation 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.
- CWWBV3603E: The link ''{0}'' cannot be used in the compensation handler of the scope activity ''{1}'', because it is defined outside of the scope activity (link defined in the flow 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.
- CWWBV3604E: The link ''{0}'' cannot cross the boundary of the compensation handler of the invoke activity ''{1}'' (link defined in the flow activity ''{2}'').
- Explanation: A link crosses the boundary of a compensation handler. This means that the source activity is nested in a compensation 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.
- CWWBV3605E: The link ''{0}'' cannot be used in the compensation handler of the invoke activity ''{1}'', because it is defined outside of the invoke activity (link defined in the flow 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.
- CWWBV3606E: The link ''{0}'' cannot cross the boundary of the event handler of the scope activity ''{1}'' (link defined in the flow 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.
- CWWBV3607E: 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 flow 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.
- CWWBV3608E: The inbound link ''{0}'' cannot cross the boundary of the fault handler of the scope activity ''{1}'' (link defined in the flow 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.
- CWWBV3609E: 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 flow 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.
- CWWBV3610E: 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 flow 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.
- CWWBV3611E: The inbound link ''{0}'' cannot cross the boundary of the fault handler of the invoke activity ''{1}'' (link defined in the flow 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.
- CWWBV3612E: 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 flow 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.
- CWWBV3613E: The link ''{0}'' cannot cross the boundary of two serializable scope activities (source scope activity ''{1}'', target scope activity ''{2}'', link defined in the flow 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.
- CWWBV3614E: The activity ''{0}'' cannot be part of a cycle.
- Explanation: The cycle prevents the process from ending.
- User Action: Remove the cycle.
- CWWBV3615E: The link ''{0}'' cannot be part of a cycle.
- Explanation: The cycle prevents the process from ending.
- User Action: Remove the cycle.
- CWWBV3616E: The source activity is missing for the link ''{0}'' (link defined in the flow 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.
- CWWBV3617E: The target activity is missing for the link ''{0}'' (link defined in the flow 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.
- CWWBV3618E: The link ''{0}'' is not used (link defined in the flow activity ''{1}'').
- Explanation: All of the links defined in a flow 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.
- CWWBV3619E: The link ''{0}'' has more than one source activity: ''{1}'' (link defined in the flow 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.
- CWWBV3620E: The {0} link has the following target activities: {1} (link defined in the {2} flow activity).
- 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.
- CWWBV3621E: The source type of the {0} activity must not be {2} (source of standard flow link {1}).
- Explanation: All links that are defined in a standard flow activity must not have the source type attribute set.
- User Action: Remove the type attribute.
- CWWBV3622E: The target type of {0} activity must not be {2} (target of standard flow link {1}).
- Explanation: All links that are defined in a standard flow activity must not have the target type attribute set.
- User Action: Remove the type attribute.
- CWWBV3623E: The link ''{0}'' cannot cross the boundary of the forEach activity ''{1}'' (link defined in the flow activity ''{2}'').
- Explanation: A link crosses the boundary of a forEach activity. This means that the source activity is nested in a forEach activity 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.
- CWWBV3624E: The link ''{0}'' cannot be used in the forEach activity ''{1}'', because it is defined outside of the forEach activity (link defined in the flow activity ''{2}'').
- Explanation: A link is used in a forEach 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.
- CWWBV3625W: The type attribute of the sources or targets element is deprecated ({0} activity, {1} link).
- Explanation: The wpc:type is not supported on the Business Process Execution Language (BPEL) flow.
- User Action: Remove the type attribute.
- CWWBV3650E: The extension activity ''{0}'' is not supported. Only generalized flow activities are supported.
- Explanation: Only the generalized flow activity is supported as an extension activity.
- User Action: Either remove the extension activity or change it to an generalized flow activity.
- CWWBV3651E: The source type of the {0} activity must be one of split, fork, or ior (source of the {1} generalized flow link).
- Explanation: All links that are defined in a generalized flow activity must have a source activity of type split, fork, or ior.
- User Action: Either define another source activity for the link, or change the source type to split, fork, or ior.
- CWWBV3652E: The target type of the {0} activity must be merge, join, or ior (target of the {1} generalized flow link).
- Explanation: All links that are defined in a generalized flow activity must have a target activity of type merge, join, or ior.
- User Action: Either define another target activity for the link, or change the target type to merge, join, or ior.
- CWWBV3653E: The source activity ''{0}'' of the generalized flow link ''{1}'' must be directly nested in the generalized flow activity ''{2}''.
- Explanation: All links defined in an generalized flow activity must connect activities which are directly nested in the generalized flow activity.
- User Action: Either remove the link or move the activity so that it is directly nested in the generalized flow activity.
- CWWBV3654E: The target activity ''{0}'' of the generalized flow link ''{1}'' must be directly nested in the generalized flow activity ''{2}''.
- Explanation: All links defined in an generalized flow activity must connect activities which are directly nested in the generalized flow activity.
- User Action: Either remove the link or move the activity so that it is directly nested in the generalized flow activity.
- CWWBV3655E: The generalized flow activity ''{0}'' must contain exactly one start activity. Found start activities: ''{1}''.
- Explanation: A start activity is an activity that is not the target of links. An generalized flow activity must contain exactly one start activity.
- User Action: In case there is no start activity defined, add one. If no separate start activity is needed, an empty activity can be used as start activity. In case there are multiple start activities defined, remove them except one.
- CWWBV3656E: The generalized flow activity ''{0}'' must contain at least one end activity.
- Explanation: An end activity is an activity which is not the source of links. An generalized flow activity must contain at least one end activity.
- User Action: Define an end activity. If no separate end activity is needed, an empty activity can be used as end activity.
- CWWBV3657E: The activity ''{0}'' cannot be reached from the start activity ''{1}'' of the generalized flow activity ''{2}''.
- Explanation: Every activity directly contained in the generalized flow activity must be reachable from the start activity of the generalized flow activity. Otherwise, the generalized flow activity will contain multiple parallel graphs. Parallelism is currently not supported in generalized flow activities.
- User Action: Ensure the given activity is explicitly or implicitly connected with the start activity of the generalized flow activity.
- CWWBV3658E: An end activity cannot be reached from the activity ''{0}'' of the generalized flow activity ''{1}''. Connect the activity to an end activity.
- Explanation: Every activity directly contained in the generalized flow activity must be able to navigate to an end activity of the generalized flow activity. If an activity is navigated that is not explicitly or implicitly connected with an end activity, the generalized flow activity cannot be completed without an error.
- User Action: Ensure the given activity is explicitly or implicitly connected with an end activity of the generalized flow activity.
- CWWBV3659E: The activity ''{0}'' must not specify a join condition, because it is part of a graph.
- Explanation: In an generalized flow activity, no activities will be executed in parallel, even if an activity is the source of multiple links. Thus, if an activity is the target of multiple links and only one of the links is navigated, the activity is executed. Because parallelism is not supported, the other links cannot be navigated. Consequently, all activities that are part of a graph must not specify a join condition.
- User Action: Remove the join condition.
- CWWBV3660W: The generalized flow link ''{0}'' can never be navigated because the previously referenced generalized flow link ''{1}'' does not specify a transition condition (activity ''{2}'').
- Explanation: If no explicit transition condition is set, the default 'true' is used. Because in an generalized flow activity only the first link evaluating to 'true' will be navigated, the following links will never be navigated.
- User Action: Either remove the link or specify a transition condition for the previous link.
- CWWBV3661E: The link ''{0}'' cannot cross the boundary of the generalized flow activity ''{1}'' (link defined in the flow activity ''{2}'').
- Explanation: A link crosses the boundary of an generalized flow activity. This means that the source activity is nested in an generalized flow activity 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.
- CWWBV3662E: The link ''{0}'' cannot be used in the generalized flow activity ''{1}'', because it is defined outside of the generalized flow activity (link defined in the flow activity ''{2}'').
- Explanation: A link is used in an generalized flow 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.
- CWWBV3663E: The {0} flow activity is the source of multiple links but has no source type specified.
- Explanation: A flow activity that is the source of multiple links must define a source type. Possible values are split, fork, and ior.
- User Action: Specify a source type.
- CWWBV3664E: The {0} flow activity is the target of multiple links but has no target type specified.
- Explanation: A flow activity which is the target of multiple links must define a target type. Possible values are merge, join, and ior.
- User Action: Specify a target type.
- CWWBV3665W: The region analysis of ''{0}'' flow activity is failing.
- Explanation: The region analysis cannot be used.
- User Action: Check the technical information databases on the WebSphere Process Server support site at http://www.ibm.com/software/integration/wps/support/. If you cannot find the information that you need to solve the problem, contact your technical support provider or again refer to the WebSphere Process Server support site for information about IBM Software Support and Services
- CWWBV3666E: The fault source must contain a catch element or a catchAll element. (source activity ''{0}'', number of fault source ''{1}'')
- Explanation: A fault source must have one catch element or one catchAll element.
- User Action: Define a catch element, or a catchAll element, or remove the fault source.
- CWWBV3667E: The fault source must not contain more than one catch element or a catchAll element. (source activity ''{0}'', number of fault source ''{1}'')
- Explanation: A fault source must have only one catch element or one catchAll element.
- User Action: Remove a catch element, or a catchAll element, or remove the fault source.
- CWWBV3668E: There must not be more than one fault source with catch all. (source activity ''{0}'').
- Explanation: A activity may only define one fault source with catch all.
- User Action: Ensure that there exist only one fault source with catch all.
- CWWBV3669E: The fault source requires either a faultName attribute, a faultVariable attribute or both (source activity ''{0}'', number of fault source ''{1}'')
- Explanation: The faultName attribute, faultVariable attribute or both must be set for a fault source.
- User Action: Set the faultName attribute faultVariable attribute or both.
- CWWBV3670E: The fault variable ''{0}'' on the fault source cannot be found. (source activity ''{1}'', number of fault source ''{2}'')
- Explanation: The fault variablemust be declared on a parent scope.
- User Action: Ensure that the fault variable is set.
- CWWBV3671E: The source activity of a fault link must not be a structured activity (except the scope activity), a throw activity or a rethrow activity. (source activity ''{0}'').
- Explanation: A source activity can be each basic activity (but not throw and re-throw) and the scope activity.
- User Action: Correct the source activity.
- CWWBV3672E: One region of generalized flow ''{0}'' is not mappable. (participating activities ''{1}'').
- Explanation: The generalized flow cannot be executed in the runtime.
- User Action: Correct region types of your generalized flow.
- CWWBV3673E: The link or activity ''{0}'' is participating on a parallel region which contains a cycle (generalized flow ''{1}'').
- Explanation: Cycles in parallel regions are not supported.
- User Action: Remove either the cycle or change the type of the region.
- CWWBV3674W: One region of generalized flow ''{0}'' is may result in exceptions during runtime. (participating activities ''{1}'')
- Explanation: The generalized flow may result in exceptions in the runtime.
- User Action: Correct region types of your generalized flow.
- CWWBV3675W: The fault source requires a fault variable as the defined fault ''{0}'' has associated fault data. (source activity ''{1}'', number of fault source ''{2}'')
- Explanation: If the fault has associated fault data, a catch activity specifying a matching fault name value and a no fault variable the default catchAll handler will be selected if present during runtime.
- User Action: Ensure that the correct fault variable is set.
- CWWBV3676W: The fault name ''{0}'' does not exist in the operation ''{1}''. (source activity ''{2}'', number of fault source ''{3}'')
- Explanation: The fault needs to be specified on the operation. Otherwise the default catchAll handler is selected if present during runtime.
- User Action: Ensure that the correct fault exist on the operation.
- CWWBV3677W: The fault variable ''{0}'' has not the message type of fault data of the fault name ''{1}'' (source activity ''{2}'', number of fault source ''{3}'')
- Explanation: The variable must be of the fault data message type .
- User Action: Ensure that the variable has the message type of the fault.
- CWWBV3700E: The partnerLink ''{0}'' referenced in the undo action was not found (invoke activity ''{1}'').
- Explanation: The partnerLink referenced in the undo action of the invoke activity is not defined.
- User Action: Ensure that the partnerLink is correct and that it is defined.
- CWWBV3701E: 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.
- CWWBV3702E: 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.
- CWWBV3703E: 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.
- CWWBV3704E: 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.
- CWWBV3705E: 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.
- CWWBV3706E: 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.
- CWWBV3707E: 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.
- CWWBV3708E: 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.
- CWWBV3710E: 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.
- CWWBV3711E: The undo action partnerLink ''{0}'' does not define the partnerRole role (invoke activity ''{1}'').
- Explanation: PartnerLinks used in invoke activities must define the partnerRole role.
- User Action: Define the partnerRole role for the partnerLink or use a different partnerLink.
- CWWBV3712E: The portType attribute referenced in the undo action of the invoke activity ''{0}'' and in the partnerRole role ''{1}'' must be the same (partnerLink ''{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 the partnerRole role in the partnerLink.
- User Action: Ensure that the portType attributes are the same.
- CWWBV3713E: The partnerLink ''{0}'' does not define the partnerRole role (invoke activity ''{1}'').
- Explanation: PartnerLinks used in invoke activities must define the partnerRole role.
- User Action: Define the partnerRole role for the partnerLink or use a different partnerLink.
- CWWBV3714E: The inputVariable attribute of the undo action must not be set because an undo action input element 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-typed variables specified in the input element.
- User Action: Remove the inputVariable attribute from the undo action.
- CWWBV3715E: The variable ''{0}'' used in the undo action is not defined (input element of the undo action of invoke activity ''{1}'', parameter number {2}).
- Explanation: The variable used in the parameter extension is not defined.
- User Action: Check that the variable name is defined correctly.
- CWWBV3716E: The message-typed variable cannot be used here (input element of the undo action of invoke activity ''{0}'', parameter number {1}, variable ''{2}'').
- Explanation: You can use only element-typed or type-typed variables in input elements.
- User Action: Use an XSD-typed variable.
- CWWBV3717E: The variable ''{0}'' cannot be used multiple times in the same input element (input element of the undo action of invoke activity ''{1}'', parameter number {2}).
- Explanation: A variable can be used only once in an input element.
- User Action: Use another XSD-typed variable.
- CWWBV3718E: 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.
- CWWBV3719E: The undo action must specify a variable if the invoke activity specifies a variable by using the parameter extension (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.
- CWWBV3720E: 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, which cannot 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.
- CWWBV3721E: The parameter ''{0}'' is not mapped to an element or part (undo action of invoke activity ''{1}'', parameter number {2}).
- Explanation: A parameter has been found that 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.
- CWWBV3722E: The XSD type definition ''{0}'' was not found (undo action of invoke activity ''{1}'', parameter number {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 inline in a WSDL interface or in an XML schema.
- User Action: Check that the XSD type definition is correctly referenced and that it is defined correctly.
- CWWBV3723E: The XSD element declaration ''{0}'' was not found (undo action of invoke activity ''{1}'', parameter number {2}, matching part or element ''{3}'').
- Explanation: The XSD element declaration referenced in the matching part or element must be either defined inline 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.
- CWWBV3724E: 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 number {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.
- CWWBV3725E: The XSD element ''{0}'' is not mapped to a parameter (undo action of invoke activity ''{1}'').
- Explanation: An element has been found in the wrapper that does not map to a parameter.
- User Action: Remove the element or map it to a parameter.
- CWWBV3726E: The message-part ''{0}'' is not mapped to a parameter (undo action of invoke activity ''{1}'').
- Explanation: A message-part has been found in the wrapper that does not map to a parameter.
- User Action: Remove the message-part or map it to a parameter.
- CWWBV3727W: In the undo action of the ''{2}'' invoke activity, parameter number {3}, assigning the ''{0}'' xsd:anyType typed variable to the ''{1}'' xsd:anySimpleType typed element or part might cause a runtime error.
- Explanation: The xsd:anyType variable and the xsd:anySimpleType element or part must match.
- User Action: Edit the xsd:anyType and the xsd:anySimpleType so that they match.
- CWWBV3800E: The XSD-typed variable cannot be used here (pick activity ''{0}'', onMessage element number {1}, variable ''{2}'').
- Explanation: Only WSDL-typed variables are allowed for pick activities.
- User Action: Use a WSDL-typed variable.
- CWWBV3801E: The partnerLink ''{0}'' was not found (pick activity ''{1}'', onMessage element number {2}).
- Explanation: The partnerLink referenced in the activity is not defined.
- User Action: Ensure that the partnerLink is correct and that it is defined.
- CWWBV3802E: The partnerLink ''{0}'' does not define the myRole role (pick activity ''{1}'', onMessage element number {2}).
- Explanation: PartnerLinks used in onMessage elements of a pick activity must define the myRole role.
- User Action: Define the myRole role for the partnerLink or use a different partnerLink.
- CWWBV3803E: The portType ''{0}'' was not found (pick activity ''{1}'', onMessage element number {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.
- CWWBV3804E: The portType referenced in the pick activity ''{0}'' and in the myRole role ''{1}'' must be the same (onMessage element number {2}, partnerLink ''{3}'', partnerLinkType ''{4}'').
- Explanation: The portType attribute in the onMessage element is optional. If this attribute is set, it must be the same as portType set in the myRole role in the partnerLink.
- User Action: Ensure the port types are the same.
- CWWBV3805E: The operation ''{0}'' was not found (pick activity ''{1}'', onMessage element number {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.
- CWWBV3806E: The input element is not defined in the operation ''{0}'' (pick activity ''{1}'', onMessage element number {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.
- CWWBV3807E: The messageType is not set in the input element of the operation ''{0}'' (pick activity ''{1}'', onMessage element number {2}).
- Explanation: The input messageType must be set when the operation is used in an onMessage element of a pick activity.
- User Action: Set the input messageType or use a different operation.
- CWWBV3808E: The messageType ''{0}'' referenced in the operation ''{1}'' was not found (pick activity ''{2}'', onMessage element number {3}).
- Explanation: The messageType referenced must be defined when the operation is used in an onMessage element of a pick activity.
- User Action: Set the messageType or use a different operation.
- CWWBV3809E: The messageType of the variable ''{0}'' and of the input element of operation ''{1}'' must be the same (pick activity ''{2}'', onMessage element number {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.
- CWWBV3810E: The variable for onMessage element number {1} in pick activity ''{0}'' is not set.
- Explanation: A mandatory variable for the onMessage element on a pick is not defined.
- User Action: Define the mandatory variable. In WebSphere Integration Developer, in the business process editor, select the specified element. In the Properties view, select the Details tab and specify a variable.
- CWWBV3811E: The variable ''{0}'' is not defined (pick activity ''{1}'', onMessage element number {2}).
- Explanation: The variable used in the pick activity is not defined.
- User Action: Check that the variable name is defined correctly.
- CWWBV3812E: The correlation set ''{0}'' was not found (pick activity ''{1}'', onMessage element number {2}).
- Explanation: The correlation set used in the pick activity is not defined.
- User Action: Define the correlation set, or remove it from the onMessage element of the pick activity.
- CWWBV3813E: A matching propertyAlias definition was not found for the property ''{0}'' and messageType ''{1}'' (pick activity ''{2}'', onMessage element number {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.
- CWWBV3814E: The part ''{0}'' referenced in the propertyAlias for the property ''{1}'' and the messageType ''{2}'' was not found (pick activity ''{3}'', onMessage element number {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.
- CWWBV3815E: The part ''{0}'' referenced in the propertyAlias for the property ''{1}'' and the messageType ''{2}'' does not reference a valid XML schema simple type (pick activity ''{3}'', onMessage element number {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.
- CWWBV3816E: The type of the part ''{0}'' of the messageType ''{1}'' and the property ''{2}'' is not the same (pick activity ''{3}'', onMessage element number {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.
- CWWBV3817E: Multiple propertyAlias definitions were found for the property ''{0}'' and the messageType ''{1}'' (pick activity ''{2}'', onMessage element number {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.
- CWWBV3818E: The onMessage element, number {0}, in pick activity ''{1}'' does not use a correlation set.
- Explanation: If more than one pick or receive activity is used in a process model, all of the onMessage elements of a pick 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 onMessage element. In WebSphere Integration Developer, in the business process editor, select the specified onMessage element. In the Properties view, select the Correlation tab and add a correlation set.
- CWWBV3819E: The wrong set of correlation sets is used in onMessage element number {0} of the pick activity ''{1}''. The expected set of correlation sets, as used in the activity ''{2}'', is: ''{3}''.
- Explanation: All of the pick or receive activities that create process instances must use the same set of correlation sets.
- User Action: Ensure that all of the receive and pick activities that create process instances use the same set of correlation sets.
- CWWBV3821E: The pick activity ''{0}'' can create process instances but it has onAlarm events.
- Explanation: If the pick activity creates process instances, onAlarm events are not allowed.
- User Action: Remove the onAlarm events or redefine the pick activity so that it does not create process instances.
- CWWBV3822E: A reply activity was not found that matches onMessage element number {0} of the pick activity ''{1}''.
- Explanation: For each two-way operation onMessage element in a pick 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 onMessage element of the pick activity.
- CWWBV3823E: The variable must not be set because an output element is available (pick activity ''{0}'', onMessage element number {1}, variable ''{2}'').
- Explanation: The data that is received by this onMessage element can be stored in the activity variable, which must be message-typed, or in one or more XSD-typed variables specified in the output element.
- User Action: Remove the variable attribute from the onMessage element.
- CWWBV3824E: The variable ''{0}'' is not defined (pick activity ''{1}'', output element of onMessage element number {2}, parameter number {3}).
- Explanation: The variable used in the parameter extension is not defined.
- User Action: Check that the variable name is defined correctly.
- CWWBV3825E: The message-typed variable cannot be used here (pick activity ''{0}'', output element of onMessage element number {1}, parameter number {2}, variable ''{3}'').
- Explanation: You can use only element-typed or type-typed variables in output elements.
- User Action: Use an XSD-typed variable.
- CWWBV3826E: The variable ''{0}'' cannot be used multiple times in the same output element (pick activity ''{1}'', output element of onMessage element number {2}, parameter number {3}).
- Explanation: A variable can be used only once in an output element.
- User Action: Use another XSD-typed variable.
- CWWBV3827E: The human task ''{0}'' cannot be found (pick activity ''{1}'', onMessage element number {2}).
- Explanation: The human task that is referenced in the onMessage element cannot be found.
- User Action: Remove the human task reference or ensure that the human task can be found.
- CWWBV3828E: The human task ''{0}'' is not an invocation task (pick activity ''{1}'', onMessage element number {2}).
- Explanation: The human task that is referenced in the onMessage element must be an invocation task.
- User Action: Reference an invocation task.
- CWWBV3829E: The portType that is referenced in onMessage element number {0} and in the human task ''{1}'' must be the same (pick activity ''{2}'').
- Explanation: The portTypes must be the same.
- User Action: Ensure that the portTypes are the same.
- CWWBV3830E: The operation that is referenced in onMessage element number {0} and in the human task ''{1}'' must be the same (pick activity ''{2}'').
- Explanation: The operations must be the same.
- User Action: Ensure that the operations are the same.
- CWWBV3831E: The part is not set in the propertyAlias for the property ''{0}'' and the messageType ''{1}'' (pick activity ''{2}'', onMessage element number {3}, correlation set ''{4}'').
- Explanation: The part must be set in the propertyAlias.
- User Action: Set the part.
- CWWBV3832E: The query language ''{0}'' used in the propertyAlias is not supported. It must be one of ''{1}'' (pick activity ''{2}'', onMessage element number {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.
- CWWBV3833E: The onAlarm event must specify at least a for expression, or an until expression (pick activity ''{0}'', onAlarm 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. One of these two expressions must occur in an onAlarm event.
- User Action: Specify a for expression, or an until expression.
- CWWBV3834E: The onAlarm event must specify at least a for expression, an until expression, or a timeout expression (pick activity ''{0}'', onAlarm 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 WebSphere Application Server scheduling service, or user-written calendars adhering to those conventions. One of these three expressions must occur in an onAlarm event.
- User Action: Specify a for expression, an until expression, or a timeout expression.
- CWWBV3835E: The onAlarm event cannot specify a for expression and a timeout expression, or an until expression and a timeout expression (pick activity ''{0}'', onAlarm 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 WebSphere Application Server scheduling service, or user-written calendars adhering to those conventions. One of these three expressions must occur in an onAlarm event.
- User Action: Specify a for expression, an until expression, or a timeout expression.
- CWWBV3836E: The repeatEvery expression is not allowed in pick activities (pick activity ''{0}'', onAlarm event {1}).
- Explanation: Syntactically the repeatEvery expression is allowed in pick activities, however, this expression is only useful in event handlers.
- User Action: Use the for expression instead.
- CWWBV3837E: The onMessage element, number {0}, implements operation ''{1}'' of portType ''{2}'', which is already implemented in another onMessage element (pick activity ''{3}'').
- Explanation: The same portType and operation can be implemented only once in the same pick activity. In case a message is received for a specific portType and operation, the executing engine must know which onMessage element in that instance of the process has to be executed.
- User Action: Remove the onMessage element or change the operation.
- CWWBV3838E: The parameter-extension cannot be used for the message ''{0}'' (pick activity ''{1}'', onMessage element number {2}).
- Explanation: The input message of the used operation of the onMessage element cannot be used together with the parameter-extension. For example, the message contains an array, which cannot 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.
- CWWBV3839E: The parameter ''{0}'' is not mapped to an element or part (pick activity ''{1}'', onMessage element number {2}, parameter number {3}).
- Explanation: A parameter has been found that 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.
- CWWBV3840E: The XSD type definition ''{0}'' was not found (pick activity ''{1}'', onMessage element number {2}, parameter number {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 inline in a WSDL interface or in an XML schema.
- User Action: Check that the XSD type definition is correctly referenced and that it is defined correctly.
- CWWBV3841E: The XSD element declaration ''{0}'' was not found (pick activity ''{1}'', onMessage element number {2}, parameter number {3}, matching part or element ''{4}'').
- Explanation: The XSD element declaration referenced in the matching part or element must be either defined inline 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.
- CWWBV3842E: The element or part ''{0}'' cannot be assigned to variable ''{1}'' because the data type does not match (pick activity ''{2}'', onMessage element number {3}, parameter number {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.
- CWWBV3843E: The XSD element ''{0}'' must be mapped to a parameter (pick activity ''{1}'', onMessage element number {2}).
- Explanation: An element has been found in the wrapper that does not map to a parameter.
- User Action: Remove the element or map it to a parameter.
- CWWBV3844E: The message-part ''{0}'' is not mapped to a parameter (pick activity ''{1}'', onMessage element number {2}).
- Explanation: A message-part has been found in the wrapper that does not map to a parameter.
- User Action: Remove the message-part or map it to a parameter.
- CWWBV3845E: The correlation set ''{0}'' is used already (pick activity ''{1}'', onMessage element number {2}).
- Explanation: The correlation set can be used only once per onMessage element.
- User Action: Ensure the correlation set is used only once in the given onMessage element.
- CWWBV3846W: The pick activity ''{0}'' is contained in the parallel forEach activity ''{1}''. This can result in the standard fault ''bpws:conflictingReceive''.
- Explanation: The pick activity is contained in a parallel forEach activity. If multiple branches are created in the parallel forEach activity, the contained pick activity may lead to the standard fault 'bpws:conflictingReceive' during run time.
- User Action: Review and test the process carefully to ensure the parallel execution of the branches in the forEach activity will not result in the standard fault 'bpws:conflictingReceive'.
- CWWBV3847E: The same operation of the same port type is implemented by process onEvent event number {0}. This would result in the standard fault ''bpws:conflictingReceive'' (pick activity ''{1}'', onMessage element number {2}).
- Explanation: If the pick activity is enabled simultaneously with the onEvent event, the standard fault 'bpws:conflictingReceive' would be thrown. The reason for this behavior is that it is not clear to which of the two constructs an inbound message for that operation and port type should be delivered. The process would be in an undefined status.
- User Action: Either remove the pick activity, the onMessage element of the pick activity or the process onEvent event, or change the implemented operation or port type of the onMessage element or onEvent event.
- CWWBV3848E: The same operation of the same port type is implemented by onEvent event number {0} of the scope activity ''{1}''. This would result in the standard fault ''bpws:conflictingReceive'' (pick activity ''{2}'', onMessage element number {3}).
- Explanation: If the pick activity is enabled simultaneously with the onEvent event, the standard fault 'bpws:conflictingReceive' would be thrown. The reason for this behavior is that it is not clear to which of the two constructs an inbound message for that operation and port type should be delivered. The process would be in an undefined status.
- User Action: Either remove the pick activity, the onMessage element of the pick activity or the onEvent event, or change the implemented operation or port type of the onMessage element or onEvent event.
- CWWBV3849W: The pick activity ''{0}'' is contained in process onEvent event number {1}, which implements a one-way operation. This can result in the standard fault ''bpws:conflictingReceive''.
- Explanation: The pick activity is contained in an onEvent event, which implements a one-way operation. If this onEvent event is executed multiple times in parallel, the contained pick activity may lead to the standard fault 'bpws:conflictingReceive' during run time.
- User Action: Review and test the process carefully to ensure the parallel execution of the onEvent event will not result in the standard fault 'bpws:conflictingReceive'.
- CWWBV3850W: The pick activity ''{0}'' is contained in onEvent event number {1} of the scope activity ''{2}'', which implements a one-way operation. This can result in the standard fault ''bpws:conflictingReceive''.
- Explanation: The pick activity is contained in an onEvent event, which implements a one-way operation. If this onEvent event is executed multiple times in parallel, the contained pick activity may lead to the standard fault 'bpws:conflictingReceive' during run time.
- User Action: Review and test the process carefully to ensure the parallel execution of the onEvent event will not result in the standard fault 'bpws:conflictingReceive'.
- CWWBV3851E: The XPath for- or until-expression is not valid: {0} (pick activity ''{1}'', onAlarm event {2}).
- Explanation: The given XPath for- or until-expression is not syntactically valid.
- User Action: Ensure that the XPath for- or until-expression is valid.
- CWWBV3852E: The XPath correlation set property propertyAlias query is not valid: {0} (pick activity ''{1}'', onMessage element number {2}, correlation set ''{3}'', propertyAlias for the property ''{4}'' and the messageType ''{5}'').
- Explanation: The given XPath query in the correlation set property propertyAlias is not syntactically valid.
- User Action: Ensure that the XPath query in the correlation set property propertyAlias is valid.
- CWWBV3853W: The XPath correlation set property propertyAlias query must not be empty (pick activity ''{0}'', onMessage element number {1}, correlation set ''{2}'', propertyAlias for the property ''{3}'' and the messageType ''{4}'').
- Explanation: The given XPath query in the correlation set property propertyAlias is not syntactically valid.
- User Action: Ensure that the XPath query in the correlation set property propertyAlias is valid. Either add a query construct or remove the query element.
- CWWBV3854W: Assigning the xsd:anyType typed element or part ''{0}'' to the xsd:anySimpleType typed variable ''{1}'' might result in a runtime error (pick activity ''{2}'', onMessage element number {3}, parameter number {4}).
- Explanation: The xsd:anyType and xsd:anySimpleType must match.
- User Action: Edit the types so that they match.
- CWWBV3855W: The XPath for-expression or until-expression in onAlarm event number {2} of pick activity ''{1}'' is not valid: ''{0}''
- Explanation: The specified XPath expression is not supported.
- User Action: Edit the XPath for-expression or until-expression is valid. In WebSphere Integration Developer, in the business process editor, select the specified onAlarm in the specified onMessage switch activity. In the Properties view, select the Details tab and correct the XPath expression.
- CWWBV3862W: The XPath for-expression or until-expression in onAlarm event number {2} of pick activity ''{1}'' is not valid because the ''$'' notation that is used to refer to a variable in the ''{0}'' XPath expression or query is not supported. (onMessage switch activity ''{1}'', onAlarm event number {2}).
- Explanation: The '$' notation to reference a variable is not supported in this XPath expression.
- User Action: Edit the XPath for-expression or until-expiration-expression so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified onAlarm in the specified receive activity. In the Properties view, select the Details tab and correct the XPath expression without using the "$" notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBV3863W: The XPath correlation set property propertyAlias query is not valid: ''{0}'' (pick activity ''{1}'', onMessage element number {2}, correlation set ''{3}'', propertyAlias for the property ''{4}'' and the messageType ''{5}'').
- Explanation: The specified XPath expression is not supported.
- User Action: Edit the XPath query in the propertyAlias element so that it is valid. In WebSphere Integration Developer, in the business process editor, in the tray on the right side of the process, select the specified correlation property. In the Properties view, correct the XPath expression by selecting the appropriate row in the table and clicking Edit.
- CWWBV3866W: The XPath correlation set property propertyAlias query is not valid: The ''$'' notation to reference a variable in the XPath expression or query ''{0}'' is not supported. (pick activity ''{1}'', onMessage element number {2}, correlation set ''{3}'', propertyAlias for the property ''{4}'' and the messageType ''{5}'').
- Explanation: The '$' notation to reference a variable is not supported in this XPath expression.
- User Action: Edit the XPath query in the propertyAlias element so that it is valid. In WebSphere Integration Developer, in the business process editor, in the tray on the right side of the process, select the specified correlation property. In the Properties view, correct the XPath expression by selecting the appropriate row in the table and clicking Edit Correct the XPath expression without using the "$" notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBV3867W: The onMessage element, number {0}, in pick activity ''{1}'' does not use a correlation set.
- Explanation: If more than one pick or receive activity is used in a process model, all of the onMessage elements in a pick 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 onMessage element. In WebSphere Integration Developer, in the business process editor, select the onMessage element. In the Properties view, select the Correlation tab and add a correlation set.
- CWWBV3868E: The variable must not be set because a fromParts element is available ({0} pick activity, onMessage element number {1}, {2} variable).
- Explanation: The data that is received by this onMessage element can be stored in the activity variable, which must be message-typed, or a message part is specified in the fromPart element.
- User Action: Remove the variable attribute from the onMessage element.
- CWWBV3900E: The receive activity ''{0}'' does not use a correlation set.
- Explanation: If more than one pick or receive activity is used in a process model, all of the receive activities 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 activity.
- CWWBV3901E: 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 pick or receive activities that create process instances must use the same set of correlation sets.
- User Action: Ensure that all of the receive and pick activities that create process instances use the same set of correlation sets.
- CWWBV3902E: 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.
- CWWBV3903E: 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-typed variables specified in the output element.
- User Action: Remove the variable attribute from the receive activity.
- CWWBV3904E: The human task ''{0}'' is not an invocation task (receive activity ''{1}'').
- Explanation: The human task that is referenced in the receive activity must be an invocation task.
- User Action: Reference an invocation task.
- CWWBV3905W: The receive activity ''{0}'' is contained in the parallel forEach activity ''{1}''. This can result in the standard fault ''bpws:conflictingReceive''.
- Explanation: The receive activity is contained in a parallel forEach activity. If multiple branches are created in the parallel forEach activity, the contained receive activity may lead to the standard fault 'bpws:conflictingReceive' while runtime.
- User Action: Review and test the process carefully to ensure the parallel execution of the branches in the forEach activity will not result in the standard fault 'bpws:conflictingReceive'.
- CWWBV3906E: The same operation of the same port type is implemented by process onEvent event number {0}. This would result in the standard fault ''bpws:conflictingReceive'' (receive activity ''{1}'').
- Explanation: If the receive activity is enabled simultaneously with the onEvent event, the standard fault 'bpws:conflictingReceive' would be thrown. The reason for this behavior is that it is not clear to which of the two constructs an inbound message for that operation and port type should be delivered. The process would be in an undefined status.
- User Action: Either remove the receive activity, or remove the process onEvent event, or change the implemented operation or port type of the receive activity or onEvent event.
- CWWBV3907E: The same operation of the same port type is implemented by onEvent event number {0} of the scope activity ''{1}''. This would result in the standard fault ''bpws:conflictingReceive'' (receive activity ''{2}'').
- Explanation: If the receive activity is enabled simultaneously with the onEvent event, the standard fault 'bpws:conflictingReceive' would be thrown. The reason for this behavior is that it is not clear to which of the two constructs an inbound message for that operation and port type should be delivered. The process would be in an undefined status.
- User Action: Either remove the receive activity, or remove the onEvent event, or change the implemented operation or port type of the receive activity or onEvent event.
- CWWBV3908W: The receive activity ''{0}'' is contained in the process onEvent event number {1}, which implements a one-way operation. This can result in the standard fault ''bpws:conflictingReceive''.
- Explanation: The receive activity is contained in an onEvent event, which implements a one-way operation. If this onEvent event is executed multiple times in parallel, the contained receive activity may lead to the standard fault 'bpws:conflictingReceive' during run time.
- User Action: Review and test the process carefully to ensure the parallel execution of the onEvent event will not result in the standard fault 'bpws:conflictingReceive'.
- CWWBV3909W: The receive activity ''{0}'' is contained in onEvent event number {1} of the scope activity ''{2}'', which implements a one-way operation. This can result in the standard fault ''bpws:conflictingReceive''.
- Explanation: The receive activity is contained in an onEvent event, which implements a one-way operation. If this onEvent event is executed multiple times in parallel, the contained receive activity may lead to the standard fault 'bpws:conflictingReceive' during run time.
- User Action: Review and test the process carefully to ensure the parallel execution of the onEvent event will not result in the standard fault 'bpws:conflictingReceive'.
- CWWBV3910W: The receive activity ''{0}'' does not use a correlation set.
- Explanation: If more than one pick or receive activity is used in a process model, all of the receive activities must use at least one correlation set. The correlation set ensures that the input messages can correlate with the process instance.
- User Action: Use at least one correlation set for the receive activity.
- CWWBV3911E: The variable must not be set because a fromParts element is available ({0} receive activity, {1} variable).
- Explanation: The data that is received by this receive activity can be stored in the activity variable, which must be message-typed, or a message part is specified in the fromParts element.
- User Action: Remove the variable attribute from the receive activity.
- CWWBV4000E: 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.
- CWWBV4001E: 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.
- CWWBV4002E: No pick 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 pick activity, receive activity, or onEvent event with the same port type and operation.
- User Action: Add a pick activity, receive activity, or onEvent event to the process with the same port type and operation type as the reply activity.
- CWWBV4003E: 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-typed variables specified in the input element.
- User Action: Remove the variable attribute from the reply activity.
- CWWBV4004E: The variable must not be set because a toParts element is available ({0} reply activity, {1} variable).
- Explanation: The data that is sent by this reply activity can be identified by the variable or the toParts elements. It is only allowed to use either the variable attribute or the toParts element.
- User Action: Remove the variable attribute from the reply activity.
- CWWBV4100E: 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.
- CWWBV4101E: The rethrow activity ''{0}'' cannot be used inside of a scope.
- 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 the scope around the rethrow activity.
- CWWBV4200E: 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'.
- CWWBV4201E: 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.
- CWWBV4202E: 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.
- CWWBV4203E: 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.
- CWWBV4204E: 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 defined 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.
- CWWBV4205E: 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.
- CWWBV4206E: 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.
- CWWBV4207E: The event handler of the scope activity must contain an onEvent event or an onAlarm event (scope activity ''{0}'').
- Explanation: An event handler must have at least one onEvent event or one onAlarm event.
- User Action: Define an onEvent event or an onAlarm event, or remove the event handler.
- CWWBV4208E: The partnerLink ''{0}'' was not found (scope activity ''{1}'', onEvent event number {2}).
- Explanation: The partnerLink referenced in the onEvent event is not defined.
- User Action: Ensure that the partnerLink is correct and that it is defined.
- CWWBV4209E: The partnerLink ''{0}'' does not define the myRole role (scope activity ''{1}'', onEvent event number {2}).
- Explanation: PartnerLinks used in onEvent events must define the myRole role.
- User Action: Define the myRole role for the partnerLink or use a different partnerLink.
- CWWBV4210E: The portType ''{0}'' was not found (scope activity ''{1}'', onEvent event number {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.
- CWWBV4211E: The portType referenced in onEvent event number {0} and in myRole role ''{1}'' must be the same (scope activity ''{2}'', partnerLink ''{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 partnerLink.
- User Action: Ensure that the port types are the same.
- CWWBV4212E: The operation ''{0}'' was not found (scope activity ''{1}'', onEvent event number {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.
- CWWBV4213E: The input element is not defined in the operation ''{0}'' (scope activity ''{1}'', onEvent event number {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.
- CWWBV4214E: The messageType is not set in the input element of the operation ''{0}'' (scope activity ''{1}'', onEvent event number {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.
- CWWBV4215E: The messageType ''{0}'' referenced in the operation ''{1}'' was not found (scope activity ''{2}'', onEvent event number {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.
- CWWBV4216E: 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 number {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.
- CWWBV4217E: The variable is not set (scope activity ''{0}'', onEvent event number {1}).
- Explanation: A mandatory variable for the onEvent event is not defined.
- User Action: Define the mandatory variable.
- CWWBV4218E: The messageType or element is not set ({0} scope activity, onEvent event number {1}).
- Explanation: A mandatory attribute (messageType or element) for the onEvent event is not defined.
- User Action: Define either the messageType or element attribute.
- CWWBV4219E: The messageType ''{0}'' was not found (scope activity ''{1}'', onEvent event number {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.
- CWWBV4220E: The correlation set ''{0}'' was not found (scope activity ''{1}'', onEvent event number {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.
- CWWBV4221E: The variable must not be set because an output element is available (scope activity ''{0}'', onEvent event number {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-typed variables specified in the output element.
- User Action: Remove the variable attribute from the onEvent event.
- CWWBV4222E: 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'.
- CWWBV4223E: The parameter-extension cannot be used for the message ''{0}'' (scope activity ''{1}'', onEvent event number {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, which cannot 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.
- CWWBV4224E: The parameter ''{0}'' is not mapped to an element or part (scope activity ''{1}'', onEvent event number {2}, parameter number {3}).
- Explanation: A parameter has been found that 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.
- CWWBV4225E: The variable name ''{0}'' is used already in the same onEvent event (scope activity ''{1}'', output element of onEvent event number {2}, parameter number {3}).
- Explanation: A variable name can be used only once in an output element.
- User Action: Use another variable name.
- CWWBV4226E: A matching propertyAlias definition was not found for the property ''{0}'' and messageType ''{1}'' (scope activity ''{2}'', onEvent event number {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.
- CWWBV4227E: 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 number {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.
- CWWBV4228E: The part ''{0}'' that is referenced in the propertyAlias for the property ''{1}'' and the messageType ''{2}'' does not reference a valid XML schema simple type (scope activity ''{3}'', onEvent event number {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.
- CWWBV4229E: 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 number {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.
- CWWBV4230E: Multiple propertyAlias definitions were found for the property ''{0}'' and the messageType ''{1}'' (scope activity ''{2}'', onEvent event number {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.
- CWWBV4231E: The human task ''{0}'' cannot be found (scope activity ''{1}'', onEvent event number {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.
- CWWBV4232E: The human task ''{0}'' is not an invocation task (scope activity ''{1}'', onEvent event number {2}).
- Explanation: The human task referenced in the scope activity onEvent event must be an invocation task.
- User Action: Reference an invocation task.
- CWWBV4233E: The portType referenced in onEvent event number {0} and in the 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.
- CWWBV4234E: The operation that is referenced in onEvent event number {0} and in the 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.
- CWWBV4235E: The part is not set in the propertyAlias for the property ''{0}'' and the messageType ''{1}'' (scope activity ''{2}'', onEvent event number {3}, correlation set ''{4}'').
- Explanation: The part must be set in the propertyAlias.
- User Action: Set the part.
- CWWBV4236E: The query language ''{0}'' used in the propertyAlias is not supported. It must be one of ''{1}'' (scope activity ''{2}'', onEvent event number {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.
- CWWBV4237E: A reply activity was not found that matches onEvent event number {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.
- CWWBV4238E: The expression is not valid (scope activity ''{0}'', onAlarm 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.
- CWWBV4239E: There are too many variable type definitions set for the variable ''{0}'' (scope activity ''{1}'', onEvent event number {2}, parameter number {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.
- CWWBV4240E: The XSD element declaration ''{0}'' was not found (scope activity ''{1}'', onEvent event number {2}, parameter number {3}, variable ''{4}'').
- Explanation: The XSD element declaration referenced in the variable must be either defined inline 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.
- CWWBV4241E: The XSD type definition ''{0}'' was not found (scope activity ''{1}'', onEvent event number {2}, parameter number {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 inline in a WSDL interface or in an XML schema.
- User Action: Check that the XSD type definition is correctly referenced and that it is defined correctly.
- CWWBV4242E: The variable ''{0}'' must have a variable type definition (scope activity ''{1}'', onEvent event number {2}, parameter number {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.
- CWWBV4243E: The XSD type definition ''{0}'' was not found (scope activity ''{1}'', onEvent event number {2}, parameter number {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 inline in a WSDL interface or in an XML schema.
- User Action: Check that the XSD type definition is correctly referenced and that it is defined correctly.
- CWWBV4244E: The XSD element declaration ''{0}'' was not found (scope activity ''{1}'', onEvent event number {2}, parameter number {3}, matching part or element ''{4}'').
- Explanation: The XSD element declaration referenced in the matching part or element must be either defined inline 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.
- CWWBV4245E: The element ''{0}'' cannot be assigned to variable ''{1}'' because the data type does not match (scope activity ''{2}'', onEvent event number {3}, parameter number {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.
- CWWBV4246E: The part ''{0}'' cannot be assigned to variable ''{1}'' because the data type does not match (scope activity ''{2}'', onEvent event number {3}, parameter number {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.
- CWWBV4247E: The XSD element ''{0}'' is not mapped to a parameter (scope activity ''{1}'', onEvent event number {2}).
- Explanation: An element has been found in the wrapper that does not map to a parameter.
- User Action: Remove the element or map it to a parameter.
- CWWBV4248E: The message-part ''{0}'' is not mapped to a parameter (scope activity ''{1}'', onEvent event number {2}).
- Explanation: A message-part has been found in the wrapper that does not map to a parameter.
- User Action: Remove the message-part or map it to a parameter.
- CWWBV4249E: The correlation set ''{0}'' is used already (scope activity ''{1}'', onEvent event number {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.
- CWWBV4250W: The scope activity ''{0}'' defines event handlers and is contained in the parallel forEach activity ''{1}''. This can result in the standard fault ''bpws:conflictingReceive''.
- Explanation: The scope activity is contained in a parallel forEach activity. If multiple branches are created in the parallel forEach activity, the contained event handlers of the scope activity may lead to the standard fault 'bpws:conflictingReceive while runtime'.
- User Action: Review and test the process carefully to ensure the parallel execution of the branches in the forEach activity will not result in the standard fault 'bpws:conflictingReceive'.
- CWWBV4251E: The onEvent event, number {0}, implements operation ''{1}'' of portType ''{2}'', which is already implemented in another onEvent event (scope activity ''{3}'').
- Explanation: The same portType and operation can be implemented only once in the same event handler. In case a message is received for a specific portType and operation, the executing engine must know which onEvent event in that instance of the process have to be executed.
- User Action: Remove the onEvent event or change the operation.
- CWWBV4252E: The onEvent event, number {0}, does not use a correlation set (scope activity ''{1}'').
- Explanation: If an onEvent event is used in a process model, it 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 onEvent event.
- CWWBV4253E: The same operation of the same port type is implemented by process onEvent event number {0}. This would result in the standard fault ''bpws:conflictingReceive'' (scope activity ''{1}'', onEvent event number {2}).
- Explanation: If the scope activity is enabled simultaneously with the process onEvent event, the standard fault 'bpws:conflictingReceive' would be thrown. The reason for this behavior is that it is not clear to which of the two events an inbound message for that operation and port type should be delivered. The process would be in an undefined status.
- User Action: Either remove the scope activity, the onEvent event of the scope activity or the process onEvent event, or change the implemented operation or port type of one of the onEvent events.
- CWWBV4254E: The same operation of the same port type is implemented by onEvent event number {0} of the outer scope activity ''{1}''. This would result in the standard fault ''bpws:conflictingReceive'' (inner scope activity ''{2}'', onEvent event number {3}).
- Explanation: If the inner scope activity is enabled simultaneously with the onEvent event of the outer scope activity, the standard fault 'bpws:conflictingReceive' would be thrown. The reason for this behavior is that it is not clear to which of the two events an inbound message for that operation and port type should be delivered. The process would be in an undefined status.
- User Action: Either remove the inner scope activity, the onEvent event of the inner scope activity or the onEvent event of the outer scope activity, or change the implemented operation or port type of one of the onEvent events.
- CWWBV4255W: The scope activity ''{0}'' defines event handlers and is contained in process onEvent event number {1}, which implements a one-way operation. This can result in the standard fault ''bpws:conflictingReceive''.
- Explanation: The scope activity defining event handlers is contained in a process onEvent event, which implements a one-way operation. If the process onEvent event is executed multiple times in parallel, the defined event handlers in the scope activity may lead to the standard fault 'bpws:conflictingReceive' during run time.
- User Action: Review and test the process carefully to ensure the parallel execution of the onEvent event will not result in the standard fault 'bpws:conflictingReceive'.
- CWWBV4256W: The inner scope activity ''{0}'' defines event handlers and is contained in onEvent event number {1} of the outer scope activity ''{2}'', which implements a one-way operation. This can result in the standard fault ''bpws:conflictingReceive''.
- Explanation: The inner scope activity defining event handlers is contained in an onEvent event of the outer scope activity, which implements a one-way operation. If the outer onEvent event is executed multiple times in parallel, the defined event handlers in the scope activity may lead to the standard fault 'bpws:conflictingReceive' during run time.
- User Action: Review and test the process carefully to ensure the parallel execution of the onEvent event will not result in the standard fault 'bpws:conflictingReceive'.
- CWWBV4257E: The query properties extension is only allowed for process variables (scope activity ''{0}'', scope variable ''{1}'').
- Explanation: The query properties extension is for identifying process instances upon variable values. Therefore, the extension is only allowed for global variables defined at the process element.
- User Action: Remove the query properties extension defined for the scope variable.
- CWWBV4258E: The XPath for-, until- or repeatEvery-expression is not valid: {0} (scope activity ''{1}'', onAlarm event {2}).
- Explanation: The given XPath for-, until- or repeatEvery-expression is not syntactically valid.
- User Action: Ensure that the XPath for-, until- or repeatEvery-expression is valid.
- CWWBV4259E: The XPath correlation set property propertyAlias query is not valid: {0} (scope activity ''{1}'', onEvent event number {2}, correlation set ''{3}'', propertyAlias for the property ''{4}'' and the messageType ''{5}'').
- Explanation: The given XPath query in the correlation set property propertyAlias is not syntactically valid.
- User Action: Ensure that the XPath query in the correlation set property propertyAlias is valid.
- CWWBV4260W: The XPath correlation set property propertyAlias query must not be empty (scope activity ''{0}'', onEvent event number {1}, correlation set ''{2}'', propertyAlias for the property ''{3}'' and the messageType ''{4}'').
- Explanation: The given XPath query in the correlation set property propertyAlias is not syntactically valid.
- User Action: Ensure that the XPath query in the correlation set property propertyAlias is valid. Either add a query construct or remove the query element.
- CWWBV4261W: In onEvent event number {3} from the event handler that is attached to the scope activity ''{2}'', assigning the ''{0}'' xsd:anyType typed element to the ''{1}'' xsd:anySimpleType typed variable might cause a runtime error (parameter number {4}).
- Explanation: The xsd:anyType and the variable of type xsd:anySimpleType must match.
- User Action: Edit the types so that they match.
- CWWBV4262W: In onEvent event number {3} of the event handler that is attached to scope activity ''{2}'', assigning the ''{0}'' xsd:anyType typed part to the ''{1}'' xsd:anySimpleType variable might cause a runtime error (parameter number {4}).
- Explanation: The part of the xsd:anyType and the variable of the xsd:anySimpleType must match.
- User Action: Edit the types so that they match.
- CWWBV4263W: The XPath for-expression, until-expression, or repeatEvery-expression in onAlarm event number {2} in scope activity ''{1}'' is not valid: ''{0}''
- Explanation: The specified XPath expression is not supported.
- User Action: Edit the XPath for-expression, until-expression, or repeatEvery-expression so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified scope activity. Open the associated event handler and select the specified onAlarm. In the Properties view, select the Details tab and correct the XPath expression.
- CWWBV4266W: The XPath for-expression, until-expression, or repeatEvery-expression in onAlarm event number {2} in scope activity ''{1}'' is not valid because the ''$'' notation that is used to refer to a variable in the ''{0}'' XPath expression or query is not supported.
- Explanation: The '$' notation to reference a variable is not supported in this XPath expression.
- User Action: Edit the XPath for-expression, until-expression, or repeatEvery-expression so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified scope activity. Open the associated event handler and select the specified onAlarm. In the Properties view, select the Details tab and correct the XPath expression without using the "$" notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBV4267W: The XPath correlation set property propertyAlias query is not valid: ''{0}'' (scope activity ''{1}'', onEvent event number {2}, correlation set ''{3}'', propertyAlias for the property ''{4}'' and the messageType ''{5}'').
- Explanation: The specified XPath expression is not supported.
- User Action: Edit the XPath query in the specified element (propertyAlias) so that it is valid. In WebSphere Integration Developer, in the business process editor, in the tray on the right side of the process, select the specified correlation property. In the Properties view, correct the XPath expression by selecting the appropriate row in the table and clicking Edit.
- CWWBV4270W: The XPath correlation set property propertyAlias query is not valid: The ''$'' notation to reference a variable in the XPath expression or query ''{0}'' is not supported. (scope activity ''{1}'', onEvent event number {2}, correlation set ''{3}'', propertyAlias for the property ''{4}'' and the messageType ''{5}'').
- Explanation: The '$' notation to reference a variable is not supported in this XPath expression.
- User Action: Edit the XPath query in the specified element (propertyAlias) so that it is valid. In WebSphere Integration Developer, in the business process editor, in the tray on the right side of the process, select the specified correlation property. In the Properties view, select the appropriate row in the table, click Edit, and correct the XPath expression without using the "$" notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBV4271E: You cannot specify both the element and messageType attributes for the onEvent element. Remove one of the attributes ({0} scope activity, onEvent number {1}).
- Explanation: The OnEvent element can specify either an element attribute or a messageType attribute, but not both.
- User Action: Remove either the element or the messageType attribute.
- CWWBV4272E: The {0} element was not found ({1} scope activity, onEvent number {2}).
- Explanation: The element that is referenced in the onEvent event is not defined in the Web Services Description Language (WSDL) interface.
- User Action: Modify the element if it is not defined correctly in the WSDL interface.
- CWWBV4273E: The variable must not be set because a fromParts element is available ({0} scope activity, onEvent event number {1}, {2} variable).
- Explanation: The data that was received by this onEvent event can be stored in the onEvent variable, which must be message-typed, or a message part is specified in the fromParts element.
- User Action: Remove the variable attribute from the onEvent event.
- CWWBV4400E: The expression language ''{0}'' of the condition element is not supported. It must be one of ''{1}'' (switch activity ''{2}'', case element number {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.
- CWWBV4401E: The condition expression is not valid (switch activity ''{0}'', case element number {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-in expression language in the case condition, only the values 'wpc:true' and 'wpc:false' are allowed.
- User Action: Check the expression and the expression language.
- CWWBV4402E: The XPath case condition is not valid: {0} (switch activity ''{1}'', case element number {2}).
- Explanation: The given XPath case condition is not syntactically valid.
- User Action: Ensure that the XPath case condition is valid.
- CWWBV4403W: The XPath case condition in case element number {2} of the ''{1}'' switch activity is not valid: ''{0}''
- Explanation: The specified XPath expression is not supported.
- User Action: Edit the XPath case condition so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified switch activity. In the Properties view, select the Details tab and correct the XPath expression.
- CWWBV4406W: The XPath case condition in case element number {2} of switch activity ''{1}'' is not valid because the ''$'' notation that is used to refer to a variable in the ''{0}'' XPath expression or query is not supported. (switch activity ''{1}'', case element number {2}).
- Explanation: The '$' notation to reference a variable is not supported in this XPath expression.
- User Action: Edit the XPath case condition so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified switch activity. In the Properties view, select the Details tab and correct the XPath expression without the "$" notation to refer to a variable. Instead, use the bpws:getVariableData() XPath function.
- CWWBV4500E: 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.
- CWWBV4600E: 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 specifies when the alarm event is fired. One of these expressions must occur in a wait activity.
- User Action: Specify a for-expression or an until-expression.
- CWWBV4601E: 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 specifies when the alarm 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.
- CWWBV4602E: 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 WebSphere Application 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.
- CWWBV4603E: 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 WebSphere Application 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.
- CWWBV4604E: 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.
- CWWBV4605E: The XPath for- or until-expression is not valid: {0} (wait activity ''{1}'').
- Explanation: The given XPath for- or until-expression is not syntactically valid.
- User Action: Ensure that the XPath for- or until-expression is valid.
- CWWBV4606W: In the ''{1}'' wait activity, the XPath for-expression or until-expression is not valid: ''{0}''
- Explanation: The specified XPath expression is not supported.
- User Action: Edit the XPath for-expression or until-expression so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified wait activity. In the Properties view, select the Details and correct the XPath expression.
- CWWBV4609W: In the ''{1}'' wait activity, the XPath for-expression or until-expression is not valid because the ''$'' notation that is used to refer to a variable in the ''{0}'' XPath expression or query is not supported.
- Explanation: The '$' notation to reference a variable is not supported in this XPath expression.
- User Action: Edit the XPath for-expression or until-expression so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified wait activity. In the Properties view, select the Details tab and correct the XPath expression without using the "$" notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBV4700E: The expression language ''{0}'' of the condition element is not supported. It must be one of ''{1}'' (while 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.
- CWWBV4701E: The condition expression is not valid (while 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-in expression language in the while condition, only the values 'wpc:true' and 'wpc:false' are allowed.
- User Action: Check the expression and the expression language.
- CWWBV4702E: The XPath while condition is not valid: {0} (while activity ''{1}'').
- Explanation: The given XPath while condition is not syntactically valid.
- User Action: Ensure that the XPath while condition is valid.
- CWWBV4703W: In the ''{1}'' while activity, the XPath while condition is not valid: ''{0}''
- Explanation: The specified XPath expression is not supported.
- User Action: Edit the XPath while condition so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified while activity. In the Properties view, select the Details tab and correct the XPath expression.
- CWWBV4706W: In the ''{1}'' while activity, the XPath while condition is not valid because the ''$'' notation that is used to refer to a variable in the ''{0}'' XPath expression or query is not supported.
- Explanation: The '$' notation to reference a variable is not supported in this XPath expression.
- User Action: Edit the XPath while condition so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified while activity. In the Properties view, select the Details tab and correct the XPath expression without using the "$" notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBV4800E: 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://'.
- CWWBV4801E: 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.
- CWWBV4802E: 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.
- CWWBV4803E: {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.
- CWWBV4804W: {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.
- CWWBV4805I: {0} (custom activity ''{1}'', plug-in ''{2}'').
- Explanation: The plug-in for the custom activity reported the given informational message.
- User Action: No action is required.
- CWWBV4806E: The result returned from the plug-in validation is not valid: {0} (custom activity ''{1}'', plug-in ''{2}'').
- Explanation: The plug-in validation must return ValidationMessages.
- User Action: Contact the plug-in owner.
- CWWBV4900E: 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.
- CWWBV4901E: The adminTask element is not allowed (human task activity ''{0}'').
- Explanation: AdminTask elements are only allowed for normal invoke, script, and custom activities, but not for human task activities.
- User Action: Remove the adminTask element from the human task activity.
- CWWBV4902E: The human task ''{0}'' is not a To-do task (human task activity ''{1}'').
- Explanation: The human task that is referenced in the human task activity must be a To-do task.
- User Action: Reference a To-do task.
- CWWBV4903E: 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.
- CWWBV4904E: 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.
- CWWBV4905E: The process contains a human task that contains errors (human task name ''{0}'').
- Explanation: The process contains a human task with errors.
- User Action: See the human task errors and correct them.
- CWWBV5000E: The expression language ''{0}'' of the startCounterValue element is not supported. It must be one of ''{1}'' (forEach 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.
- CWWBV5001E: The expression language ''{0}'' of the finalCounterValue element is not supported. It must be one of ''{1}'' (forEach 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.
- CWWBV5002E: The expression language ''{0}'' of the completionCondition element is not supported. It must be one of ''{1}'' (forEach 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.
- CWWBV5003E: A variable with the name ''{0}'' must not be defined on the scope activity ''{1}'', because a variable with that name is defined on that scope activity implicitely in the forEach activity ''{2}''.
- Explanation: The forEach activity specifies a counter name which is an implicit variable declaration on the directly enclosed scope activity. Therefore, the in the forEach activity directly enclosed scope activity must not define a variable with a name which is equal to the counter name.
- User Action: Either remove the variable from the scope activity, rename it or rename the counter name in the given forEach activity.
- CWWBV5004E: The XPath startCounterValue expression is not valid: {0} (forEach activity ''{1}'').
- Explanation: The given XPath startCounterValue expression is not syntactically valid.
- User Action: Ensure that the XPath startCounterValue expression is valid.
- CWWBV5005E: The XPath finalCounterValue expression is not valid: {0} (forEach activity ''{1}'').
- Explanation: The given XPath finalCounterValue expression is not syntactically valid.
- User Action: Ensure that the XPath finalCounterValue expression is valid.
- CWWBV5006E: The XPath completionCondition expression is not valid: {0} (forEach activity ''{1}'').
- Explanation: The given XPath completionCondition expression is not syntactically valid.
- User Action: Ensure that the XPath completionCondition expression is valid.
- CWWBV5007W: In the ''{1}'' forEach activity, the XPath completionCondition expression is not valid: ''{0}''
- Explanation: The specified XPath expression is not supported.
- User Action: Edit the XPath completionCondition expression so that it is valid. In WebSphere Integration Developer, select the specified forEach activity. In the Properties view, select the Details tab and open the Early Exit Criterion section. Correct the XPath expression.
- CWWBV5010W: In the ''{1}'' forEach activity, the XPath completionCondition expression is not valid because the ''$'' notation that is used to refer to a variable in the ''{0}'' XPath expression or query is not supported. (forEach activity ''{1}'').
- Explanation: The '$' notation to reference a variable is not supported in this XPath expression..
- User Action: Edit the XPath completionCondition expression so that it is valid. In WebSphere Integration Developer, select the specified forEach activity. In the Properties view, select the Details tab and open the Early Exit Criterion section. Correct the XPath expression without using the "$" notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBV5011W: In the ''{1}'' forEach activity, the XPath finalCounterValue expression is not valid: ''{0}''
- Explanation: The specified XPath expression is not supported.
- User Action: Edit the XPath finalCounterValue expression is valid. In WebSphere Integration Developer, select the specified forEach activity. In the Properties view, select the Details tab and open the Iteration section. Correct the XPath expression.
- CWWBV5014W: In the ''{1}'' forEach activity, the XPath finalCounterValue expression is not valid because the ''$'' notation that is used to refer to a variable in the ''{0}'' XPath expression or query is not supported. (forEach activity ''{1}'').
- Explanation: The '$' notation to reference a variable is not supported in this XPath expression.
- User Action: Ensure that the XPath finalCounterValue expression is valid. In WebSphere Integration Developer, select the specified forEach activity. In the Properties view, select the Details tab and open the Iteration section. Correct the XPath expression without using the "$" notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBV5015W: In the ''{1}'' forEach activity, the XPath startCounterValue expression is not valid: ''{0}''
- Explanation: The specified XPath expression is not supported.
- User Action: Ensure that the XPath startCounterValue expression is valid In WebSphere Integration Developer, select the specified forEach activity. In the Properties view, select the Details tab and open the Iteration section. Correct the XPath expression.
- CWWBV5018W: In the {1} forEach activity, the XPath startCounterValue expression is not valid because the ''$'' notation that is used to refer to a variable in the ''{0}'' XPath expression or query is not supported. (forEach activity ''{1}'').
- Explanation: The '$' notation to reference a variable is not supported in this XPath expression.
- User Action: Edit the XPath startCounterValue expression so that it is valid. In WebSphere Integration Developer, select the specified forEach activity. In the Properties view, select the Details tab and open the Iteration section. Correct the XPath expression without using the "$" notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBV6000E: The XSD-typed variable can only use inline defined query properties (process variable ''{0}'', queryProperty element number {1}, referenced property ''{2}'').
- Explanation: Referenced properties can be used as query properties only in the context of message-typed variables.
- User Action: Define an inline query property, or remove the queryProperty element from the variable.
- CWWBV6001E: The property ''{0}'' is already used as query property in this variable (process variable ''{1}'', queryProperty element number {2}).
- Explanation: Properties, regardless if referenced or defined inline, can be used as query properties only once per variable.
- User Action: Remove the queryProperty element from the variable.
- CWWBV6002E: The property ''{0}'' is referenced to be used as query property, but attribute ''name'', ''type'' and/or ''part'' and/or a query expression is specified (process variable ''{1}'', queryProperty element number {2}).
- Explanation: A queryProperty element can either reference an existing property or it can define an inline property by specifying the attributes 'name', 'type' and/or 'part' and/or a query expression.
- User Action: Ensure that either an existing property is referenced or an inline property is specified.
- CWWBV6003E: The queryProperty element, number {0}, must either reference an existing property or define an inline property (process variable ''{1}'').
- Explanation: A queryProperty element can either reference an existing property or it can define an inline property by specifying the attributes 'name', 'type' and/or 'part' and/or a query expression.
- User Action: Ensure that either an existing property is referenced or an inline property is specified.
- CWWBV6004E: The inline defined query property does not specify a name (process variable ''{0}'', queryProperty element number {1}).
- Explanation: An inline defined query property must specify the attribute 'name'.
- User Action: Set the 'name' attribute.
- CWWBV6005E: The inline defined query property ''{0}'' does not specify the type (process variable ''{1}'', queryProperty element number {2}).
- Explanation: An inline defined query property must specify the attribute 'type'.
- User Action: Set the 'type' attribute.
- CWWBV6006E: The type of the referenced property ''{0}'' is not set (process variable ''{1}'', queryProperty element number {2}).
- Explanation: The type of the referenced property must be set. Only XML schema simple types are allowed. List types and union types are not allowed.
- User Action: Set the XML schema simple type for the property.
- CWWBV6007E: The type ''{0}'' of the referenced property ''{1}'' was not found or is not an allowed or valid XML schema simple type in this context (process variable ''{2}'', queryProperty element number {3}).
- Explanation: The type used in the referenced property 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 schema primitive simple types and all simple types derived by restriction from a primitive simple type.
- User Action: Select an allowed XML schema simple type.
- CWWBV6008E: A matching propertyAlias definition was not found for the referenced property ''{0}'' and the messageType ''{1}'' (process variable ''{2}'', queryProperty element number {3}).
- Explanation: A propertyAlias definition is needed to map the parts of a messageType to the referenced property.
- User Action: Define the propertyAlias.
- CWWBV6009E: The part ''{0}'' was not found referenced in the propertyAlias for the referenced property ''{1}'' and the messageType ''{2}'' (process variable ''{3}'', queryProperty element number {4}).
- Explanation: The part must be defined in the messageType.
- User Action: Define the part, or use another existing part in the propertyAlias.
- CWWBV6010E: The part ''{0}'' does not reference a valid XML schema simple type (process variable ''{1}'', queryProperty element number {2}, part referenced in the propertyAlias for the referenced property ''{3}'' and the messageType ''{4}'').
- Explanation: The selected part of the messageType must be an XML schema simple type because a query property can only be of an XML schema simple type.
- User Action: Select a part that is of an XML schema simple type.
- CWWBV6011E: The type of part ''{0}'' of messageType ''{1}'' and property ''{2}'' are not the same (process variable ''{3}'', queryProperty element number {4}).
- Explanation: The selected part of the messageType does not have the same type as the property.
- User Action: Select a part that has the same XML schema simple type as the property.
- CWWBV6012E: Multiple propertyAlias definitions were found for referenced property ''{0}'' and messageType ''{1}'' (process variable ''{2}'', queryProperty element number {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 a new property and propertyAlias definition.
- CWWBV6013E: The part is not set in the propertyAlias for referenced property ''{0}'' and messageType ''{1}'' (process variable ''{2}'', queryProperty element number {3}).
- Explanation: The part must be set in the propertyAlias.
- User Action: Set the part.
- CWWBV6014E: The query language ''{0}'' used in the propertyAlias is not supported. It must be one of ''{1}'' (process variable ''{2}'', queryProperty element number {3}, propertyAlias for the referenced 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.
- CWWBV6015E: The type ''{0}'' was not found or is not an allowed or valid XML schema simple type in this context (process variable ''{1}'', queryProperty element number {2}, inline defined query property ''{3}'').
- Explanation: The type specified for the inline defined query property 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 schema primitive simple types and all simple types derived by restriction from a primitive simple type.
- User Action: Select an allowed XML schema simple type.
- CWWBV6016E: The inline defined query property ''{0}'' must specify the part, because the variable is message-typed (process variable ''{1}'', queryProperty element number {2}, messageType ''{3}'').
- Explanation: The part attribute must be set if the variable is message-typed.
- User Action: Set the part attribute.
- CWWBV6017E: The inline defined query property ''{0}'' specifies a part, but the variable is not message-typed (process variable ''{1}'', queryProperty element number {2}).
- Explanation: A part is not available if the variable is type-typed or element-typed.
- User Action: Remove the part attribute.
- CWWBV6018E: The part ''{0}'' was not found in the messageType ''{1}'' (process variable ''{2}'', queryProperty element number {3}, inline defined query property ''{4}'').
- Explanation: The part must be defined in the messageType.
- User Action: Define the part, or use another existing part.
- CWWBV6019E: The part ''{0}'' does not reference a valid XML schema simple type (process variable ''{1}'', queryProperty element number {2}, inline defined query property ''{3}'', messageType ''{4}'').
- Explanation: The selected part of the messageType must be an XML schema simple type because a query property can only be of an XML schema simple type.
- User Action: Select a part that is of an XML schema simple type.
- CWWBV6020E: The query language ''{0}'' is not supported. It must be one of ''{1}'' (process variable ''{2}'', queryProperty element number {3}, inline defined query property ''{4}'').
- 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.
- CWWBV6021E: The part must be the same as the part ''{0}'' as specified in process variable ''{1}'', in queryProperty element number {2} (process variable ''{3}'', queryProperty element number {4}, inline defined query property ''{5}'').
- Explanation: The same inline defined query property is specified in two message-typed variables of the same message type. Thus, the part specified in the inline defined query property must be the same.
- User Action: Ensure the part of both query property definitions is the same.
- CWWBV6022E: The query must be the same as the query specified in process variable ''{0}'' in queryProperty element number {1} (process variable ''{2}'', queryProperty element number {3}, inline defined query property ''{4}'').
- Explanation: The same inline defined query property is specified in two variables of the same message type, XSD type or XSD element. Thus, the query specified in the inline defined query property must be the same.
- User Action: Ensure the query of both query property definitions is the same.
- CWWBV6023E: The property type of the inline defined query property ''{0}'' must be ''{1}'' as specified in process variable ''{2}'' in queryProperty element number {3} (process variable ''{4}'', queryProperty element number {5}).
- Explanation: The same name is specified in two inline query property definitions in two variables, but the type is different.
- User Action: Ensure the type of both query property definitions is the same.
- CWWBV6024E: The XPath queryProperty propertyAlias query is not valid: {0} (process variable ''{1}'', queryProperty element number {2}, propertyAlias for referenced property ''{3}'' and messageType ''{4}'').
- Explanation: The given XPath query in the queryProperty propertyAlias is not syntactically valid.
- User Action: Ensure that the XPath query in the queryProperty propertyAlias is valid.
- CWWBV6025E: The XPath queryProperty query is not valid: {0} (process variable ''{1}'', queryProperty element number {2}, inline defined query property ''{3}'').
- Explanation: The given XPath query in the queryProperty is not syntactically valid.
- User Action: Ensure that the XPath query in the queryProperty is valid.
- CWWBV6026E: The XPath for-, until- or repeatEvery-expression is not valid: {0} (process onAlarm event {1}).
- Explanation: The given XPath for-, until- or repeatEvery-expression is not syntactically valid.
- User Action: Ensure that the XPath for-, until- or repeatEvery-expression is valid.
- CWWBV6027E: The XPath correlation set property propertyAlias query is not valid: {0} (process onEvent event number {1}, correlation set ''{2}'', propertyAlias for the property ''{3}'' and the messageType ''{4}'').
- Explanation: The given XPath query in the correlation set property propertyAlias is not syntactically valid.
- User Action: Ensure that the XPath query in the correlation set property propertyAlias is valid.
- CWWBV6028W: The XPath queryProperty propertyAlias query must not be empty (process variable ''{0}'', queryProperty element number {1}, propertyAlias for the referenced property ''{2}'' and the messageType ''{3}'').
- Explanation: The given XPath query in the queryProperty propertyAlias is not syntactically valid.
- User Action: Ensure that the XPath query in the queryProperty propertyAlias is valid. Either add a query construct or remove the query element.
- CWWBV6029W: The XPath correlation set property propertyAlias query must not be empty (process onEvent event number {0}, correlation set ''{1}'', propertyAlias for the property ''{2}'' and the messageType ''{3}'').
- Explanation: The given XPath query in the correlation set property propertyAlias is not syntactically valid.
- User Action: Ensure that the XPath query in the correlation set property propertyAlias is valid. Either add a query construct or remove the query element.
- CWWBV6030W: In process onAlarm event number {1}, the XPath for-expression, until-expression, or repeatEvery-expression is not valid: ''{0}''.
- Explanation: The specified XPath expression is not supported.
- User Action: Edit the XPath for-expression, until-expression, or repeatEvery-expression so that it is valid. In WebSphere Integration Developer, in the business process editor, go to the start node. Open the event handler and select the specified onAlarm event. In the Properties view, select the Details tab and correct the XPath expression.
- CWWBV6033W: In process onAlarm event number {1}, the XPath for-expression, until-expression, or repeatEvery-expression is not valid because the ''$'' notation that is used to refer to a variable in the ''{0}'' XPath expression or query is not supported.
- Explanation: The '$' notation to reference a variable is not supported in this XPath expression.
- User Action: Edit the XPath for-expression, until-expression, or repeatEvery-expression so that it is valid. In WebSphere Integration Developer, in the business process editor, go to the start node. Open the event handler and select the specified onAlarm event. In the Properties view, select the Details tab and correct the XPath expression without using the "$" notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBV6034W: The XPath queryProperty propertyAlias query is not valid: ''{0}'' (process variable ''{1}'', queryProperty element number {2}, propertyAlias for the referenced property ''{3}'' and the messageType ''{4}'').
- Explanation: The specified XPath expression is not supported.
- User Action: Edit the XPath query in the queryProperty propertyAlias so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified process variable. In the Properties view, select the Query Properties tab. In the table, select the specified queryProperty element and click Edit. In the dialog box, correct the XPath expression.
- CWWBV6037W: The XPath queryProperty propertyAlias query is not valid: The ''$'' notation to reference a variable in the XPath expression or query ''{0}'' is not supported. (process variable ''{1}'', queryProperty element number {2}, propertyAlias for the referenced property ''{3}'' and the messageType ''{4}'').
- Explanation: The '$' notation to reference a variable is not supported in this XPath expression.
- User Action: Edit the XPath query in the queryProperty propertyAlias so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified process variable. In the Properties view, select the Query Properties tab. In the table, select the specified queryProperty element and click Edit. In the dialog box, correct the XPath expression without using the "$" notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBV6038W: For the process variable ''{1}'', queryProperty element number {2} points to the inline defined query property ''{3}'', which is not valid: ''{0}''
- Explanation: The specified XPath expression is not supported.
- User Action: Edit the XPath query in the queryProperty so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified process variable. In the Properties view, select the Query Properties tab. In the table, select the specified queryProperty element and click Edit. In the dialog box, correct the XPath expression.
- CWWBV6041W: For the process variable ''{1}'', queryProperty element number {2} points to the inline defined query property ''{3}'', which is not valid because the ''$'' notation that is used to refer to a variable in the ''{0}'' XPath expression or query is not supported.
- Explanation: The '$' notation to reference a variable is not supported in this XPath expression.
- User Action: Edit the XPath query in the queryProperty so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified process variable. In the Properties view, select the Query Properties tab. In the table, select the specified queryProperty element and click Edit. In the dialog box, correct the XPath expression without using the "$" notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBV6042W: The XPath correlation set property propertyAlias query is not valid: ''{0}'' (process onEvent event {1}, correlation set ''{2}'', propertyAlias for the property ''{3}'' and the messageType ''{4}'').
- Explanation: The specified XPath expression is not supported.
- User Action: Edit the XPath query in the propertyAlias element so that it is valid. In WebSphere Integration Developer, in the business process editor, in the tray on the right side of the process, select the specified correlation property. In the Properties view, correct the XPath expression by selecting the appropriate row in the table and clicking Edit.
- CWWBV6045W: The XPath correlation set property propertyAlias query is not valid: The ''$'' notation to reference a variable in the XPath expression or query ''{0}'' is not supported. (process onEvent event number {1}, correlation set ''{2}'', propertyAlias for the property ''{3}'' and the messageType ''{4}'').
- Explanation: The '$' notation to reference a variable is not supported in this XPath expression.
- User Action: Edit the XPath query in the propertyAlias element so that it is valid. In WebSphere Integration Developer, in the business process editor, in the tray on the right side of the process, select the specified correlation property. In the Properties view, correct the XPath expression without using the "$" notation to refer to a variable. Instead, use the bpws:getVariableData() function.
- CWWBV6046W: An administration task cannot be used in a microflow (non-interruptible process). The administration task is defined on the ''{0}'' activity.
- Explanation: Microflows (non-interruptible processes) must not contain asynchronous activities, such as administration tasks, human task activities or wait activities.
- User Action: Define the process as a long-running process or remove the asynchronous activity.
- CWWBV6047E: The value of the continueOnError attribute is not valid in this context. For processes, only the value 'yes' or 'no' is allowed.
- Explanation: The continueOnError attribute on a process can only have the value 'yes' or 'no'.
- User Action: Use one of the valid values.
- CWWBV6048W: Deprecation: The {0} role defines a portType element. This use is deprecated. Use the portType attribute instead. ({1} process partnerLink, {2} partnerLinkType).
- Explanation: The portType element is deprecated.
- User Action: Use the portType attribute.
- CWWBV6049E: The {0} role defines a portType element and a portType attribute. You must use only a portType attribute. ({1} process partnerLink, {2} partnerLinkType)
- Explanation: The role uses the old and new schemas of the portType definition on a role. This is not supported.
- User Action: Use only the portType attribute.
- CWWBV6050E: The {0} element was not found (process onEvent event {1}).
- Explanation: The element that is referenced in the onEvent event is not defined in the Web Services Description Language (WSDL) interface.
- User Action: Modify the element if it is not defined correctly in the WSDL interface.
- CWWBV6051E: The onEvent element cannot specify both element and messageType attributes. Remove one of the attributes (process onEvent event {0}).
- Explanation: The onEvent element can specify either an element attribute or a messageType attribute but not both.
- User Action: Remove either the element or the messageType attribute.
- CWWBV6052W: The catch requires a fault variable as the defined fault ''{0}'' has associated fault data. (fault handler of activity ''{1}'', catch element number {2}).
- Explanation: If the fault has associated fault data, a catch activity specifying a matching fault name value and a no fault variable the default catchAll handler will be selected if present during runtime.
- User Action: Ensure that the correct fault variable is set.
- CWWBV6053W: The fault name ''{0}'' does not exist in the operation ''{1}''. (fault handler of activity ''{2}'', catch element number {3}).
- Explanation: The fault needs to be specified on the operation. Otherwise the default catchAll handler is selected if present during runtime.
- User Action: Ensure that the correct fault exist on the operation.
- CWWBV6054W: The fault message type ''{0}'' does not match the message type of fault data of the fault name ''{1}'' (fault handler of activity ''{2}'', catch element number {3}).
- Explanation: The fault message type must be of the fault data message type .
- User Action: Ensure that the fault message type is correct.
- CWWBV6300E: The {0} expression language of the condition element is not supported. It must be one of {1} ({2} RepeatUntil activity).
- Explanation: The specified expression language is unknown. Expressions that are specified in this expression language cannot be executed.
- User Action: Use one of the supported expression languages.
- CWWBV6301E: The condition expression is not valid ({0} RepeatUntil activity, {1} expression language).
- Explanation: The specified expression is not valid for the given expression language, or it is not valid in this context. For example, if you use the built-in expression language in the RepeatUntil condition, only the values wpc:true and wpc:false are allowed.
- User Action: Check the expression and the expression language, and modify them if they are not valid.
- CWWBV6302E: The XML Path Language (XPath) RepeatUntil condition is not valid. The error is: {0} ({1} RepeatUntil activity).
- Explanation: The specified XPath RepeatUntil condition is not syntactically valid.
- User Action: Correct the XPath RepeatUntil condition so that it is valid.
- CWWBV6303W: In the {1} RepeatUntil activity, the XML Path Language (XPath) RepeatUntil condition is not valid. The error is: {0}
- Explanation: The specified XPath expression is not supported.
- User Action: Edit the XPath RepeatUntil condition so that it is valid. In WebSphere Integration Developer, in the business process editor, select the specified RepeatUntil activity. In the Properties view, click the Details tab and correct the XPath expression.
- CWWBV9000I: 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: No action is required.
- CWWBV9001I: 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.
- CWWBV9002I: 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.
- CWWBV9050E: 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.
- CWWBV9051W: 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.
- CWWBV9052I: 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: No action is required.
- CWWBV9100E: 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.
- CWWBV9101E: 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.
- CWWBV9102E: 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.
- CWWBV9103E: 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.
- CWWBV9104E: 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 partnerLink in the process implementation file. The interface specified by this reference is different to the port type of the port 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 partner links.
- CWWBV9105E: The process component file ''{0}'' contains an interface ''{1}'' that does not have a corresponding partnerLink 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 partnerLink which match.
- CWWBV9106E: The process component file ''{0}'' contains a reference ''{1}'' that does not have a corresponding partnerLink 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 partnerLink which match.
- CWWBV9107E: The process component file ''{0}'' does not contain an interface that corresponds to the inbound partnerLink ''{1}'' in the process implementation file.
- Explanation: The process component file does not contain an interface that matches the signature of the inbound partnerLink ''{1}'' in the process implementation file.
- User Action: Add an interface to the process component file that matches the signature of the partnerLink.
- CWWBV9108E: The process component file ''{0}'' does not contain a reference that corresponds to the outbound partnerLink ''{1}'' in the process implementation file.
- Explanation: The process component file does not contain a reference that matches the signature of the outbound partnerLink ''{1}'' in the process implementation file.
- User Action: Add a reference to the process component file that matches the signature of the partnerLink.
- CWWBV9200E: 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.
- CWWBV9201E: 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, only the Transaction implementation qualifier is allowed.
- CWWBV9202E: 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.
- CWWBV9203E: 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.
- CWWBV9204E: 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 qualifier with a value of 'false'.
- User Action: Change the value of the JoinTransaction interface qualifier to 'false'.
- CWWBV9205E: 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 qualifier with a value of 'false'.
- User Action: Change the value of the JoinTransaction interface qualifier to 'false'.
- CWWBV9206E: 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 qualifier with value of 'true'.
- User Action: Change the value of the JoinTransaction interface qualifier to 'true'.
- CWWBV9207E: 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 qualifier with a value of 'true'.
- User Action: Change the value of the JoinTransaction interface qualifier to 'true'.
- CWWBV9208E: The interface ''{1}'' in the process component file ''{0}'' specifies the JoinTransaction interface qualifier although it is not allowed in 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.
- CWWBV9209E: The operation ''{2}'' of the interface ''{1}'' in the process component file ''{0}'' specifies the JoinTransaction interface qualifier although it is not allowed in 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.
- CWWBV9210E: 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 an activity 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.
- CWWBV9211E: 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.
- CWWBV9212E: 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'.
- CWWBV9213E: The process component file ''{0}'' must specify the implementation qualifier ''Transaction'' with a value of ''local'' and the local transaction boundary with 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 local transaction boundary to 'activity session'.
- User Action: Add the indicated implementation qualifier.
- CWWBV9214E: The process component file ''{0}'' must specify the implementation qualifier ''Transaction'' with a value of ''local'' and the local transaction boundary with 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 local transaction boundary to 'activity session'.
- User Action: Change the indicated implementation qualifier.
- CWWBV9215E: 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.
- CWWBV9216E: The interface ''{1}'' in the process component file ''{0}'' specifies the JoinActivitySession interface 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 JoinActivitySession interface qualifier.
- User Action: Remove the JoinActivitySession interface qualifier from the interface.
- CWWBV9217E: 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.
- CWWBV9218E: 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'.
- CWWBV9219E: The operation ''{2}'' of the interface ''{1}'' in the process component file ''{0}'' specifies the JoinActivitySession interface qualifier although it is not allowed 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.
- CWWBV9220E: The operation ''{2}'' of 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.
- CWWBV9221E: 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.
- CWWBV9222E: 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'.
- CWWBV9223E: 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 a transaction.
- 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.
- CWWBV9224E: 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.
- CWWBV9225E: 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.
- CWWBV9226E: 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.
- CWWBV9227E: 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'.
- CWWBV9228E: 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.
- CWWBV9229E: 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.
- CWWBV9230E: 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.
- CWWBV9231E: 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 for long-running processes.
- User Action: Add the indicated reference qualifier to the reference in the process component file.
- CWWBV9232E: 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.
- CWWBV9300E: 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 cannot be found.
- User Action: Correct the process component file so it points to an existing process implementation file.
- CWWBV9301W: The reference ''{1}'' in the process component file ''{0}'' is wired to another component, but this component is ignored because the corresponding partnerLink has a process template specified.
- Explanation: The partnerLink in the process implementation file specifies a process template. Therefore, the specified partner is chosen during runtime and the wired 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 wire the components, remove the process template specification from the partnerLink in the process implementation file.
- CWWBV9302W: In process onEvent event handler number {2}, parameter number {3}, assigning the ''{0}'' xsd:anyType typed element to the ''{1}'' xsd:anySimpleType typed variable might cause a runtime error.
- Explanation: The xsd:anyType and the xsd:anySimpleType variable must match.
- User Action: Edit the types so that they match.
- CWWBV9303W: In process onEvent event handler number {2}, parameter number {3}, assigning the ''{0}'' xsd:anyType typed part to the ''{1}'' xsd:anySimpleType typed variable might cause a runtime error.
- Explanation: The part of the xsd:anyType and the variable of the xsd:anySimpleType must match.
- User Action: Edit the types so that they match.
- CWWBV9304I: The activity name ''{0}'' is already used.
- Explanation: A duplicate activity name was found.
- User Action: Change the activity name to be unique.