- CWSCA0001W: \"{0}\" is not a valid Service Component Definition Language file for the following reason: \"{1}\".
- Explanation: The file does not conform to the Service Component Definition Language schema for the reason listed.
- User Action: Check the file to make sure it conforms to the Service Component Definition Language schema.
- CWSCA0002W: The namespace \"{0}\" has already been registered.
- Explanation: Namespaces must have unique names for registration.
- User Action: Use a unique name for the namespace registration.
- CWSCA2001E: The SCA message-driven bean returned the following exception: \"{0}\".
- Explanation: This exception is due to an unhandled code path.
- User Action: Use the exception and the stack trace to report the location of the exception.
- CWSCA2002W: The SCA message-driven bean fails to store error message with id \"{0}\", exception \"{1}\"
- Explanation: The Service Component Architecture message-driven bean did not store the message.
- User Action: Find the destination of the message to see why it is not reachable.
- CWSCA2003W: The SCA message-driven bean failed to retrieve error message with id \"{0}\", exception \"{1}\"
- Explanation: The SCA message-driven bean could not retrieve the message.
- User Action: Find the origination of the message to see why it is not reachable.
- CWSCA2004W: The SCA message-driven bean fails to send error message with id \"{0}\", exception \"{1}\"
- Explanation: The SCA message-driven bean could not send the message.
- User Action: Find the destination of the message to see why it is not reachable.
- CWSCA2005W: The SCA Asynchronous Source Handler was invoked with the wrong interaction type: \"{0}\"
- Explanation: The SCA Asynchronous Source Handler was expecting a different interaction type.
- User Action: Correct or try another interaction type.
- CWSCA2006W: The SCA Asynchronous Target Handler was invoked with the wrong interaction type: \"{0}\"
- Explanation: The SCA Asynchronous Target Handler was expecting a different interaction type.
- User Action: Correct or try another interaction type.
- CWSCA2007E: The SCA link mediation received exception \"{0}\".
- Explanation: This exception is due to an unhandled code path.
- User Action: Use the exception and the stack trace to report the location of the exception.
- CWSCA2008W: The SCA message-driven bean fails to restore the original system classloader, exception \"{0}\"
- Explanation: This exception is due to an unhandled code path.
- User Action: Use the exception and the stack trace to report the location of the exception.
- CWSCA2009W: SCA message-driven bean was invoked without any message driven context
- Explanation: This exception is due to an unhandled code path.
- User Action: Consult the WPS Troubleshooting Guide at http://www.ibm.com/software/integration/wps/support/.
- CWSCA2010W: SCA Component \"{0}\" has attempted to make an asynchronous invocation using the deferred response invocation style against reference \"{1}\". This reference has the qualifier ''deliverAsyncAt'' = \"Commit\". This is a conflict that will cause the invocation to fail. Please change the ''deliverAsyncAt'' qualifier on \"{2}\" to \"Call\".
- Explanation: This is because on an asynchronous invocation using the deferred response invocation style with Commit qualifier, the message may not be delivered to the target until the transaction commits. As a result, there may not be a response from the target and the invokeResponse call will timeout or hang.
- User Action: Please change the "deliverAsyncAt" qualifier on the mentioned reference to \"Call\".
- CWSCA3001I: The SCA runtime is initializing.
- User Action: No user action is needed.
- CWSCA3002I: The SCA runtime has been initialized.
- User Action: No user action is needed.
- CWSCA3003I: The SCA runtime is being destroyed.
- User Action: No user action is needed.
- CWSCA3004I: The SCA runtime has been destroyed.
- User Action: No user action is needed.
- CWSCA3005I: The SCA runtime is starting.
- User Action: No user action is needed.
- CWSCA3006I: The SCA runtime started successfully.
- User Action: No user action is needed.
- CWSCA3007I: The SCA runtime is stopping.
- User Action: No user action is needed.
- CWSCA3008I: The SCA runtime has been stopped.
- User Action: No user action is needed.
- CWSCA3009I: The SCA module \"{0}\" is starting.
- User Action: No user action is needed.
- CWSCA3010I: The SCA module started successfully.
- User Action: No user action is needed.
- CWSCA3011I: The SCA module \"{0}\" is stopping.
- User Action: No user action is needed.
- CWSCA3012I: The SCA module has been stopped.
- User Action: No user action is needed.
- CWSCA3013I: Resources for the SCA application \"{0}\" are being configured.
- User Action: No user action is needed.
- CWSCA3014I: Resources for the SCA application \"{0}\" have been configured successfully.
- User Action: No user action is needed.
- CWSCA3015I: Resources for the SCA application \"{0}\" were not configured.
- User Action: No user action is needed.
- CWSCA3016I: Archive \"{0}\" is being processed.
- User Action: No user action is needed.
- CWSCA3017I: Installation task \"{0}\" is running.
- User Action: No user action is needed.
- CWSCA3018I: Resources for the SCA application \"{0}\" are being removed.
- User Action: No user action is needed.
- CWSCA3019I: Resources for the SCA application \"{0}\" have been removed successfully.
- User Action: No user action is needed.
- CWSCA3020I: The SCA application \"{0}\" is being updated.
- Explanation: The SCA application is being updated.
- User Action: No user action is needed.
- CWSCA3021I: The SCA application \"{0}\" has been updated.
- User Action: No user action is needed.
- CWSCA3022E: The SCA application \"{0}\" was not updated; exception \"{1}\" occurred.
- Explanation: No additional information available.
- User Action: Use the exception and the stack trace to report the location of the exception.
- CWSCA3023I: The EAR file \"{0}\" is being loaded for the SCA module.
- User Action: No user action is needed.
- CWSCA3024W: The operation failed due to exception \"{0}\".
- Explanation: No additional information available.
- User Action: Use the exception and the stack trace to report the location of the exception.
- CWSCA3025E: The SCA runtime detected that artifact loader failed to initialize properly. The error is: \"{0}\"
- Explanation: No additional information available.
- User Action: Use the exception and the stack trace to report the location of the exception.
- CWSCA3026E: The SCA runtime detected that the business object component framework failed to initialize properly. The error is: \"{0}\"
- Explanation: No additional information available.
- User Action: Use the exception and the stack trace to report the location of the exception.
- CWSCA3027E: Before mediating data from one type to another, SCA performed \"{0}\" validation, and found that source type = \"{1}\", source type size = \"{2}\", but target type = \"{3}\", target type size = \"{4}\", so SCA will throw a ClassCastException.
- Explanation: No additional information available.
- User Action: Find why the mediation origin and target do not match.
- CWSCA3028E: Before mediating data from one type to another, SCA performed \"{0}\" validation, and found that source type is \"{1}\", but target type is \"{2}\" with multiplicity \"{3}\", so SCA will throw a ClassCastException.
- Explanation: No additional information available.
- User Action: Find why the mediation origin and target do not match.
- CWSCA3029E: An SCA module with this name \"{0}\" already exists in the cell. This module can not be installed.
- Explanation: No additional information available.
- User Action: Two SCA module with the same name can not be deployed in the same cell. Please make sure the names a unique."
- CWSCA3031E: Should not specify binding type \"{0}\" when using local endpoint \"{1}\"
- Explanation: No additional information available.
- User Action: Modify the application to not specify binding type when local endpoint invocation is made.
- CWSCA3032E: Should not specify import \"{0}\" when using local endpoint \"{1}\"
- Explanation: No additional information available.
- User Action: Modify the application to not specify an import when local endpoint invocation is made.
- CWSCA3033E: Target import not compatible with URI protocol or binding type specified; Target Import: \"{0}\" URI: \"{1}\" BindingType: \"{2}\"
- Explanation: No additional information available.
- User Action: Modify the application so that protocol and binding type (if specified) is compatible with the target import.
- CWSCA3034E: An invalid protocol specified on address URI; URI: \"{0}\" Protocol: \"{1}\"
- Explanation: Supported/valid protocols are (case in-sensitive) : sca, http, https, jms, jca, and wmq
- User Action: Check and update your application accordingly.
- CWSCA3035E: Wired import not compatible with URI protocol specified; Wired import: \"{0}\" URI: \"{1}\"
- Explanation: No additional information available.
- User Action: Modify your application so that URI protocol is compatible with the wired import.
- CWSCA3036E: Cannot perform pure dynamic invocation with binding type: \"{0}\" and URI: \"{1}\"
- Explanation: Note that for invocations over JMS, JCA, WMQ and HTTP bindings, the reference must be wired to a compatible import (unless a target import is specified on the EPR).
- User Action: Check and modify the application accordingly.
- CWSCA4001I: SCA module artifacts are being installed for resource adapter \"{0}\"
- Explanation: SCA module artifacts are being installed for resource adapter.
- User Action: No user action is needed.
- CWSCA4002I: Custom properties for the SCA module resource adapter are being configured.
- Explanation: Custom properties for the SCA module resource adapter are being configured.
- User Action: No user action is needed.
- CWSCA4003I: SCA module \"{0}\" destination on service integration bus \"{1}\" with JNDI name \"{2}\" and type \"{3}\" is being installed.
- Explanation: SCA module destination on service integration bus is being installed.
- User Action: No user action is needed.
- CWSCA4004I: SCA module \"{0}\" destination JNDI name \"{1}\" is being installed.
- Explanation: SCA module destination JNDI name is being installed.
- User Action: No user action is needed.
- CWSCA4005I: SCA module \"{0}\" ActivationSpec JNDI name \"{1}\" is being installed.
- Explanation: SCA module ActivationSpec JNDI name is being installed.
- User Action: No user action is needed.
- CWSCA4006I: SCA module \"{0}\" connection factory JNDI name \"{1}\" is being installed.
- Explanation: SCA module connection factory JNDI name is being installed.
- User Action: No user action is needed.
- CWSCA4007I: SCDL module \"{0}\" is being loaded. Import \"{1}\".
- Explanation: SCDL module import is being loaded.
- User Action: No user action is needed.
- CWSCA4008I: SCDL module \"{0}\" is being loaded. Export \"{1}\".
- Explanation: SCDL module export is being loaded.
- User Action: No user action is needed.
- CWSCA4009I: The JMS response message could not be correlated with the system callback mechanism. Received correlation id: \"{0}\".
- Explanation: A response message was received by the import, but it could not be correlated with a request. This can occur if the response contains incorrect or invalid correlation information or if a previous response with identical correlation information has already been received.
- User Action: Check the response provides the correct correlation information according to the chosen correlation scheme.
- CWSCA4201I: SCA module \"{0}\" JMS artifacts for \"{1}\" are being installed
- Explanation: The JMS import or export binding is being installed.
- CWSCA4202I: Custom properties for the SCA module resource adapter are being configured.
- Explanation: Custom properties for the SIB JMS resource adapter are being configured.
- CWSCA4203I: SCA module \"{0}\" destination on service integration bus \"{1}\" with JNDI name \"{2}\" and type \"{3}\" is being installed.
- Explanation: The destination is being created on the service integration bus.
- CWSCA4204I: SCA module \"{0}\" JMS destination for \"{1}\" with JNDI name \"{2}\" is being installed.
- Explanation: The JMS destination is being created on the server.
- CWSCA4205I: SCA module \"{0}\" ActivationSpec JNDI name \"{1}\" is being installed.
- Explanation: The JMS activation spec is being created on the server.
- CWSCA4206I: SCA module \"{0}\" JMS connection factory for \"{1}\" with JNDI name \"{2}\" is being installed.
- Explanation: The JMS connection factory is being created on the server.
- CWSCA4300I: SCA module \"{0}\" MQ JMS artifacts for \"{1}\" are being installed
- Explanation: The WebSphere MQ JMS import or export binding is being installed.
- CWSCA4301I: SCA module \"{0}\" WebSphere MQ connection factory for \"{1}\" with JNDI name \"{2}\" is being installed.
- Explanation: The WebSphere MQ JMS connection factory is being created on the server.
- CWSCA4302I: SCA module \"{0}\" WebSphere MQ destination for \"{1}\" with JNDI name \"{2}\" is being installed.
- Explanation: The WebSphere MQ JMS destination is being created on the server.
- CWSCA4303I: SCA module \"{0}\" listener port for \"{1}\" with name \"{2}\" is being installed.
- Explanation: The listener port is being created on the server.
- CWSCA4304W: SCA module \"{0}\" Event sequencing is not supported for MQ JMS export binding \"{1}\" in cluster environment
- Explanation: Event sequencing has been specified for the WebSphere MQ JMS export binding, but it is not supported in a clustered environment. Event sequencing will not be enforced.
- User Action: If event sequencing is required, the application cannot be deployed to a cluster.
- CWSCA4400I: SCA module \"{0}\" MQ JMS artifacts for \"{1}\" are being installed
- Explanation: The WebSphere MQ import or export binding is being installed.
- CWSCA4401I: SCA module \"{0}\" WebSphere MQ connection factory for \"{1}\" with JNDI name \"{2}\" is being installed.
- Explanation: The WebSphere MQ JMS connection factory is being created on the server.
- CWSCA4402I: SCA module \"{0}\" WebSphere MQ destination for \"{1}\" with JNDI name \"{2}\" is being installed.
- Explanation: The WebSphere MQ JMS destination is being created on the server.
- CWSCA4403I: SCA module \"{0}\" listener port for \"{1}\" with name \"{2}\" is being installed.
- Explanation: The listener port is being created on the server.
- CWSCA4404W: SCA module \"{0}\" Event sequencing is not supported for MQ export binding \"{1}\" in a clustered environment
- Explanation: Event sequencing has been specified for the MQ export binding, but it is not supported in a clustered environment. Event sequencing will not be enforced.
- User Action: If event sequencing is required, the application cannot be deployed to a cluster.
- CWSCA4500I: SCA module \"{0}\" Generic JMS artifacts for \"{1}\" are being installed
- Explanation: The generic JMS import or export binding is being installed.
- CWSCA4501I: SCA module \"{0}\" Generic JMS connection factory for \"{1}\" with JNDI name \"{2}\" is being installed.
- Explanation: The generic JMS connection factory is being created on the server.
- CWSCA4502I: SCA module \"{0}\" Generic JMS destination for \"{1}\" with JNDI name \"{2}\" is being installed.
- Explanation: The generic JMS destination is being created on the server.
- CWSCA4503I: SCA module \"{0}\" listener port for \"{1}\" with name \"{2}\" is being installed.
- Explanation: The listener port is being created on the server.
- CWSCA4504W: SCA module \"{0}\" Event sequencing is not supported for Generic JMS export binding \"{1}\" in cluster environment
- Explanation: Event sequencing has been specified for the Generic JMS export binding but is not supported in a cluster environment. Event sequencing will not be enforced.
- User Action: If event sequencing is required then the application cannot be deployed to a cluster.
- CWSCA5001I: A messaging engine was not found for the destination. The deployment target \"{0}\" has not been prepared to have SCA applications deployed to it. Prepare \"{0}\" by creating the appropriate messaging engines or defining the server or cluster to host the messaging engines.
- Explanation: Could not find a messaging engine for the destination.
- User Action: Create the appropriate messaging engine.
- CWSCA5002I: Could not find a messaging engine for the destination. The deployment target \"{0}\" has been configured to host destinations at \"{1}\". \"{1}\" has not been prepared for creating the destinations. Prepare \"{1}\" by creating the appropriate messaging engines.
- Explanation: Could not find a messaging engine for the destination.
- User Action: Create the appropriate messaging engine.
- CWSCA5003E: SCA modules can not be deployed to more than one server or cluster in a cell : moduleURI=\"{0}\" target=\"{1}\"
- Explanation: SCA modules must be unique within a cell and can not be deployed to more than one server or cluster.
- User Action: Modify the application deployment attributes such that the sca module is deployed to only server or cluster in a cell.
- CWSCA6001W: The {0} content length will be ignored because the content-encoding header has the value {1}.
- Explanation: The content-length header must not be set when the content-encoding header is enabled.
- User Action: In the data binding, the mediation module or the binding configuration, unset the content-length header. Alternatively, unset the content-encoding header in the binding configuration.
- CWSCA6002W: The {0} content length will be ignored because the transfer-encoding header has the value {1}.
- Explanation: The content-length header must not be set when the transfer-encoding header has value other than "identity".
- User Action: In the data binding, the mediation module or the binding configuration, unset the content-length header or set the transfer-encoding header to "identity" in the binding configuration.
- CWSCA6003W: The {0} header will be ignored. This header must be specified as a control parameter.
- Explanation: Headers exposed through control parameters must always be set in the control parameters structure.
- User Action: In the data binding, the mediation module or the binding configuration, set this header in the control parameters section.
- CWSCA6004W: The {0} HTTP export cannot be found.
- Explanation: The initialization parameter for the HTTP export handler contains the name of a nonexistent export.
- User Action: By using HTTP Export wizard or by manually editing the HTTP binding .export file, specify the valid export.
- CWSCA6005W: The {0} export is not an HTTP export.
- Explanation: The initialization parameter for the HTTP export handler contains the name of an export whose type is not valid.
- User Action: By using HTTP Export wizard or by manually editing the HTTP binding .export file, specify the valid export.
- CWSCA6006W: The {0} HTTP export does not reference an existing function selector.
- Explanation: Either the export does not contain a valid, fully qualified function selector name, or the associated class file does not exist.
- User Action: In the HTTP export editor, specify a valid function selector name.
- CWSCA6007W: The system cannot obtain the Secure Sockets Layer (SSL) settings for the {0} alias. The error is: {1}
- Explanation: The alias that is specified in the Service Component Definition Language (SCDL) file has not been configured in the administrative console.
- User Action: In the administrative console, navigate to Applications > SCA modules > ModuleName > ImportName and create a matching alias as specified in the SCDL file with valid SSL settings. For more information, see http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/c.
- CWSCA6008W: The {0} content encoding that is specified on the Service Component Architecture (SCA) message is not valid, so it is ignored.
- Explanation: The content encoding that is configured on the SCA message is not supported. Supported content encodings are GZIP, XGZIP, DEFLATE, and IDENTITY.
- User Action: Specify a valid content encoding on the SCA message header.
- CWSCA6009W: The HTTP import binding has detected an infinite redirection while processing the request. Attempts at more redirections have stopped.
- Explanation: The target server has continuously redirected to another address. The request is no longer redirected.
- User Action: Contact the network administrator of the target server to obtain the direct address, and update the HTTP import binding with the new URL.
- CWSCA6010W: The {0} user ID with the *********** password in the Service Component Architecture (SCA) message cannot be authenticated with the target server.
- Explanation: No additional information available.
- User Action: Update the authentication settings on the SCA message header with valid credentials .
- CWSCA6011W: The {0} user ID with the *********** password that was retrieved from the {1} alias in the Service Component Definition Language (SCDL) configuration cannot be authenticated with the target server.
- Explanation: The alias in the SCDL definition does not contain valid credentials.
- User Action: In the administrative console, navigate to SCA modules > ModuleName > ImportName, and update the alias with valid credentials.
- CWSCA6012I: The HTTP import binding is sending the request message with the following settings: {0}
- Explanation: The HTTP import binding is processing the request message and is summarizing the settings that are used for the request.
- User Action: No action is required.
- CWSCA6013I: The HTTP import binding has sent the request message and is preparing to parse the response.
- Explanation: No additional information available.
- User Action: No action is required.
- CWSCA6014W: The HTTP import binding does not support messages that contain a payload in the {0} format.
- Explanation: Supported payload formats are DataObject, NativeData, and null.
- User Action: Change the payload on the Service Component Architecture (SCA) message to one of the supported formats, and resend the request message.
- CWSCA6015W: The request cannot be processed because the {0} method is not available in the HTTP import binding.
- Explanation: Binding information for the specified method cannot be obtained. The method that is invoked is not available in the Service Component Definition Language (SCDL) definition.
- User Action: Open the Web Services Description Language (WSDL) definition file, which is in the module project, with the interface editor and add the specified method. Update the .import file, which is also in the module project, with the method binding information. Resend the request.
- CWSCA6016W: The J2EE Connector architecture (J2C) authenication information for the {0} alias that is specified in the Service Component Definition Language (SCDL) configuration cannot be obtained. The error is: {1}
- Explanation: No additional information available.
- User Action: In the administrative console, navigate to SCA modules > ModuleName > ImportName, and create an alias with valid J2C authentication settings to match the alias that is specified in the SCDL file. Resend the request.
- CWSCA6017W: The combination of values for the content encoding ({0}) and the transfer encoding ({1}) that is set on the Service Component Architecture (SCA) message is not valid.
- Explanation: If both content encoding and transfer encoding are specified, at least one of the values must be Identity.
- User Action: If both content encoding and transfer encoding are required for the SCA message, set one of the values as Identity on the SCA message header.
- CWSCA6018W: The combination of values for the content encoding ({0}) and the transfer encoding ({1}) that is set on the Service Component Definition Language (SCDL) configuration is not valid.
- Explanation: If both content encoding and transfer encoding are specified, at least one of the values must be Identity.
- User Action: If both content encoding and transfer encoding are required for the SCDL definition, set one of the values to Identity. To check or modify the values, in the administrative console, navigate to SCA modules > ModuleName > ImportName, and select Identity for one of the values.
- CWSCA6019W: The HTTP method cannot be obtained from the settings that are specified on the request.
- Explanation: The HTTP method cannot be obtained from the settings that are specified on the request.
- User Action: In the administrative console, navigate to SCA modules > ModuleName > ImportName, set the HTTP method on the request message, and resend the request.
- CWSCA6020W: The combination of values for the content encoding ({0}) that is set on the Service Component Architecture (SCA) message and the transfer encoding ({1}) that is set on the Service Component Definition Language (SCDL) configuration is not valid.
- Explanation: If both content encoding and transfer encoding are specified, at least one of the values must be Identity.
- User Action: If both content encoding and transfer encoding are required to be set on the request message, set one of the values to Identity. You can set the content encoding value to Identity on the SCA message header. To set the transfer encoding value to Identity, in the administrative console, navigate to Applications > SCA modules > ModuleName > ImportName, and select Identity.
- CWSCA6021W: The combination of values for the content encoding ({0}) that is set on the Service Component Definition Language (SCDL) configuration and the transfer encoding ({1}) that is set on the Service Component Architecture (SCA) message is not valid.
- Explanation: If both content encoding and transfer encoding are specified, at least one of the values must be Identity.
- User Action: If both content encoding and transfer encoding are required to be set on the request message, set one of the values to Identity. To set the content encoding value to Identity, in the administrative console, navigate to Applications > SCA modules > ModuleName > ImportName, and select Identity. You can set the transfer encoding value to Identity on the SCA message header.
- CWSCA6022W: The HTTP version cannot be obtained from the settings that are specified on the request. The default value 1.1 will be used.
- Explanation: The HTTP version is not set on the Service Component Definition Language (SCDL) configuration or on the Service Component Architecture (SCA) message headers. The default value 1.1 will be used.
- User Action: To set the HTTP version on the Service Component Definition Language (SCDL) configuration, in the administrative console, navigate to Applications > SCA modules > ModuleName > ImportName, and set the version. You can set the HTTP version on the Service Component Architecture (SCA) message header.
- CWSCA6023I: The HTTP import binding has completed the processing of the {0} Service Component Architecture (SCA) message.
- Explanation: No additional information available.
- User Action: No action is required.
- CWSCA6024I: The HTTP import binding has started processing the {0} Service Component Architecture (SCA) message.
- Explanation: No additional information available.
- User Action: No action is required.
- CWSCA6025W: The input data binding for the export, which was obtained from the method-level configuration in the Service Component Definition Language (SCDL) file for the {0} method, cannot be instantiated. The error is: {1}
- User Action: In the SCDL file, verify that the data binding class is available and, if it is an interface or an abstract class, change it.
- CWSCA6026W: The input data binding for the export, which was obtained from the binding-level configuration in the Service Component Definition Language (SCDL) file for the {0} method, cannot be instantiated. The error is: {1}
- User Action: In the SCDL file, Verify that the data binding class is available and, if it is an interface or an abstract class, change it.
- CWSCA6027W: The output data binding for the export, which was obtained from the method-level configuration in the Service Component Definition Language (SCDL) file for the {0} method, cannot be instantiated. The error is: {1}
- User Action: In the SCDL file, Verify that the data binding class is available and, if it is an interface or an abstract class, change it.
- CWSCA6028W: The output data binding for the export, which was obtained from the binding-level configuration in the Service Component Definition Language (SCDL) file for the {0} method, cannot be instantiated. The error is: {1}
- User Action: In the SCDL file, Verify that the data binding class is available and, if it is an interface or an abstract class, change it.
- CWSCA6029W: The input data binding for the import, which was obtained from the method-level configuration in the Service Component Definition Language (SCDL) file for the {0} method, cannot be instantiated. The error is: {1}
- User Action: In the SCDL file, Verify that the data binding class is available and, if it is an interface or an abstract class, change it.
- CWSCA6030W: The input data binding for the import, which was obtained from the binding-level configuration in the Service Component Definition Language (SCDL) file for the {0} method, cannot be instantiated. The error is: {1}
- User Action: In the SCDL file, Verify that the data binding class is available and, if it is an interface or an abstract class, change it.
- CWSCA6031W: The output data binding for the import, which was obtained from the method-level configuration in the Service Component Definition Language (SCDL) file for the {0} method, cannot be instantiated. The error is: {1}
- User Action: In the SCDL file, Verify that the data binding class is available and, if it is an interface or an abstract class, change it..
- CWSCA6032W: The output data binding for the import, which was obtained from the binding-level configuration in the Service Component Definition Language (SCDL) file for the {0} method, cannot be instantiated. The error is: {1}
- User Action: In the SCDL file, Verify that the data binding class is available and, if it is an interface or an abstract class, change it.
- CWSCA6033W: The combination of values for the content encoding ({0}) and the transfer encoding ({1}) for the {2} export that is set on the Service Component Architecture (SCA) message is not valid.
- Explanation: If both content encoding and transfer encoding are specified, at least one of the values must be Identity.
- User Action: If both content encoding and transfer encoding are required for the SCA message, set one of the values as Identity on the SCA message header.
- CWSCA6034W: The combination of values for the content encoding ({0}) and the transfer encoding ({1}) for the {2} export that is set on the Service Component Definition Language (SCDL) configuration is not valid.
- Explanation: If both content encoding and transfer encoding are specified, at least one of the values must be Identity.
- User Action: If both content encoding and transfer encoding are required for the SCDL definition, set one of the values to Identity. To check or modify the values, in the administrative console, navigate to Applications > SCA modules > moduleName > exportName, and select Identity for one of the values.
- CWSCA6035W: The combination of values for the content encoding ({0}) that is set on the Service Component Architecture (SCA) message and the transfer encoding ({1}) that is set on the Service Component Definition Language (SCDL) configuration for the {2} export is not valid.
- Explanation: If both content encoding and transfer encoding are specified, at least one of the values must be Identity.
- User Action: If both content encoding and transfer encoding are required for the request message, set one of the values to Identity. You can set the content encoding value to Identity on the SCA message header. To set the transfer encoding value to Identity, in the administrative console, navigate to Applications > SCA modules > moduleName > exportName, and select Identity.
- CWSCA6036W: The combination of values for the content encoding ({0}) that is set on the Service Component Definition Language (SCDL) configuration and the transfer encoding ({1}) that is set on the Service Component Architecture (SCA) message for the {2} export is not valid.
- Explanation: If both content encoding and transfer encoding are specified, at least one of the values must be Identity.
- User Action: If both content encoding and transfer encoding are required for the request message, set one of the values to Identity. To set the content encoding value to Identity, in the administrative console, navigate to Applications > SCA modules > moduleName > exportName, and select Identity. You can set the transfer encoding value to Identity on the SCA message header.
- CWSCA6037W: The {0} payload format of the Service Component Architecture (SCA) response message for the {1} request message is not valid.
- Explanation: Supported payload formats are DataObject, NativeData, and null.
- User Action: Change the payload format on the SCA message to one of the supported formats, and ask the client to resend the request message.
- CWSCA6038W: The authentication scheme that is used on the authorization header {0} of the {1} request message is not valid.
- Explanation: The only supported authentication scheme is Basic authentication.
- User Action: Ask the client to change the authentication scheme on the authorization header and to resend the request message. The valid value for the authorization header is Basic followed by a space, followed by a base64-encoded user ID and password that are separated by a colon.
- CWSCA6039W: The {0} HTTP method of the {1} request message is not supported.
- Explanation: Supported HTTP methods are GET, HEAD, POST, DELETE, OPTIONS, TRACE, and PUT.
- User Action: Ask the client to change the HTTP method on the request to one of the supported formats and to resend the request message.
- CWSCA6040W: The {0} export cannot be retrieved from the {1} module.
- User Action: Verify that the specified export is available in the specified module, and make it available if it is not. To verify, in the administrative console, navigate to Applications > SCA modules > moduleName > and check if the specified export is available.
- CWSCA6041W: The HTTP export binding cannot instantiate the function selector from the {0} function selector class name, which was obtained from the binding-level configuration in the Service Component Definition Language (SCDL) file. The error is: {1}
- User Action: In the SCDL file, verify that the function selector class is available and, if it is an interface or an abstract class, change it.
- CWSCA6042W: The function selector for the export binding cannot be found in the Service Component Definition Language (SCDL) file.
- User Action: Verify that the function selector class is available in the SCDL file of your module project.
- CWSCA6043W: The {0} authorization header that is set on the {1} request message is malformed.
- User Action: Ask the client to correct the authorization header on the request to a valid syntax and to resend the request message.
- CWSCA6044W: The request cannot be processed because the {0} method is not available in the HTTP export binding.
- Explanation: Binding information for the specified method cannot be obtained. The method that is invoked is not available in the Service Component Definition Language (SCDL) definition.
- User Action: Using the interface editor, open the Web Services Description Language (WSDL) definition file, which is in the module project, and add the specified method. Update the .export file, which is also in the module project, with the method binding information. Resend the request.
- CWSCA6045W: The request cannot be processed because the native method name cannot be generated from the {0} request message. Error: {1}
- User Action: Obtain the request headers and payload, and review the data to determine if any fields are missing. If so, ask the client to resend the request message with all of the necessary information. If a custom function selector is used for the request, troubleshoot the code. To obtain the request details when using a custom function selector or the default function selector that is provided by the binding, start the TCP/IP monitor or change the log level setting to FINER.
- CWSCA6046I: The HTTP export binding has completed the processing of the {0} request message.
- User Action: No action is required.
- CWSCA6047I: The HTTP export binding has started processing the {0} request message.
- User Action: No action is required.
- CWSCA6048W: The HTTP Import received a request with DynamicOverrideURL set. Please use com.ibm.websphere.sca.addressing.EndpointReference APIs or set the /headers/SMOHeader/Target/address field in SMO header to override request destination URL.
- Explanation: DynamicOverrideURL APIs should not be used to set HTTP Import request destination url.
- User Action: For subsequent HTTP Import requests, use EndpointReference APIs or the /headers/SMOHeader/Target/address field in SMO header to set destination url.
- CWSCA8000E: The {0} Java implementation class cannot be found.
- Explanation: The Java class identified in the implementation section of this component is not available to the project.
- User Action: If the class exists, open the dependency editor for the module and add the library or Java project. If the class name is incorrect, select another class for this component by opening the assembly diagram for the module. Select the component and then right-click and select Show in Properties. In the Properties view, select the Implementation tab, and then click Browse. The Select Implementation dialog box opens, allowing you to select the correct Java class. If the class name is correct and you want to create a new class for this implementation, open the assembly diagram for the module. Select the component and run Regenerate Implementation from the context menu.
- CWSCA8001E: The {0} Java interface cannot be found.
- Explanation: A java Interface referenced by this component can not be located in the workspace because it either does not exist or is not in its dependency path.
- User Action: If the Java interface exists, open the dependency editor for the module and add the library or Java project. If the name of the Java interface is incorrect, select another interface for this component by opening the assembly diagram for the module. Select the part and then select Show in Properties from the menu. In the Properties view, select the Details tab, locate the interface, and select Change Interface. If the Java interface should be removed from the part, open the assembly diagram for the module. Select the interface icon or the reference, depending on if the interface is on the part or a reference of the part, and then select Delete.
- CWSCA8002E: The {0} interface cannot have overloaded methods.
- Explanation: All operations for a component, import, or export must have unique names. The specified method is defined twice for the same interface or it is defined for two interfaces. If a Java interface extends a parent Java interface, the Java interface inherits the methods of that parent Java interface, which might lead to the name conflict.
- User Action: Double-click the error message. In the assembly diagram, double-click the error marker on the selected interface. If there are multiple interfaces, select the specified one. In the Java editor, change the name of the specified method. If the Java interface inherits the method from another Java interface, open it with the Java editor and change the name of the method.
- CWSCA8003E: The {0} component name does not match the path of the component file.
- Explanation: The name of the component and component path must match.
- User Action: If you double-click the error message, the assembly editor will open and will update the name of the component to match the path of the component.
- CWSCA8004W: The {0} component has no implementation.
- Explanation: The component implementation cannot be found.
- User Action: Double-click the error message. Right-click the selected component and choose Generate Implementation or Select Implementation.
- CWSCA8005E: The {0} export name does not match the path of the export file.
- Explanation: The name of the export and the export path must match. One of the names might not be specified.
- User Action: If you double-click the error message, the assembly editor will open and will update the name of the export to match the path of the export.
- CWSCA8006E: The {0} target of the export cannot be found.
- Explanation: The value of the target attribute (shown in the assembly diagram as a wire leading from the export) specifies an import or a component that does not exist.
- User Action: Double-click the error message. Right-click the target of the export, which has a dashed outline, and select Create As > Component or Create As > Import to create the target. Alternatively, if you want the export to connect to another target, delete the target with the dashed outline and connect the export to the correct target with a new wire.
- CWSCA8007W: The export does not specify a target component or import.
- Explanation: The target component or import name could not be found.
- User Action: Double-click the error message. Connect a wire from the selected export to a target.
- CWSCA8008E: The {0} import name does not match the path of the import file.
- Explanation: The name for the import and the path do not match. One of the names might not be specified.
- User Action: If you double-click the error message, the assembly editor will open and will update the name of the import to match the path of the import.
- CWSCA8009E: The {0} import name has already been used by another component in the module.
- Explanation: Import names must be unique in each module.
- User Action: If you double-click the error message, the assembly editor will open and fix the error.
- CWSCA8010E: The {0} import has no binding.
- Explanation: All imports must have a binding.
- User Action: Double-click the error message. In the assembly diagram, right-click the selected import and then select Generate Binding.
- CWSCA8011E: The {0} operation cannot be found.
- Explanation: The component, import, export, or stand-alone reference refers to an operation of an interface, but that operation does not exist.
- User Action: Double-click the error message. In the assembly diagram, right-click the selected node and choose Show in Properties. On the Details tab, locate the operation and select it. Where the details of the operation appear, select the specified operation and click Delete operation.
- CWSCA8012E: The {0} module name does not match the name of the project.
- Explanation: The module name must match the name of the enclosing project.
- User Action: Double-click the error message. In the assembly diagram for the module, right-click an empty area in the diagram and select Show in Properties. In the Properties view, click Repair name.
- CWSCA8013E: The {0} target of the wire cannot be found.
- Explanation: The target for this wire can not be located in the workspace.
- User Action: Open the assembly diagram for the module. The target of the wire appears with a dashed outline. To create the target, right-click this target with the dashed outline and select Create As > Component or Create As Import. Or you can delete the image and connect a new wire to the proper target.
- CWSCA8014W: The {0} reference does not specify an interface.
- Explanation: SCA References must specify an Interface.
- User Action: Double-click the error message. Right-click the reference and select Show in Properties. In the Properties view, on details tab, right-click the reference and select Change Interface.
- CWSCA8015W: The {0} reference is not wired to a target component or an import.
- Explanation: A reference normally requires a wire unless it is created for dynamic invocations.
- User Action: If the reference is created for static invocation, wire it by double-clicking the error message and draw a wire from the selected reference to the appropriate target. If the reference is created for dynamic invocation, ignore the warning message.
- CWSCA8016E: The {0} reference with multiplicity 1..1 cannot be wired to more than one target.
- Explanation: A multiplicity value of 1..1 indicates that the reference requires exactly one wire.
- User Action: Double-click the error message and delete all except one wire from the reference.
- CWSCA8017E: The activity session qualifiers that are defined for the interface and for the implementation do not match.
- Explanation: The activity session qualifiers in the interface and implementation must match.
- User Action: Double-click the error message. Right-click the selected component and choose Show in Properties. In the Properties view, on the Details tab, select the interface in the tree. Select the Qualifiers tab and then select the join activity session qualifier. Where its properties are shown, change the value. Alternatively, on the Implementation tab, select the Qualifiers tab and then select the activity session qualifier. Change the value of the activity session qualifier to match the value of the join activity session qualifier for the interface.
- CWSCA8018E: The transaction qualifiers that are defined in the transaction interface and the transaction implementation do not match.
- Explanation: The transaction qualifiers in the interface and implementation must match.
- User Action: Double-click the error message. Right-click the selected component and choose Show in Properties. In the Properties view, on the Details tab, select the interface in the tree. Select the Qualifiers tab and then select the join transaction qualifier. Where its properties are shown, change the value. Alternatively, on the Implementation tab, select the Qualifiers tab and then select the transaction qualifier. Change the value of the transaction qualifier to match the value of the join transaction qualifier for the interface.
- CWSCA8019E: A matching interface cannot be found on the {0} target.
- Explanation: The interface for the source of the wire does not match any of the interfaces in the target of the wire.
- User Action: Double-click the error message and delete the wire. Create a new wire and connect it to a valid target.
- CWSCA8020E: The {0} file extension does not match the root element.
- Explanation: Components must be stored in a file whose type is .component. Imports must be stored in a file whose type is .import. Exports must be stored in a file whose type is .export. The module must be stored in the sca.module file. The stand-alone references must be stored in the sca.references file.
- User Action: In the Physical Resources view, right-click the resource and select Rename. Change the file extension to match the root element.
- CWSCA8021E: An error occurred while validating the Service Component Definition Language (SCDL) file: "{0}.
- Explanation: The specified file could not be validated.
- User Action: Resolve the problems that appear in the Error log. Select Project > Clean and choose Clean all projects.
- CWSCA8022E: The {0} port attribute defined in the Web service export binding cannot be found in the module and dependent libraries.
- Explanation: The End-point specified in the Export Binding can not be found.
- User Action: Double-click the error message. Right-click the export with the error marker and select Replace Binding.
- CWSCA8023E: The import binding contains identical location and namespace values of {0}. (+)
- Explanation: The import binding in the WSDL file should not have identical location and namespace.
- User Action: Change the location to the correct location for the import binding.
- CWSCA8024E: The {0} port attribute that is defined in the Web service import binding cannot be found in the module and dependent libraries.
- Explanation: The port specified in the Web Service Import Binding could not be found in any of the Modules and Libraries in the dependency path of this module.
- User Action: Double-click the assembly editor. In the Properties view, on the Binding tab, click Browse and select an existing port.
- CWSCA8025E: The WSDL portType on the interface cannot be found.
- Explanation: No additional information available.
- User Action: If the interface does not exist, double-click the error message and add an existing interface to the import or export. Right-click the import or export where you added the interface and select Replace Binding. Alternatively, if the interface exists, in the Business Integration view, open the dependencies editor for the module, and add the library that contains the interface as a dependency.
- CWSCA8026E: The name for the {0} operation on the {1} interface is being used.
- Explanation: Each operation for a component, import, or export must have a unique name. Also, two interfaces for the same element cannot have operations with the same name. Duplication might cause runtime errors.
- User Action: Double-click the error message. In the assembly diagram, In the assembly diagram, double-click the selected interface icon and then choose the interface that caused the error. In the interface editor, give the method a unique name.
- CWSCA8027W: The {0} operation has two or more faults with the same name.
- Explanation: No additional information available.
- User Action: In the interface editor, located the specified operation and remove one of the faults with the duplicated name or give all of the faults unique names.
- CWSCA8028E: The interfaces are not of the same type.
- Explanation: All interfaces of an element must all be WSDL interfaces or they must all be Java interfaces. An element cannot have both a WSDL interface and a Java interface.
- User Action: Double-click the error message. In the Properties view, select the Details tab and delete one of the interfaces.
- CWSCA8029W: The {0} module cannot be found.
- Explanation: The sca.module file is not found in this module.
- User Action: Export the module as a project interchange file. In the Business Integration view, delete the module. On the Confirm Module Delete dialog box, select Do not delete contents and click Yes. Recreate the module with the same name. If you lost information, delete this new module and import the original module from the project interchange file.
- CWSCA8030E: The {0} export in the {1} module cannot be found.
- Explanation: No additional information available.
- User Action: Double-click the error message. Right-click the selected import and choose Select Service to Import. Choose an appropriate export.
- CWSCA8031E: The {0} export binding connection type does not implement {1}.
- Explanation: The binding must implement the specified interface.
- User Action: Double-click the error message and add the missing interface to the implements clause of the specified connection.
- CWSCA8032E: The {0} import binding connection type does not implement {1}.
- Explanation: The binding must implement the specified interface.
- User Action: Add the missing interface to the implements clause of the specified connection.
- CWSCA8033E: The {1} property on the {0} class does not have a get method.
- Explanation: The property must have a get method so that its value can be accessed.
- User Action: Add a get method for the specified property to the class.
- CWSCA8034E: The {1} property on {0} does not have a set method.
- Explanation: The property must have a set method so that its value can be updated.
- User Action: Add a set method for the specified property to the class.
- CWSCA8035E: The {0} InteractionSpec type does not implement the {1} InteractionSpec interface.
- Explanation: The specified InteractionSpec type must implement the InteractionSpec interface.
- User Action: Add the InteractionSpec interface to the specified InteractionSpec type.
- CWSCA8036E: The {0} ConnectionSpec type does not implement the {1} ConnectionSpec interface.
- Explanation: The specified ConnectionSpec type must implement the ConnectionSpec interface.
- User Action: Add the ConnectionSpec interface to the specified ConnectionSpec type.
- CWSCA8037E: The {0} InteractionSpec type that is on the method binding for the {1} method does not implement {2}.
- Explanation: The InspectionSpec type on the method binding must implement the InteractionSpec interface.
- User Action: Add the InteractionSpec interface to the specified InteractionSpec type implementation.
- CWSCA8038E: Only one Java interface of type {0} must be present for resource adapter import.
- Explanation: The product only supports one class for import.
- User Action: Edit the resource adapter import so that it recognizes only one class type.
- CWSCA8039E: The method binding must not be present for resource adapter import with Java interface type as {0}.
- Explanation: The interface must not contain the MethodBinding.
- User Action: Remove the method binding from the interface.
- CWSCA8040E: The {0} JMS Export binding response connection type does not implement {1}.
- Explanation: The export binding must implement the specified interface.
- User Action: Add the interface to the response connection type.
- CWSCA8041E: The {0} resource adapter type does not implement the {1} ResourceAdapter interface.
- Explanation: The resource adapter must implement the Resource Adapter interface.
- User Action: Add the interface to the resource adapter type.
- CWSCA8042E: The {0} selector type does not implement {1}.
- Explanation: The specified selector type must implement the FunctionSelector interface.
- User Action: Add the interface and its implementation to the selector.
- CWSCA8043W: {0} cannot be validated.
- Explanation: The class is either not on the class path or a dependency of the class (such as an interface or another class) is not on the class path.
- User Action: Either correct the type on the resource with the error marker, or open the dependencies for the module and add the library or the dependent Java project that contains the class.
- CWSCA8044E: The {0} property cannot have a value of type {2}. The property must have a value of type {1}. (+-)
- Explanation: The property has an incorrect type.
- User Action: Double-click the error message. In the Properties view, on the Binding tab, select the End-point configuration tab and change the property to a valid type.
- CWSCA8045W: The properties on type {0} cannot be validated.
- Explanation: The class cannot be found.
- User Action: If you want the properties to be validated in the next run, add the given class to the class path or change the dependencies of the project.
- CWSCA8046W: The first attribute on the property, {0}, must be "type".
- Explanation: The expected type of the property was not found.
- User Action: Double-click the error message. In the selected property, add the type attribute.
- CWSCA8047E: The {0} operations do not have method bindings.
- Explanation: Each operation must have a method binding.
- User Action: Double-click the error message. In the Properties view, on the Method Bindings tab, add a method binding to each operation and redeploy the application
- CWSCA8048E: The operation is missing for the method binding of the {0} method.
- Explanation: Each method binding must have a matching operation defined on the interface.
- User Action: Double-click the error message. In the Properties view, on the Details tab, add an operation to the interface and redeploy the application
- CWSCA8049E: The target attribute is missing on the connection.
- Explanation: The target attribute must be present on the connection when the resource Adapter element is absent.
- User Action: Double-click the error message. In the Properties view, on the Binding tab, select the End-point configuration sub-tab. On the Connection sub-tab, and add the target attribute for the connection.
- CWSCA8050E: The target attribute is missing on the destination.
- Explanation: The target attribute must be present on the destination when the resourceAdapter element is absent.
- User Action: Double-click the error message. In the Properties view, on the Binding tab, select the End-point configuration sub-tab. On the Connection sub-tab, and add the target attribute for the destination.
- CWSCA8051E: The target attribute is missing on the ResponseConnection.
- Explanation: The target attribute must be present on the ResponseConnection when the resource Adapter element is absent.
- User Action: Double-click the error message. In the Properties view, on the Binding tab, select the End-point configuration sub-tab. On the Connection sub-tab, and add the target attribute for the ResponseConnection.
- CWSCA8052E: A resource adapter archive (RAR) file that contains the {0} type is missing from a valid project.
- Explanation: A RAR file, which is also known as connector project, that contains the specified type must be present in a valid project when the applicationRAR property value is set to "true."
- User Action: Using the dependencies editor, add the connector project to the module. Alternatively, set the applicationRAR property to "false".
- CWSCA8053E: The connection does not have a "type" attribute.
- Explanation: If the applicationRAR property is set to "true", then the connection must have a "type" attribute.
- User Action: Double-click the error message. In the Properties view, on the Binding tab, select the End-point configuration sub-tab. On the Connection sub-tab, add the "type" attribute to the connection. Alternatively, set the applicationRAR property to "false".
- CWSCA8054E: The {0} ListenerType is missing on the classpath or in the dependencies.
- Explanation: The specified ListenerType must be provided.
- User Action: Using the dependencies editor, add the ListenerType to the module.
- CWSCA8055E: An error occurred while generating the following artifact: {0}.
- Explanation: The specified artifact cannot be edited.
- User Action: The error log will give you more information about why this artifact could not be generated.
- CWSCA8056E: An error occurred while the resource references and EJB deployment descriptor contents were being generated: {0}.
- Explanation: No additional information available.
- User Action: The error log will give you more information about why the resource references and EJB deployment descriptor contents could not be generated. Update the resource references and EJB deployment descriptor contents accordingly.
- CWSCA8057E: An error occurred while the data binding was being generated: {0}.
- Explanation: No additional information available.
- User Action: The error log will give you more information about why the data binding could not be generated. Update the data binding accordingly.
- CWSCA8058E: The validation could not complete: {0}.
- Explanation: No additional information available.
- User Action: The error log will give you more information about why the validation could not complete.
- CWSCA8059E: The {1} type of the {0} JMS Header property is not valid.
- Explanation: Invalid JMS Header property specified.
- User Action: Edit the property type of the named JMS header property.
- CWSCA8060E: The artifacts for {0} are missing on the classpath or in the dependencies.
- Explanation: Missing classpath entries for required dependencies.
- User Action: Using the dependencies editor, add the artifact types to the specified project or change the dependencies for this project.
- CWSCA8061E: The import with the {0} SCA binding refering to {1} export in {2} module does not have an SCA binding.
- Explanation: The import has an SCA binding that refers to the specified export, but this export does not have an SCA binding.
- User Action: To change the export that the import refers to, double-click the error message. Right-click the selected import and choose Select Service to Import, and then choose an appropriate export.To change the export to have the SCA binding, open the assembly diagram for the specified module. Right-click the export and select Remove Binding. Right-click the export again and select Generate Binding > SCA Binding.
- CWSCA8062E: No client configuration can be found.
- Explanation: The transport specified is CLIENT and requires either a Client Channel Definition Table or client configuration.
- User Action: In the assembly editor, in the Properties view, on the Binding tab, select the End-point configuration tab. In the Connection Factory tab, specify client configuration properties or change the transport type to BINDINGS. Redeploy the application.
- CWSCA8063E: The {0} property is not specified for the {1} MQ JMS.
- Explanation: The specified property is required.
- User Action: In the assembly editor, in the Properties view, on the Binding tab, set the missing property on the MQ JMS binding and then redeploy the application.
- CWSCA8064E: The cipher suite property is missing.
- Explanation: Because the peer name property is specified, a cipher suite must be specified.
- User Action: In the assembly editor, in the Properties view, on the Binding tab, select the Security attributes tab. In the SSL tab, set the cipher suite property.
- CWSCA8065E: The {0} is missing and is required for {1} MQ JMS.
- Explanation: The MQJMS binding .import or .export file was missing some mandatory information.
- User Action: In the assembly editor, in the Properties view, on the Binding tab, add the missing artifact on the MQ JMS binding and redeploy the application.
- CWSCA8066E: The minimum port is greater than the maximum port.
- Explanation: The minimum port is greater than the maximum port in the local address configuration.
- User Action: In the assembly editor, in the Properties view, on the Binding tab, select the End-point configuration tab. In the Connection Factory tab, edit the minimum port to be less than the maximum port and redeploy the application.
- CWSCA8067E: Digit encoding is specified.
- Explanation: When Use native encoding is specified, the digit encoding property cannot be set to "true".
- User Action: In the assembly editor, in the Properties view, on the Binding tab, select the End-point configuration tab. In the Destination tab, clear the setting of the digit encoding property and redeploy the application.
- CWSCA8068E: The {0} property is not supported unless the transport is {1}.
- Explanation: The feature specified is not compatible with the selected transport type.
- User Action: Modify the transport type or clear the setting of the unsupported property, and then redeploy the application.
- CWSCA8069W: The class cannot be located for the data binding of type {0}.
- Explanation: The data binding implementation class cannot be found.
- User Action: Add the data binding class to the class path or to the application. Redeploy the application.
- CWSCA8070E: The {0} data binding type does not implement the {1} interface.
- Explanation: The data binding class used on the binding does not implement the supported data binding interface.
- User Action: Fix the data binding class by implementing the correct interface. Redeploy the application.
- CWSCA8071E: The {0} local address port has an integer value that is not valid.
- Explanation: The local address port in the MQ or MQJMS connection settings has an invalid integer value. The local address port value must be a positive integer.
- User Action: Replace the integer in the local port address with a valid integer. Redeploy the application.
- CWSCA8072E: {0} was found when correlation scheme type is {1}.
- Explanation: The specified correlation schema is not compatible with the binding type and configuration.
- User Action: In the assembly editor, in the Properties view, on the Binding tab, select the Method Configuration sub-tab and then select another response correlation scheme.
- CWSCA8073E: The callback destination for the {0} binding is missing.
- Explanation: The callback destination is required for the binding if the interface contains two-way operations.
- User Action: In the assembly editor, in the Properties view, on the Binding tab, select the End-point configuration tab . . ., set a callback destination for the binding and redeploy the application.
- CWSCA8074W: The endpoint of the {0} port is incorrect.
- Explanation: The address location specified in the Export Binding is not correct.
- User Action: Double-click the error message. Right-click the export and select Replace Binding. Alternatively, you can continue to use this WSDL file by editing the address location in the WSDL file.
- CWSCA8075W: The export Web Services Description Language (WSDL) exposes the {0} port, which might not be accessible to clients.
- Explanation: Web service clients might require all ports present in the WSDL file to be available.
- User Action: In the WDSL file that contains the port, move the specified port to another WSDL file.
- CWSCA8076E: The Web service binding refers to the {0} Web service port definition, which uses the {1} Web Services Description Language (WSDL) port type.
- Explanation: The parent Web service import or export must expose the specified WSDL port type. A port type is also known as an interface. The interface that the Web service port refers to must match the interface used in the export or import.
- User Action: Double-click the error message. If the import is a Web service, select a port that exposes the correct interface. If the export is a Web service, regenerate the import binding.
- CWSCA8077E: The {0} import has a Web service binding with multiple interfaces.
- Explanation: An import with a Web service binding must have only one interface.
- User Action: Double-click the error message. In the Properties view, on the Details tab, remove all except one interface.
- CWSCA8078E: The {0} export has a Web service binding with multiple interfaces.
- Explanation: An export with a Web service binding must have only one interface.
- User Action: Double-click the error message. In the Properties view, on the Details tab, remove all except one interface.
- CWSCA8079E: The {0} property is not specified for the {1} Generic JMS.
- Explanation: The specified property is required.
- User Action: In the assembly editor, in the Properties view, on the Binding tab, set the missing property on the Generic JMS binding and then redeploy the application.
- CWSCA8080E: The {0} is missing and is required for the {1} Generic JMS.
- Explanation: The Generic JMS binding .import or .export file was missing some mandatory information.
- User Action: In the assembly editor, in the Properties view, on the Binding tab, add the missing artifact on the Generic JMS binding and redeploy the application.
- CWSCA8081E: {0} was found when correlation scheme type is {1}.
- Explanation: The specified correlation schema is not compatible with the binding type and configuration.
- User Action: In the assembly editor, in the Properties view, on the Binding tab, select the Method Configuration sub-tab and then select another response correlation scheme.
- CWSCA8082E: The resource adapter of the {0} type is missing in the class path or in the dependencies.
- Explanation: The resource adapter class is required.
- User Action: Using the dependencies editor, add the resource adapter of the specified type to the module.
- CWSCA8083E: The fault binding of {0} type is missing in the class path or in the dependencies.
- Explanation: The specified fault binding class is required
- User Action: Using the dependencies editor, add the fault binding of the specified type to the module.
- CWSCA8084E: The fault binding of the {0} type does not implement {1}.
- Explanation: The specified fault binding has incorrect interface implementation.
- User Action: In the assembly editor, in the Properties view, on the Binding tab or the Method Bindings tab select the fault binding class that implements the required interface.
- CWSCA8085W: The fault selector of {0} type is missing in the class path or in the dependencies.
- Explanation: The specified fault selector class must be provided.
- User Action: Using the dependencies editor, add the fault selector of the specified type to the module.
- CWSCA8086E: The fault selector of the {0} type does not implement {1}.
- Explanation: The specified fault selector has incorrect interface implmentation.
- User Action: In the assembly editor, in the Properties view, on the Binding tab or the Method Bindings tab select the FaultSelector class implementing the required interface.
- CWSCA8087E: Fault name or binding type or binding reference for one of the fault maps is missing.
- Explanation: Fault name, binding type or binding reference for each fault map must be provided.
- User Action: In the assembly editor, in the Properties view, on the Binding tab or the Method Bindings tab add the values for fault name, binding type or binding reference.
- CWSCA8088E: Fault bindings missing.
- Explanation: When fault selector is present, at least one fault binding is required.
- User Action: In the assembly editor, in the Properties view, on the Binding tab, select the Method Bindings tab and add the Fault Bindings. Fault Bindings can also be specified on the binding according to the requirement.
- CWSCA8089E: Neither selector type nor selector reference was found on the inbound connection.
- Explanation: Either selector type or reference must be provided.
- User Action: In the assembly editor, in the Properties view, on the Binding tab, select the End-point configuration tab. On the Inbound Connection tab, add the selector type or reference.
- CWSCA8090E: The {0} destination of type topic is not supported with a two-way operation.
- Explanation: A destination type of topic with a two-way operation is not supported for this binding.
- User Action: Either change the destination type to queue or change the two-way operation into a one-way operation in either the property view or the export or import file.
- CWSCA8091E: The {0} destination can not be found.
- Explanation: This destination can not be null.
- User Action: Make sure the request destination is specified and the response destinations are existing if this binding has a two-way operation.
- CWSCA8092E: The {0} connection and the {1} destination are on different buses.
- Explanation: The JMS binding requires that both connection and it''s corresponding destination have to be on the same bus if they are specified by the user.
- User Action: The user can either change the bus name property for JMSExport/JMSImport component in WID or change the busName from the .export/.import file.
- CWSCA8093W: A possible incompatibly between the connection factory {0} , and the default callback destination has been detected.
- Explanation: A user defined connection factory has been specified in combination with the default callback destination, this may not work if the connection factory does not connect to the default bus.
- User Action: The user should either use the default connection factory with the default callback destination, or define a different callback destination on the same bus as the response destination.
- CWSCA8094E: Incompatible static MQ headers {0} and {1} found on MQ import binding, method {2}.
- Explanation: The list of static headers defined on the MQ import method binding was found to contain conflicting headers. Some headers cannot be used in combination with each other.
- User Action: Modify the conflicting static header definitions and recompile the project.
- CWSCA9079W: The module name for SCA import {0} is missing.
- Explanation: SCA imports must specify the module name of the target SCA export.
- User Action: Double-click the warning message. Right-click the selected import and choose Select Service to Import, and then choose an appropriate export.
- CWSCA9080W: The target export name for SCA import {0} is missing.
- Explanation: SCA imports must specify a name for the target SCA export.
- User Action: Double-click the warning message. Right-click the selected import and choose Select Service to Import, and then choose an appropriate export.
- CWSCA9081W: The version value for the target export for SCA import {0} is missing.
- Explanation: SCA imports must specify a version value for the target SCA export if the export is owned by a module that has a version declared. If the owning module does not have a version declared this attribute is not required and the warning can be ignored.
- User Action: Double-click the warning message. Right-click the selected import and choose Select Service to Import, and then choose an appropriate export. If the owning module has a version declared the version value will be provided automatically.
- CWSCA9090E: The following error occurred the custom deployment settings for the module were being loaded: {0}.
- Explanation: The reported problem was found while validating the contents of the Custom Deployment.
- User Action: Correct the custom deployment settings so that they are valid.
- CWSCA9091E: The {0} specified in the custom deployment settings could not be found.
- Explanation: The settings specified in the Custom Deployment file are not consistent with the existing settings in the current project.
- User Action: Resolve the reported inconsistency in the custom deployment settings.
- CWSCA9092E: Duplicates were found at the {0} path for {1} in the custom deployment settings.
- Explanation: Duplicate names for items in the custom deployment settings were found. This names are expected to be unique to avoid resolution problems at runtime.
- User Action: In the specified path, change one of the duplicate items so that it is unique in the custom deployment settings.
- CWSCA9093W: The following inconsistent content was found in the custom deployment settings: {0}.
- Explanation: While validating the Custom Deployment settings some items were found to be in conflict with other settings or require items not found in the workspace.
- User Action: Resolve the reported inconsistencyin the custom deployment settings.
- CWSCA9094W: The {0} Web project that is associated with the {1} module does not exist or will not get generated.
- Explanation: The specified Web project, which is in the custom deployment settings, might have been deleted or it might not be necessary for run time, so it will not be generated.
- User Action: If the you want this Web project to be generated, open the assembly diagram for the module and create a Web services export. If the Web project does not exist, it will be created.
- CWSCA9095E: A reference with the name {0} already exists
- Explanation: If two references share the same name, resolution of the reference by name will return an ambiguous result
- User Action: Double-click the error message. Right-click the reference and select Show in Properties. In the Properties view, change the reference name so that it is unique
- CWSCA9096E: The Function Selector in the EJBImportBinding cannot be found.
- Explanation: The Function Selector with the Java fully qualified name cannot be located.
- User Action: In the assembly editor, Properties menu, Bindings tab, add the Function Selector property to the EJB Import.
- CWSCA9097E: A JNDI name in the EJBImportBinding cannot be found.
- Explanation: A JNDI name attribute is either null or empty.
- User Action: In the assembly editor, Properties menu, Bindings tab, add the JNDI Name property to the EJB Import.
- CWSCA9099E: The method field in the EJBImportBinding cannot be found.
- Explanation: A method attribute is either null or empty.
- User Action: In the assembly editor, Properties menu, Bindings tab, Method column, add the method property to the EJB Import.
- CWSCA9100W: The fault binding of the {0} type is missing from the class path or the dependencies.
- Explanation: The specified fault binding class is required.
- User Action: In the dependencies editor, add the fault binding of the specified type to the module.
- CWSCA9101E: The WSDL Fault attribute in the {0} is missing from the WSDL file in the class path or the dependencies.
- Explanation: The specified WSDL fault property is required.
- User Action: In the assembly editor, add the fault attribute to the WSDL file or modify the WSDL Fault attribute in the assembly editor, Properties menu, Bindings tab, Fault Binding field.
- CWSCA9102W: The fault binding of the {0} type is missing from the class path or the dependencies.
- Explanation: The specified fault binding class is required.
- User Action: In the dependencies editor, add the fault binding of the specified type to the module.
- CWSCA9103E: The fault binding of the {0} type does not implement the {1} interface.
- Explanation: The specified fault binding has an incorrect interface implementation.
- User Action: In the assembly editor, in the Properties view, on the Binding tab or the Method Bindings tab select the fault binding class that implements the required interface.
- CWSCA9104W: The fault selector of the {0} type is missing from the class path or the dependencies.
- Explanation: The specified fault selector class is required.
- User Action: In the dependencies editor, add the fault selector of the specified type to the module.
- CWSCA9105E: The fault selector of the {0} type does not implement the {1} interface.
- Explanation: The specified fault selector has an incorrect interface implementation.
- User Action: In the assembly editor, in the Properties view, on the Binding tab or the Method Bindings tab select the Fault Selector class that implements the required interface.
- CWSCA9106W: The function selector of the {0} type is missing from the class path or the dependencies.
- Explanation: The specified function selector class is required.
- User Action: In the dependencies editor, add the function selector of the specified type to the module.
- CWSCA9107E: The function selector of the {0} type does not implement the {1} interface.
- Explanation: The specified function selector has incorrect interface implementation.
- User Action: In the assembly editor, in the Properties view, on the Binding tab or the Method Bindings tab select the Function Selector class that implements the required interface.
- CWSCA9108E: The class cannot be found for the data binding of the {0} type.
- Explanation: In the dependencies editor, add the data binding class to the class path or the application and then redeploy the application.
- User Action: The data binding class is not found
- CWSCA9109E: The {0} data binding type does not implement the {1} interface.
- Explanation: The data binding class that is used on the binding does not implement the supported data binding interface.
- User Action: In the assembly editor, in the Properties view, on the Binding tab or the Method Bindings tab add the Data Handler Type that implements the required interface.
- CWSCA9110W: The class cannot found for the data handler of the {0} type.
- Explanation: The data handler type is not found.
- User Action: In the assembly editor, in the Properties view, on the Binding tab or the Method Bindings tab select the Data Handler class that implements the required interface.
- CWSCA9111E: The {0} data handler type does not implement the {1} interface.
- Explanation: The data handler class that is used on the binding does not implement the supported data handler interface.
- User Action: In the assembly editor, in the Properties view, on the Binding tab or the Method Bindings tab add the Data Handler Type that implements the required interface.
- CWSCA9112E: The fault name does not exist in the fault map.
- Explanation: The fault name is required in a fault map but not found in the fault map.
- User Action: In the assembly editor, in the Properties view, on the Binding tab or the Method Bindings tab select the fault map class that implements the required interface.
- CWSCA9500E: The function selector is not in the HTTP export binding configuration for the {0} export.
- Explanation: The HTTP export binding for the specified export must include a valid function selector.
- User Action: In the assembly editor, select the export. In the Properties view, on the Binding tab, specify the function selector in the export configuration.
- CWSCA9501E: The {0} function selector does not implement the interface commonj.connector.runtime.FunctionSelector on the {1} export.
- Explanation: The function selector must implement the specified interface.
- User Action: In the assembly editor, select the export. In the Properties view, on the Binding tab, browse and select the correct function selector that will implement the interface commonj.connector.runtime.FunctionSelector.
- CWSCA9502E: The {0} data binding or data handler on the {1} component does not implement neither of the following interfaces: com.ibm.websphere.sca.http.data.HTTPStreamDataBinding or commonj.connector.runtime.DataHandler.
- Explanation: The data binding or data handler must implement one of the specified interfaces.
- User Action: In the assembly editor, select the component. In the Properties view, on the Binding tab, browse to and select the correct data binding or data handler that will implement either the interface com.ibm.websphere.sca.http.data.HTTPStreamDataBinding or commonj.connector.runtime.DataHandler.
- CWSCA9503E: No output data binding is available for the {0} method on the {1} component.
- Explanation: The output data binding is required on method or binding levels, but it is missing for this method and this binding.
- User Action: In the assembly editor, select the specified component. In the Properties view, on the Binding tab, select the Method bindings sub-tab and then select the specified bound method from the tree. Select the Data Serialization tab and then browse to and select the correct output data binding.
- CWSCA9504E: No input data binding is available for the {0} method on the {1} component.
- Explanation: The input data binding is required on method or binding levels, but it is missing for this method and this binding.
- User Action: In the assembly editor, select the specified component. In the Properties view, on the Binding tab, select the Method bindings sub-tab and then select the specified bound method from the tree. Select the Data Serialization tab and then browse to and select the correct input data binding.
- CWSCA9505E: No method binding is available for the {0} operation on the {1} component.
- Explanation: The method binding is required for each operation, but it is missing for this operation.
- User Action: In the assembly editor, select the specified component. In the Properties view, on the Binding tab, select the Method bindings sub-tab. Select the unbound method and then select Bind operation.
- CWSCA9506E: No operation is available for the {0} method binding on the {1} component.
- Explanation: The operation is required for each method binding, but it is missing for this method binding.
- User Action: In the assembly editor, select the specified component. In the Properties view, on the Binding tab, select the Method bindings sub-tab. Select the item with the error marker under Bindings for Missing Methods and then select Remove.
- CWSCA9507E: No native methods are available for the {0} method on the {1} export.
- Explanation: At least one native method is required for every method, but one is missing for this method.
- User Action: In the assembly editor, select the specified export. In the Properties view, on the Binding tab, select the Method bindings sub-tab. Select the specified method and, on the Generic tab, add a native method.
- CWSCA9508E: The method binding for the HTTP import or export binding is missing.
- Explanation: HTTP import and export bindings must include at least one method binding.
- User Action: In the assembly editor, provide at least one method binding for each export and import in the binding configuration.
- CWSCA9509E: A duplicate native method ({0}) in the {1} export exists in the {2} module.
- Explanation: A native method must be unique in the HTTP export.
- User Action: In the assembly editor, select the specified export in the module. In the Properties view, on the Binding tab, select Method bindings and modify one of duplicate methods to make it unique.
- CWSCA9510E: The {0} response header name is not valid on the {1} component because it is one of the following names (not case sensitive), which are not allowed: {2}.
- Explanation: The specified response header is not allowed.
- User Action: In the assembly editor, select the specified component. In the Properties view, on the Binding tab, select the Method bindings sub-tab. Select the specified method and, on the HTTP Headers tab, edit the name of the response header so that it is valid.
- CWSCA9511E: A duplicate response header named {0} was found on the {1} export.
- Explanation: Duplicate response headers are not allowed.
- User Action: In the assembly editor, select the specified component. In the Properties view, on the Binding tab, select the Method bindings sub-tab. Select the specified method and, on the HTTP Headers tab, rename of the one the duplicate response headers.
- CWSCA9512E: The context path in the {0} method is missing on the {1} export.
- Explanation: The context path is a required property.
- User Action: In the assembly editor, select the specified export. In the Properties view, on the Binding tab, select the Method bindings sub-tab. Select the specified method and, on the Generic tab, type the name of the context path.
- CWSCA9513E: An HTTP method for the {0} method is missing on the {1} component.
- Explanation: The HTTP method is a required property.
- User Action: In the assembly editor, select the specified component. In the Properties view, on the Binding tab, select the Method bindings sub-tab. Select the specified method and, on the HTTP Method Settings, add the HTTP method to the table.
- CWSCA9514E: The endpoint URL for the {0} method is missing on the {1} import.
- Explanation: The endpoint URL is a required property.
- User Action: In the assembly editor, select the specified import. In the Properties view, on the Binding tab, select the Method bindings sub-tab. Select the specified method and add the endpoint URL.
- CWSCA9515E: The {0} transfer encoding is not valid on the {1} component. The specified transfer encoding must be one of the following (not case sensitive): {2}.
- Explanation: The specified transfer encoding is invalid.
- User Action: Set the transfer encoding to a valid value in the binding configuration.
- CWSCA9516E: The {0} content encoding is not valid on the {1} component because it must be one the following (not case sensitive): {2}.
- Explanation: The specified content encoding is not valid.
- User Action: Set the content encoding to a valid value in the binding configuration.
- CWSCA9517E: The {0} content encoding is not valid for the {1} transfer encoding on the {2} component.
- Explanation: When the transfer encoding is "chunked", the content encoding must be "identity" or it must not be set.
- User Action: Set the content encoding to "identity," or leave it blank in the binding configuration. Alternatively, please set transfer encoding to "identity" so no change to content encoding will be necessary.
- CWSCA9518E: The {0} transfer encoding is not valid for the {1} HTTP version on the {2} import.
- Explanation: The "chunked" transfer encoding is valid only when the HTTP protocol version is 1.1.
- User Action: In the binding configuration, set the HTTP version to 1.1 if the transfer encoding is "chunked".
- CWSCA9519E: The {0} context path for the {1} method on the {2} export is not valid because the path does not start with the forward slash character (/).
- Explanation: The binding configuration requires that the context path start with the forward slash (/) character.
- User Action: In the binding configuration, correct the context path so that it starts with / for this method.
- CWSCA9520E: The {0} combined context path for the {1} method on the {2} export is not valid because the path includes the double forward slash character (//).
- Explanation: The context path must not include the double forward slash character (//).
- User Action: In the binding configuration, correct the context path so that it does not include // for this method.
- CWSCA9521E: The {0} request header name is not valid on the {1} import. The specified request header is one of the following names (not case sensitive), which are not allowed: {2}.
- Explanation: The specified request header is not allowed.
- User Action: In the assembly editor, select the specified import. In the Properties view, on the Binding tab, select the Method bindings sub-tab. Select the specified method and, on the HTTP Headers tab, rename the incorrect request header.
- CWSCA9522E: A duplicate request header named {0} was found on the {1} import.
- Explanation: Duplicate request headers are not allowed.
- User Action: In the assembly editor, select the specified import. In the Properties view, on the Binding tab, select the Method bindings sub-tab. Select the specified method and, on the HTTP Headers tab, rename of the one the duplicate response headers.
- CWSCA9523E: The SSL settings are missing on the {0} import.
- Explanation: If you use the HTTPS protocol in the endpoint URL, you must specify Secure Sockets Layer (SSL) settings.
- User Action: In the assembly editor, select the specified import. In the Properties view, on the Binding tab, select the Method bindings sub-tab. Select the specified method and, on the Security tab, specify SSL Authentication Alias.
- CWSCA9525E: A duplicate context path ({0}) in the {1} export exists in the {2} module.
- Explanation: The specified context path, which is made up of a binding level and a method level, must be unique among all of the HTTP exports in a module.
- User Action: In the assembly editor, select the specified export in the module. In the Properties view, on the Binding tab, select Method bindings and modify the values of one of the context path properties so that the context path is unique.
- CWSCA9526E: A Fault Handler specified at the fault level is missing a {0}.
- Explanation: The Fault Handler {0} is necessary to identify and label faults
- User Action: In the properties of the HTTP Binding, specify a {0}
- CWSCA9527E: Fault Handler is missing fault handler class or configuration for {0} exceptions
- Explanation: A fault handler class or configuration must be specified for {0} exceptions
- User Action: In the properties of the HTTP Binding, specify either a Fault Handler class or configuration for {0} exceptions
- CWSCA9528E: A fault selector has been specified, but required fault handlers are missing
- Explanation: If a fault selector is specified for an HTTP Import, it must have a fault handler specified at the binding level, OR every method binding must have either a method level fault handler or at least one fault level fault handler specified.
- User Action: Either specify a fault handler at the binding level, or specify either a method level handler or at least one fault level fault handler for each method binding.
- CWSCA9530E: A library dependency is declared but either the library name or the library version is missing.
- Explanation: A library dependency requires the declaration of a library name and a library version.
- User Action: In the dependency editor, in the Properties view declare the library name and the library version for the dependent library.
- CWSCA9531E: The module or library version information is missing the version or the version provider.
- Explanation: A module or library version requires the declaration of a version value and the name of the provider of the version value.
- User Action: In the dependency editor, in the Properties view declare the version value and the version provider for the module or library.
- CWSCA9532W: No {0} data format specified for method {1} in MQJMS import or export binding {2}.
- Explanation: No data format is specified on the method binding and no default data format was specified, so any attempt to parse or serialize a message will fail at runtime.
- User Action: Set the data format at the method binding level or set a default data format. Redeploy the application.
- CWSCA9533W: No {0} data format specified for method {1} in JMS import or export binding {2}.
- Explanation: No data format is specified on the method binding and no default data format was specified, so any attempt to parse or serialize a message will fail at runtime.
- User Action: Set the data format at the method binding level or set a default data format. Redeploy the application.
- CWSCA9534W: No {0} data format specified for method {1} in GENJMS import or export binding {2}.
- Explanation: No data format is specified on the method binding and no default data format was specified, so any attempt to parse a message will fail at runtime.
- User Action: Set the data format at the method binding level or set a default data format. Redeploy the application.
- CWSCA9535W: No {0} data format specified for method {1} in MQ import or export binding {2}.
- Explanation: No data format is specified on the method binding and no default data format was specified, so any attempt to parse a message will fail at runtime.
- User Action: Set the data format at the method binding level or set a default data format. Redeploy the application.
- CWSCA9536E: The data binding configuration file for the {0} is not found in the module build path.
- Explanation: The data binding configuration file specified in the import or the export can not be found in the module build path.
- User Action: The user needs to put the data binding configuration file in the module or the depended library. Redeploy the module.
- CWSCA9537W: The fault binding of {0} type is missing in the class path or in the dependencies.
- Explanation: The specified fault binding class is required
- User Action: Using the dependencies editor, add the fault binding of the specified type to the module.