WebSphere Process Server messages     Operating Systems: All supported
CWLBC0002E: There is no native fault named {0} set on the operation {1}
Explanation: The incoming response message had a native fault name that was not set on the opration on the import.
User Action: Set the native fault name on the operation during the configuration of the import in WebSphere Integration Developer.

 

CWLBC0003E: The fault selector must return either Reponse, BusinessFault or RuntimeException, null is not a valid value
Explanation: The fault selector has to fulfill a contract of returning either Response, BusinessFault or RuntimeException as the response. However, the return value in this case is null.
User Action: Change the fault selector implementation so that it returns a fault type that satisfies the fault selector interface contract.

 

CWLBC0004E: The context passed by the binding is null.
Explanation: The specific binding is expected to populate the context and pass it to the binding core.
User Action: The specific binding is invalid.

 

CWLBC0005E: The method binding object passed by the binding is null.
Explanation: The specific binding is expected to pass a valid method binding to the binding core.
User Action: The specific binding is invalid.

 

CWLBC0006E: The import binding object passed by the binding is null.
Explanation: The specific binding is expected to pass a valid import binding to the binding core.
User Action: The specific binding is invalid.

 

CWLBC0007E: The operation information passed by the binding is null.
Explanation: The specific binding is expected to pass a valid operation object to the binding core.
User Action: The specific binding is invalid.

 

CWLBC0008E: The fault on operation {0} and fault {1} is setup with a class, {2} which does not implement DataHandler.
Explanation: The configuration setup on the fault for the operation is not a data handler configuration.
User Action: Go to WebSphere Integration Developer and setup a data handler configuration on the fault for the operation.

 

CWLBC0009E: The fault selector on operation {0} is setup with a class, {1} that does not implement FaultSelector
Explanation: The fault selector configuration setup on the operation is not a fault selector configuration.
User Action: Go to WebSphere Integration Developer and setup a fault selector configuration on the operation.

 

CWLBC0010E: There is no data handler setup to handle the fault {0} on operation {1}.
Explanation: To handle faults on an operation, a data handler has to be setup either at binding, method or fault level.
User Action: Go to WebSphere Integration Developer and setup a data handler on the fault on the operation.

 

CWLBC0011E: There is no fault named {0} set on the operation {1} in the interface set on the binding.
Explanation: The wsdl fault name obtained from the binding is not set on the operation on the interface on the binding.
User Action: Go to WebSphere Integration Developer and modify the interface set on the binding to add the wsdl fault to the operation or modify the binding to add the correct wsdl fault on it.

 

CWLBC0012E: Failed to the load the class {0} while processing the configuration.
Explanation: The class that is setup in the configuration for the faults cannot be loaded because it is either not available in or visible to the module.
User Action: Ensure that the class setup in the fault configuration is available in the module or is visible to the module that is using it.

 


Reference topic

Terms of use | Feedback

Timestamp icon Last updated: 9 June 2009