- CWSDB0050E: The JMS message passed to the JMS Data Binding {0} is the wrong type, should be {1}, received {2}
- Explanation: The type of the JMS message passed to the JMS Data Binding is the wrong type for the binding.
- User Action: Check that the data binding is configured correctly, and that the function selector is sending the correct message type to the binding.
- CWSDB0060E: Data object passed to {0} is wrong type, should be {1}, received {2}
- Explanation: The type of the data object passed to the JMS Data Binding is the wrong type for the binding.
- User Action: Check that the data binding is configured correctly, and that the binding matches the data type on the runtime interface.
- CWSDB0070E: The JMS message passed to the write() method of {0} is the wrong type, should be {1}, received {2}
- Explanation: The type of the JMS message passed to the JMS Data Binding is the wrong type for the binding.
- User Action: Check that the data binding is configured correctly, and that the binding matches the data type on the runtime interface.
- CWSDB0080E: JMS {0} body contains an invalid object type, {1}
- Explanation: The body of the JMS message passed to the JMS Data Binding contains an invalid type of object.
- User Action: Check that the JMS messaging system is working correctly and no errors are reported when the messages are created.
- CWSDB0090E: An exception was thrown when the JMS Data Binding, {0}, tried to serialize the object from a JMS ObjectMessage, the exception message is {1}
- Explanation: The data binding could not serialize the object contained in the body of a JMS ObjectMessage,
- User Action: Check that the object class is available on the classpath, for example in the ear file.
- CWSDB0100E: An exception was thrown when the JMS Data Binding, {0}, tried to de-serialize the object payload of a data object, the exception is {1}
- Explanation: The data binding could not de-serialize the object contained in the data object in order to write it to a JMS ObjectMessage.
- User Action: Check that the object class is available on the classpath, for example in the ear file.
- CWSDB0110E: An exception was thrown when the JMS Data Binding, {0}, tried to create the data object {1}
- Explanation: The data binding could not create the data object required for the interface.
- User Action: Check that the XML schema definition for the data object is available at runtime.
- CWSDB0150E: The type field of an entry in the data object contains an invalid value, {0}
- Explanation: The data object passed to the data binding has an invalid value in the type field of an entry
- User Action: If the type field was modified at runtime, correct the component that modified it, otherwise contact your system administrator.
- CWSDB0160E: A String representing a byte array in an entry in the data object has the wrong length, {0}, the length should be even.
- Explanation: The data object passed to the data binding has an invalid representation of a byte array value.
- User Action: If the byte array value was modified at runtime, correct the component that modified it, otherwise contact your system administrator.
- CWSDB0170E: A String representing a byte array in an entry in the data object contains an invalid character, {0}
- Explanation: The data object passed to the data binding has an invalid representation of a byte array value.
- User Action: If the byte array value was modified at runtime, correct the component that modified it, otherwise contact your system administrator.
- CWSDB0180E: An exception was thrown in the JMS Data Binding, {0}, while parsing the native message into a data object, the exception is {1}
- Explanation: An exception was thrown whilst parsing the JMS message.
- User Action: Check the nested exception for causes of the error.
- CWSDB9998I: This is a test message
- Explanation: This is a unit test message
- User Action: No action necessary
- CWSDB9999I: This is a test parameterised message: {0}
- Explanation: This is a unit test message
- User Action: No action necessary