- CWTKS0001I: Validated the task component model ''{0}'' successfully: {1} information, {2} warnings, {3} errors.
- Explanation: Summary of the successful validation of the task component model.
- User Action: None.
- CWTKS0002I: Validated the task component model ''{0}'' with findings: {1} information, {2} warnings, {3} errors.
- Explanation: Summary of the failed validation of the task component model.
- User Action: Update the task component model to solve the problems.
- CWTKS0003I: Validated task component model ''{0}'' with findings: {1} information, {2} warnings, {3} errors: {4}
- Explanation: Summary of the failed validation of the task component model.
- User Action: Update the task component model to solve the problems.
- CWTKS0050E: Task component validation error: ''{0}''. Error parameters: {1}.
- Explanation: This is a general purpose message that is used 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.
- CWTKS0051W: Task component validation warning: ''{0}''. Warning parameters: {1}.
- Explanation: This is a general purpose message that is used 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.
- CWTKS0052I: Task component validation information: ''{0}''. Information parameters: {1}.
- Explanation: This is a general purpose message that is used when the product is in service and a new information message is needed.
- User Action: None.
- CWTKS0100E: The task component file ''{0}'' contains interfaces and references.
- Explanation: Task component files that refer to a task implementation file must follow these rules: For participating tasks, only one interface and no reference is allowed. For originatingtasks, only one reference and no interface is allowed. Human task component files cannot containa reference or an interface.
- User Action: Correct the task component file so that it contains a valid combination of interfaces and references.
- CWTKS0101E: The task component file ''{0}'' contains more than one interface.
- Explanation: Task component files must not contain more than one interface.
- User Action: Correct the task component file so that it contains only one interface.
- CWTKS0102E: The task component file ''{0}'' contains more than one reference.
- Explanation: Task component files must not contain more than one references.
- User Action: Correct the task component file so that it contains only one reference.
- CWTKS0103E: The interface in the task component file ''{0}'' contains more than one operation.
- Explanation: An interface used in a task component file must not contain more than one operation.
- User Action: Correct the task component file so that it contains only one operation for the interface.
- CWTKS0104E: The reference in the task component file ''{0}'' contains more than one operation.
- Explanation: A reference used in a task component file must not contain more than one operation.
- User Action: Correct the task component file so that it contains only one operation for the reference.
- CWTKS0105E: The reference in the task component file ''{0}'' contains more than one interface.
- Explanation: A reference used in a task component file must not contain more than one interface.
- User Action: Correct the task component file so that it contains only one interface for the reference.
- CWTKS0106E: The interface ''{1}'' in the task component file ''{0}'' needs the preferredInteractionStyle attribute with a value of ''async''.
- Explanation: The indicated interface in the task component file does not contain the specified attribute. This attribute with a value of 'async' is mandatory forparticipating tasks.
- User Action: Add the preferredInteractionStyle attribute with a value 'async' to the interface in the task component file.
- CWTKS0107E: The interface ''{1}'' of the task 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.
- CWTKS0108E: The reference ''{1}'' of the task 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.
- CWTKS0109E: The task 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.
- CWTKS0110E: The task component file ''{0}'' requires either the Transaction or the ActivitySession implementation qualifier.
- Explanation: A task 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 task component file.
- CWTKS0111E: The task component file ''{0}'' must contain the Transaction implementation qualifier with a value of ''global''.
- Explanation: Task 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.
- CWTKS0112E: The task component file ''{0}'' must contain the Transaction implementation qualifier with a value of ''global''.
- Explanation: Task 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'.
- CWTKS0113E: The task component file ''{0}'' requires to have the implementation qualifier ''Transaction'' with value ''local'' and local transaction boundary ''activity session''specified.
- Explanation: For task component files which are specified to run in an activity session, you need to set the implementation qualifier 'Transaction' with value 'local' and localtransaction boundary 'activity session'.
- User Action: Add the indicated implementation qualifier.
- CWTKS0114E: The task component file ''{0}'' requires to have the implementation qualifier ''Transaction'' with value ''local'' and local transaction boundary ''activity session'' specified.
- Explanation: For task component files which are specified to run in an activity session, you need to set the implementation qualifier 'Transaction' with value 'local' and local transactionboundary 'activity session'.
- User Action: Change the indicated implementation qualifier.
- CWTKS0115E: The task component file ''{0}'' specifies the ActivitySession implementation qualifier although it is not allowed in tasks that run in a transaction.
- Explanation: Task component files that run in a transaction cannot use the ActivitySession implementation qualifier.
- User Action: Remove the ActivitySession implementation qualifier.
- CWTKS0116E: The task component file ''{0}'' specifies the ActivitySession implementation qualifier although it is not allowed in participating tasks.
- Explanation: Task component files that specify participating tasks cannot use the ActivitySession implementation qualifier.
- User Action: Remove the ActivitySession implementation qualifier.
- CWTKS0117E: The task component file ''{0}'' does not specify the mandatory ActivitySession implementation qualifier.
- Explanation: Task component files that run in an activity session must specify the ActivitySession implementation qualifier.
- User Action: Add the ActivitySession implementation qualifier to the interface.
- CWTKS0118E: The task component file ''{0}'' does not contain an ActivitySession implementation qualifier with a value of ''true''.
- Explanation: Task 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'.
- CWTKS0119E: The interface ''{1}'' in the task component file ''{0}'' does not specify the mandatory JoinTransaction interface qualifier.
- Explanation: Task component files that run in a global transaction must specify the JoinTransaction interface qualifier.
- User Action: Add the JoinTransaction interface qualifier to the interface.
- CWTKS0120E: The interface ''{1}'' in the task component file ''{0}'' does not contain the JoinTransaction interface qualifier with a value of ''false''.
- Explanation: Task component files that run in a global transaction must contain the JoinTransaction interface qualifierwith a value of 'false'.
- User Action: Change the value of the JoinTransaction interface qualifier to 'false'.
- CWTKS0121E: The operation ''{2}'' of the interface ''{1}'' in the task component file ''{0}'' does not specify the mandatory JoinTransaction interface qualifier.
- Explanation: Task component files that run in a global transaction must specify the JoinTransaction interface qualifier.
- User Action: Add the JoinTransaction interface qualifier to the interface.
- CWTKS0122E: The operation ''{2}'' of the interface ''{1}'' in the task component file ''{0}'' does not contain the JoinTransaction interface qualifier with a value of ''false''.
- Explanation: Task component files that run in a global transaction must contain the JoinTransaction interface qualifierwith a value of 'false'.
- User Action: Change the value of the JoinTransaction interface qualifier to 'false'.
- CWTKS0123E: The reference ''{1}'' in the task component file ''{0}'' specifies the SuspendTransaction reference qualifier although it is not allowed in tasks running in anactivity session.
- Explanation: Task component files that run in an activity session cannot use the SuspendTransaction reference qualifier.
- User Action: Remove the SuspendTransaction reference qualifier from the reference.
- CWTKS0124E: The interface ''{1}'' in the task component file ''{0}'' specifies the JoinActivitySession interface qualifier although it is not allowed in participating tasks.
- Explanation: Task component files that specify participating tasks cannot use the JoinActivitySession interface qualifier.
- User Action: Remove the JoinActivitySession interface qualifier from the interface.
- CWTKS0125E: The operation ''{2}'' of the interface ''{1}'' in the task component file ''{0}'' specifies the JoinActivitySession interface qualifier although it is notallowed in participating tasks.
- Explanation: Task component files that specify participating tasks cannot use the JoinActivitySession interface qualifier.
- User Action: Remove the JoinActivitySession interface qualifier from the interface.
- CWTKS0126E: The reference ''{1}'' in the task component file ''{0}'' specifies the SuspendActivitySession reference qualifier although it is not allowed for tasks running in atransaction.
- Explanation: Task component files that run in a transaction cannot use the SuspendActivitySession reference qualifier.
- User Action: Remove the SuspendActivitySession reference qualifier from the reference.
- CWTKS0127E: The reference ''{1}'' in the task 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 fororiginating tasks.
- User Action: Add the indicated reference qualifier to the reference in the task component file.
- CWTKS0200E: The outbound interface ''{2}'' that is specified by the task implementation file ''{1}'' cannot be located as a reference in the task component file ''{0}''.
- Explanation: If the task implementation file specifies an outbound interface, the task component file must specify the same reference.
- User Action: Correct the task component file so that it contains the reference that the task implementation file specifies.
- CWTKS0201E: The inbound interface ''{2}'' specified by the task implementation file ''{1}'' cannot be located as an interface in the task component file ''{0}''.
- Explanation: If the task implementation file specifies an inbound interface, the task component file must specify the same interface.
- User Action: Correct the task component file so that it contains the interface that the task implementation file specifies.
- CWTKS0202E: The task component file ''{0}'' specifies a reference, but the task implementation file ''{1}'' does not specify an outbound interface.
- Explanation: The task component file must not specify a reference if the task implementation file does not specify an outbound interface.
- User Action: Take one of the following actions: 1)Correct either the task component file or the task implementation file so that the reference in the task component file corresponds to the outbound interfacein the task implementation file 2)Ensure that neither file contains these attributes.
- CWTKS0203E: The task component file ''{0}'' specifies an interface, but the task implementation file ''{1}'' does not specify an inbound interface.
- Explanation: The task component file must not specify an interface if the task implementation file does not specify an inbound interface.
- User Action: Take one of the following actions: 1)Correct either the task component file or the task implementation file so that the reference in the task component file corresponds to the inbound interfacein the task implementation file 2)Ensure that neither file contains these attributes.
- CWTKS0300E: The task implementation file ''{1}'' referenced by the task component file ''{0}'' cannot be found.
- Explanation: The task component file contains a reference to a corresponding task implementation file. This reference is present, but the file to which thisreference points cannot be found.
- User Action: Correct the task component file so that it points to an existing task implementation file.