ID_ATTR_NOT_FOUND_CWSIF0305=CWSIF0305E: An id attribute cannot be found for a non-root SOAP body element. Element details: name {0}, namespace {1}. Each non-root SOAP body element should have an id attribute with a unique value. Ensure that your message follows the SOAP encoding rules. JMF_LENGTH_FAILURE_CWSIF0312=CWSIF0312E: Unable to calculate message length: exception {0} This exception is unexpected. The cause is not immediately known. See accompanying error messages for further information. MUST_UNDERSTAND_ERROR_CWSIF0295=CWSIF0295E: Unexpected mustUnderstand value found. Element name {0}, element namespace {1}, mustUnderstand value {2}. The SOAP Parser found a SOAP mustUnderstand attribute with an incorrect value. Ensure the data in the message is compatible with the SOAP specification. PARSE_FAILED_CWSIF0222=CWSIF0222E: The message cannot be parsed: exception {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . ELEMENT_LIST_COPY_ERROR_CWSIF0386=CWSIF0386E: An Exception occurred during the copying of a message element list: {0}. It was not possible to copy a message element list due to the linked Exception. Investigate and resolve the problem described in the linked Exception ENVELOPE_PARSE_ERROR_CWSIF0294=CWSIF0294E: Unexpected element found. Element name {0}, element namespace {1}. The SOAP Parser expected a SOAP Header or Body element, but encountered the above element. Ensure the data in the message is compatible with the SOAP specification. ENVELOPE_PARSE_ERROR_CWSIF0293=CWSIF0293E: Unexpected element found. Element name {0}, element namespace {1}. The SOAP Parser expected a SOAP Envelope element, but encountered the above element. Ensure the data in the message is compatible with the SOAP specification. UNABLE_TO_CREATE_FACTORY_CWSIF0001=CWSIF0001E: A JsMessageFactoryImpl instance cannot be created: exception {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . JMS_FORMAT_ERROR_CWSIF0711=CWSIF0711E: Incorrect format string: {0} The format string does not match any of the format strings recognized for a JMS message. Ensure the message format is correct for a message type supported for JMS messages. UNABLE_TO_CREATE_HANDLEFACTORY_CWSIF0031=CWSIF0031E: A JsMessageHandleFactoryImpl instance cannot be created: exception {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . BEAN_WRITE_FAILURE_CWSIF0342=CWSIF0342E: Unable to write message: exception {0}. An error occured processing a Web Services request, response or fault. See accompanying error messages for further information. BAD_HEX_STRING_CWSIF0200=CWSIF0200E: The hexadecimal string {0} is incorrectly formatted. An attempt to convert from a string to a byte array failed due to the string either containing non-hexadecimal characters, or an odd number of characters. Check the content of the string for which the conversion is failing. JMS_STREAM_READ_IO_ERROR_CWSIF0716=CWSIF0716E: An input/output error occurred in the JMS Data Access Service; exception: {0} An input/output error occurred in SAX processing while trying to parse the body of a JMS stream message Examine the linked exception to determine the problem. HREF_NOT_FOUND_CWSIF0306=CWSIF0306E: An element with id attribute value {0} is not referenced. Each non-root SOAP body element should be referenced by some other part of the message. Ensure that your message follows the SOAP encoding rules. BODY_WSDL_MISMATCH_CWSIF0304=CWSIF0304E: The message body did not match any of the definitions in the WSDL The message body in the SOAP message did not match any of the definitions in the WSDL. This may be because the SOAP message is incorrect or the format string may have identified the wrong WSDL. Ensure the data in the message is compatible with the WSDL. CONTENT_HEADER_CARDINALITY_CWSIF0385=CWSIF0385E: {0} ContentType header entries were found in the message. The implementation only supports messages that contain exactly one ContentType header field. Do not supply messages containing zero, or more than one content-type fields to this utility. NON_MULTIPART_MESSAGE_CWSIF0384=CWSIF0384E: The supplied message is of type {0}, and is not the required type of multipart/related. The implementation does not support the type of the supplied message. Do not supply messages of the specified type to this utility. SOAP_FORMAT_ERROR_CWSIF0274=CWSIF0274E: Incorrect format string: {0} An error occured processing a Web Services request, response or fault. Ensure the message format follows the correct syntax for a SOAP message. JMS_STREAM_TYPE_ERROR_CWSIF0718=CWSIF0718E: An error has occurred while trying to write a JMS stream message containing an element of type {0}. The type of the element in question is not permitted in a JMS stream message. Modify the program to ensure that objects of this type are not inserted into the stream message. ELEMENT_COPY_ERROR_CWSIF0373=CWSIF0373E: An Exception occurred during the copying of a message element: {0}. It was not possible to copy a message element due to the linked Exception. Investigate and resolve the problem described in the linked Exception JMS_STREAM_PARSE_ERROR_CWSIF0715=CWSIF0715E: An error occurred while parsing the payload of a JMS stream message; exception: {0} The payload of the JMS stream message is not valid XML. Examine the linked exception to determine the problem. DIFFERENT_LENGTH_LISTS_CWSIF0700=CWSIF0700E: The map message does not have an equal number of names and values The map name list and map value lists must be the same length. Together they represent the name and value pairs of the map message. Ensure both lists have the same length. ERROR_TRANSCODING_FROM_BYTES_CWSIF0502=CWSIF0502E: An error occurred while attempting to create a message''s payload datagraph from a byte array using format {0}. The linked exception is {1}. The parsing of the byte array to create the DataGraph failed. Examine the linked exception to determine the problem. UNABLE_TO_CREATE_COMPHANDSHAKE_CWSIF0051=CWSIF0051E: A CompHandshakeImpl instance cannot be created: exception {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . NULL_HANDLE_PASSED_FOR_RESTORE_CWSIF0032=CWSIF0032E: {0} passed to SIMessageHandleRestorer. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . UNSUPPORTED_ELEMENT_TYPE_CWSIF0383=CWSIF0383E: The MimeElementList only supports MimeElement entries. The supplied parameter was of type {0}. The MimeElementList is a specialized list implementation that supports only MimeElement list entries. Create a MimeElement object containing the parameter before trying to add it to the list. ERROR_NULL_PAYLOAD_SUPPLIED_CWSIF0504=CWSIF0504E: An error occurred while attempting to create a message''s payload datagraph from a null byte array argument using format {0}. The linked exception is {1}. A non-null byte array is required to build a DataGraph of this format. Examine the linked exception to determine the problem. BAD_MQMD_PROPERTY_TYPE_CWSIF0183=CWSIF0183E: The property {0} should be set using type {1}, not {2}. JMS_IBM_MQMD_ properties must be set using specific variable types. Correct the application code to use the required variable type to set this JMS_IBM_MQMD property. BLOCKED_INPUT_CWSIF0235=CWSIF0235E: Blocking access to input stream for URI: {0}. The run-time environment blocked access to the given URI. This is caused by an attempt to load an XML Schema that has not been deployed to the SDO repository. Ensure that you have deployed appropriate WSDL and XML Schema files to the SDO repository. BEAN_WRITE_FAILURE_CWSIF0325=CWSIF0325E: Unable to write message: exception {0}. An error occured processing a Web Services request, response or fault. See accompanying error messages for further information. BEAN_WRITE_FAILURE_CWSIF0324=CWSIF0324E: Failed to acquire and invoke a method while introspecting an Object representing an enumerated type: type name {0}, namespace {1}, method name {2}, target class name {3}. An error occured processing a Web Services request, response or fault. Ensure that the supplied Objects feature appropriate accessor methods. TRANSCODING_NOT_SUPPORTED_BETWEEN_FORMATS_CWSIF0503=CWSIF0503E: The Transcoding from format {0} to format {1} is not supported. The Transcoding between the current SDO message DataGraph format and the new DataGraph format is not supported. Rewrite the application to use supported function. XSD_ERROR_CWSIF0243=CWSIF0243E: {0} An error was reported while importing an XML Schema. Refer to the error message for more information. SCHEMA_ID_ERROR_CWSIF0221=CWSIF0221E: JMF schema ID error: exception {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . TEMPORARY_CWSIF9999=CWSIF9999E: {0} If the message does not give sufficient information, check the accompanying messages for further help. See the accompanying error messages for further information. SOAP_WRITE_FAILURE_CWSIF0273=CWSIF0273E: Unable to write message: exception {0} An error occured writing a Web Services message. See accompanying error messages for further information. INSTANTIATE_OBJECT_FAILURE_CWSIF0332=CWSIF0332E: Failed to create a new instance of a bean Object: parent type name {2}, property name {0}, namespace {1}, class name {3}. An error occured processing a Web Services request, response or fault. Ensure that the bean Object can be instantiated using Class.newInstance(). RESTORE_FROM_BYTES_ARRAY_TOO_SHORT_CWSIF0033=CWSIF0033E: Data passed to SIMessageHandleRestorer.restoreFromBytes does not have a valid length. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . BINDING_MISSING_CWSIF0603=CWSIF0603E: The format string identified a port named {0} within a service with name {1} and namespace {2} at WSDL location {3}. The port was located, but did not contain a reference to a binding. The format string did not match the definitions in the WSDL. This may be because the WSDL is incomplete or the wrong WSDL has been deployed. Ensure that the port is associated with a binding in the WSDL. INVALID_HREF_CWSIF0307=CWSIF0307E: An element which matches href attribute value {0} cannot be found. A SOAP encoded element uses an href attribute but an element with a matching id attribute cannot be found. Ensure that your message follows the SOAP encoding rules. NON_ROOT_ERROR_CWSIF0297=CWSIF0297E: Incorrect SOAP root attribute found. Element name {0}, element namespace {1}, SOAP root attribute value {2}. The SOAP Parser found an element with an incorrect SOAP root attribute. Ensure the data in the message is compatible with the SOAP specification. NON_ROOT_ERROR_CWSIF0296=CWSIF0296E: Incorrect non-root SOAP body element found. Element name {0}, element namespace {1}. The SOAP Parser found a non-root SOAP body element, but the element is not SOAP encoded. Ensure the data in the message is compatible with the SOAP specification. SOAP_ENCODED_ARRAY_PARSE_FAILURE_CWSIF0334=CWSIF0334E: Failed to locate model for creation of DataObject representing SOAP-encoded array message: namespace {0}, location {1}. An error occured processing a Web Services request, response or fault. Ensure that WSDL or XML Schema definitions are available for the message. SOAP_ENCODED_ARRAY_PARSE_FAILURE_CWSIF0333=CWSIF0333E: Failed to locate model for creation of DataObject representing SOAP-encoded array message: namespace {0}, location {1}. An error occured processing a Web Services request, response or fault. Ensure that WSDL or XML Schema definitions are available for the message. JMS_STREAM_WRITE_ERROR_CWSIF0719=CWSIF0719E: An error occurred while writing the payload of a JMS stream message; exception: {0} An unexpected error has occurred while writing the payload of a JMS stream message to bytes. Examine the linked exception to determine the problem. JMF_PARSE_FAILURE_CWSIF0311=CWSIF0311E: Unable to parse message: exception {0} This exception is unexpected. The cause is not immediately known. See accompanying error messages for further information. UNASSEMBLE_FAILED_CWSIF0214=CWSIF0214E: The JMF message cannot be unassembled: exception {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . MIME_ELEM_ERROR_CWSIF0354=CWSIF0354E: Unexpected element found within message part. Message part name {0}, Element name {1}, element namespace {2}. The SOAP Parser was processing a message part whose content is delegated to a MIME attachment, but the part also contained a nested element. Ensure the data in the message is compatible with the SOAP specification. BAD_HEADER_CHILD_CWSIF0281=CWSIF0281E: Header entry contains wrong number of child data objects. Expected 1, found {0}. The data object representing a header entry did not contain the correct number of child data objects. Ensure that each header entry contains exactly one child. RESTORE_FROM_BYTES_UNKNOWN_VERSION_NUMBER_CWSIF0034=CWSIF0034E: Data passed to SIMessageHandleRestorer.restoreFromBytes does not have valid version information. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . BLOCKED_OUTPUT_CWSIF0236=CWSIF0236E: Blocking access to output stream for URI: {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . SIMPLE_ELEMENT_ERROR_CWSIF0309=CWSIF0309E: Unexpected element found. Element name {0}, element namespace {1}. The XML element contained a simple value, but the value does not fit into the data graph. Ensure that the data in the message is compatible with the types modeled in the WSDL. INVALID_WSDL_CWSIF0240=CWSIF0240E: Unable to locate WSDL {0} with name {1}. The definition was referenced within file {2}. The WSDL importer was unable to locate a definition referenced within the WSDL. Ensure that your WSDL definitions are complete, and that you have included all referenced WSDL files. SOAP_CREATE_FAILURE_CWSIF0276=CWSIF0276E: Unable to create a new SDO DataGraph: exception {0} An error occured processing a Web Services request, response or fault. See accompanying error messages for further information. GET_FIELD_FAILURE_CWSIF0331=CWSIF0331E: Failed to acquire and invoke a method while introspecting a bean Object: parent type name {2}, property name {0}, namespace {1}, method name {3}, target class name {4}. An error occured processing a Web Services request, response or fault. Ensure that the supplied Objects feature appropriate accessor methods. RESOURCE_ERROR_CWSIF0238=CWSIF0238E: An exception was raised while locating Ecore model. Target namespace {0}, location hint {1}, exception {2}. An exception was created while looking up the Ecore model. See accompanying error messages for further information. UNABLE_TO_CREATE_CONTROLFACTORY_CWSIF0041=CWSIF0041E: A ControlMessageFactoryImpl instance cannot be created: exception {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . MIME_REF_NOT_FOUND_CWSIF0357=CWSIF0357E: Unable to locate MIME attachment. Message part name {0}, reference {1}. The SOAP Parser could not find the MIME attachment referenced by the message part. Ensure the data in the message is compatible with the SOAP specification. PORT_MISSING_CWSIF0602=CWSIF0602E: The format string identified a port named {0} within a service with name {1} and namespace {2} at WSDL location {3}. The service was located, but did not contain the named port. The format string did not match the definitions in the WSDL. This may be because the port name in the format is incorrect or the wrong WSDL has been deployed. Ensure that the port name in the format string matches the definition in the WSDL. VALUE_PARSE_ERROR_CWSIF0302=CWSIF0302E: Unexpected text found. Element name {0}, element namespace {1}, data {2} The XML element contained some text, but the WSDL model does not allow this element to contain data. Ensure the data in the message is compatible with the types modeled in the WSDL. VALUE_PARSE_ERROR_CWSIF0301=CWSIF0301E: Unable to parse a value within the message. Type name {0}, type namespace {1}, data {2} The SOAP parser was unable to convert the value into an instance of the type. Ensure the data in the message is compatible with the types modeled in the WSDL. GET_FIELD_FAILURE_CWSIF0326=CWSIF0326E: Failed to acquire and invoke a method while introspecting a bean Object: parent type name {2}, property name {0}, namespace {1}, method name {3}, target class name {4}. An error occured processing a Web Services request, response or fault. Ensure that the supplied Objects feature appropriate accessor methods. INVALID_WSDL_CWSIF0234=CWSIF0234E: Unable to locate element: name {0}, namespace {1}. The WSDL importer was unable to locate an element definition. Ensure that you have included an XML Schema definition of the element in the WSDL types section. INVALID_WSDL_CWSIF0233=CWSIF0233E: Unable to locate type: name {0}, namespace {1}. The WSDL importer was unable to locate a type definition. Ensure that you have included an XML Schema definition of the type in the WSDL types section. INVALID_WSDL_CWSIF0232=CWSIF0232E: Unable to import WSDL file {0}: exception {1} The WSDL importer was unable to import the file. Ensure that you are importing valid WSDL files, and that you are using a supported version of the WSDL standard. BEAN_LENGTH_FAILURE_CWSIF0343=CWSIF0343E: Unable to calculate message length: exception {0}. An error occured processing a Web Services request, response or fault. See accompanying error messages for further information. FAULT_PARSE_FAILURE_CWSIF0330=CWSIF0330E: Failed to create DataObject for SOAP fault message: fault feature name {0}, namespace {1}, location {2}. An error occured processing a Web Services request, response or fault. Ensure that WSDL or XML Schema definitions are available for the message. BLOB_LENGTH_FAILURE_CWSIF0252=CWSIF0252E: Unable to calculate message length: exception {0} This exception is unexpected. The cause is not immediately known. See accompanying error messages for further information. UNABLE_TO_GET_DATAGRAPH_CWSIF0181=CWSIF0181E: The SDO DataGraph cannot be obtained from the message payload. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . PI_PARSE_ERROR_CWSIF0308=CWSIF0308E: Unexpected processing instruction found. Element name {0}, element namespace {1}, target {2}. The XML element contained a processing instruction, but SOAP does not allow elements to contain processing instructions. Ensure the data in the message is compatible with the SOAP specification. JMF_FORMAT_ERROR_CWSIF0315=CWSIF0315E: Incorrect format string: {0} This exception is unexpected. The cause is not immediately known. Ensure the message format follows the correct syntax for the JMF Data Access Service. INVALID_ARGUMENT_CWSIF0381=CWSIF0381E: The supplied value {0} is not valid for the parameter {1} of method {2} A parameter value was supplied that is not permitted for the defined method. Ensure valid parameters are passed to the method in question. MIME_WRITE_FAILURE_CWSIF0335=CWSIF0335E: Failed to write MIME attachment: content type {0}, content transfer encoding {1}, content id {2}. An error occured processing a Web Services request, response or fault. Ensure that the data in the message is suitable for MIME body part creation. INVALID_ARGUMENT_CWSIF0371=CWSIF0371E: The supplied value {0} is not valid for the parameter {1} of method {2} A parameter value was supplied that is not permitted for the defined method. Ensure valid parameters are passed to the method in question. JMS_PARSER_CONFIG_ERROR_CWSIF0714=CWSIF0714E: An error occurred while configuring an XML parser to read a JMS stream message; exception: {0} An unexpected error occurred while configuring an XML parser. Examine the linked exception to determine the problem. SOAP_BUFFER_ERROR_CWSIF0275=CWSIF0275E: Incorrect buffer offsets: Buffer length {0}, Start offset {1}, data length {2}. An error occured processing a Web Services request, response or fault. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . BEAN_FORMAT_ERROR_CWSIF0350=CWSIF0350E: Incorrect format string: {0}. An error occured processing a Web Services request, response or fault. Ensure the message format follows the correct syntax for the Bean Data Access Service. UNABLE_TO_CREATE_JMSFACTORY_CWSIF0011=CWSIF0011E: A JsJmsMessageFactoryImpl instance cannot be created: exception {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . MIME_ATTR_ERROR_CWSIF0355=CWSIF0355E: Unexpected attribute found within message part. Message part name {0}, Attribute name {1}, attribute namespace {2}. The SOAP Parser was processing a message part whose content is delegated to a MIME attachment, but the part also contained an unexpected attribute. Ensure the data in the message is compatible with the SOAP specification. JMF_WRITE_FAILURE_CWSIF0314=CWSIF0314E: Message length {0} does not match the expected length {1} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . JMF_WRITE_FAILURE_CWSIF0313=CWSIF0313E: Unable to write message: exception {0} This exception is unexpected. The cause is not immediately known. See accompanying error messages for further information. SOAP_PARSE_ERROR_CWSIF0291=CWSIF0291E: Unable to parse the message. Error URI {0}, error code {1}, additional data {2} The XML parser has reported an error while processing a SOAP message. Ensure the message is well-formed XML. SET_FIELD_FAILURE_CWSIF0328=CWSIF0328E: Failed to acquire and invoke a method while introspecting a bean Object: parent type name {2}, property name {0}, namespace {1}, method name {3}, target class name {4}. An error occured processing a Web Services request, response or fault. Ensure that the supplied Objects feature appropriate accessor methods. SET_FIELD_FAILURE_CWSIF0327=CWSIF0327E: Failed to acquire and invoke a method while introspecting a bean Object: parent type name {2}, property name {0}, namespace {1}, method name {3}, target class name {4}. An error occured processing a Web Services request, response or fault. Ensure that the supplied Objects feature appropriate accessor methods. MIME_PARSE_FAILURE_CWSIF0329=CWSIF0329E: Failed to parse MIME attachment: content type {0}. An error occured processing a Web Services request, response or fault. Ensure that the supplied Objects are appropriate. ATTRIBUTE_ERROR_CWSIF0310=CWSIF0310E: Unexpected attribute found. Element name {0}, element namespace {1}, attribute name {2}, attribute namespace {3}. The XML element contained an attribute, but the attribute does not fit into the data graph. Ensure the data in the message is compatible with the types modeled in the WSDL. TYPE_MAPPING_FAILURE_CWSIF0348=CWSIF0348E: Failed to map schema type to a Java Class: type name {0}, namespace {1}. An error occured processing a Web Services request, response or fault. Ensure that an appropriate mapping has been provided. TYPE_MAPPING_FAILURE_CWSIF0347=CWSIF0347E: Failed to map schema type to a Java Class: type name {0}, namespace {1}. An error occured processing a Web Services request, response or fault. Ensure that an appropriate mapping has been provided. TYPE_MAPPING_FAILURE_CWSIF0346=CWSIF0346E: Failed to process attribute value: type name {0}, namespace {1}, attribute value {2}. An error occured processing a Web Services request, response or fault. Ensure that the supplied attribute value is of an appropriate type. INCORRECT_ENCAPSULATION_CWSIF0182=CWSIF0182E: The message contains an incorrect encapsulation class: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . FAULT_WRITE_FAILURE_CWSIF0336=CWSIF0336E: Failed to write fault message: message name {0}, operation name {1}. An error occured processing a Web Services request, response or fault. Ensure that the data in the message is suitable for Detail Element creation. UNABLE_TO_CREATE_TRMFACTORY_CWSIF0021=CWSIF0021E: A TrmMessageFactoryImpl instance cannot be created: exception {0}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WSDL_MISSING_CWSIF0600=CWSIF0600E: The format string identified a port named {0} within a service with name {1} and namespace {2} at WSDL location {3}. The WSDL could not be located. The WSDL identified by the format string could not be located. This may be because the location in the format is incorrect or because the WSDL has not been deployed. Ensure that the WSDL location in the format string is correct. UNABLE_TO_GET_CONTENT_CWSIF0382=CWSIF0382E: An IOException occurred while serializing or deserializing the message in method {0} It was not possible to serialize or deserialize the message element due to the linked IOException Investigate and resolve the problem described in the linked IOException SOAP_LENGTH_FAILURE_CWSIF0272=CWSIF0272E: Unable to calculate message length: exception {0} An error occured processing a Web Services request, response or fault. See accompanying error messages for further information. UNABLE_TO_GET_CONTENT_CWSIF0372=CWSIF0372E: An IOException occurred while obtain the content of the message element. It was not possible to deserialize the message element due to the linked IOException Investigate and resolve the problem described in the linked IOException INVALID_XSD_CWSIF0242=CWSIF0242E: Error loading XML Schema: {0} The XML Schema importer was unable to load the file. Ensure that you are importing valid XML Schema files, and that you are using a supported version of the XML Schema standard. INVALID_XSD_CWSIF0241=CWSIF0241E: Unable to import XML Schema file {0}: exception {1} The XML Schema importer was unable to import the file. Ensure that you are importing valid XML Schema files, and that you are using a supported version of the XML Schema standard. UNABLE_TO_CREATE_CWSIF0061=CWSIF0061E: A {0} instance cannot be created: exception {1}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . JMS_TYPE_MISMATCH_ERROR_CWSIF0720=CWSIF0720E: An error occurred in attempting to verify the suitability of a supplied DataObject of type {0} to form the payload of a JMS message with format {1}. The type of the DataObject supplied as the payload of a JMS message must be compatible with the format of that message. Modify the program to ensure that the supplied DataObject and format are compatible. UNEXPECTED_CLASS_INIT_ERROR_CWSIF0721=CWSIF0721E: An error occurred in class initialization, exception: {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . NO_DATA_MEDIATOR_CWSIF0362=CWSIF0362E: The message format {0} is incorrect The message format provided does not match an expected message format. Ensure a correct message format is provided. NIL_ELEMENT_ERROR_CWSIF0299=CWSIF0299E: Element found within nil element. Element name {0}, element namespace {1}, nested element name {2}, nested element namespace {3} The SOAP Parser encountered an element within an element that had an xsi:nil="true" attribute. Ensure the data in the message is compatible with the XML Schema specification. NIL_DATA_ERROR_CWSIF0298=CWSIF0298E: Data found within nil element. Element name {0}, element namespace {1}, data {2}. The SOAP Parser encountered data within an element that had an xsi:nil="true" attribute. Ensure the data in the message is compatible with the XML Schema specification. BLOB_PARSE_FAILURE_CWSIF0251=CWSIF0251E: Unable to parse message: exception {0} This exception is unexpected. The cause is not immediately known. See accompanying error messages for further information. BLOB_MODEL_FAILURE_CWSIF0254=CWSIF0254E: Incorrect message model: type name {0}, namespace {1}. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . NO_DATASLICES_IN_LIST_CWSIF0002=CWSIF0002E: A null or empty DataSlice List was passed to the message restore. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . BEAN_CREATE_FAILURE_CWSIF0338=CWSIF0338E: Unable to create a new SDO DataGraph: exception {0} An error occured processing a Web Services request, response or fault. See accompanying error messages for further information. MIME_IO_ERROR_CWSIF0358=CWSIF0358E: Unable to process MIME attachment. Content ID {0}, Content type {1}, exception {2}. The SOAP Parser encountered an IOException while processing a MIME attachment with the given content id and type. Ensure the data in the message is compatible with the SOAP specification. RESTORE_FROM_BYTES_INTERNAL_LENGTH_CHECK_FAIL_CWSIF0035=CWSIF0035E: Data passed to SIMessageHandleRestorer.restoreFromBytes does not pass internal length validation checks. This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . NO_TYPE_FOR_PART_CWSIF0431=CWSIF0431E: The WSDL Part {0} in message {1} is not associated with a type or element. Each part of a WSDL message must be associated with a XML Schema type or element. Ensure that the definition of each message part includes either the 'type' or 'element' attribute. NOT_API_MESSAGE_CWSIF0101=CWSIF0101E: Message selectors are not supported for message {0}. Message selectors are only supported for API messages. Ensure that the application does not use message selectors for non-API messages. MIME_REF_ERROR_CWSIF0356=CWSIF0356E: Unable to process MIME attachment. Message part name {0}, exception {1}. The SOAP Parser encountered an exception while processing a MIME attachment referenced by the message part. Ensure the data in the message is compatible with the SOAP specification. BEAN_CREATE_FAILURE_CWSIF0322=CWSIF0322E: Failed to create DataObject: parent type name {2}, property name {0}, namespace {1}. An error occured processing a Web Services request, response or fault. Ensure that you have imported WSDL or XML Schema definitions for the message. GET_LENGTH_FAILED_CWSIF0212=CWSIF0212E: The message length cannot be calculated: exception {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . NIL_ATTR_ERROR_CWSIF0300=CWSIF0300E: Attribute found within nil element. Element name {0}, element namespace {1}, attribute name {2}, attribute namespace {3} The SOAP Parser encountered an attribute within an element that had an xsi:nil="true" attribute. Ensure the data in the message is compatible with the XML Schema specification. MAP_NOT_SUPPORTED_AS_SDO_CWSIF0500=CWSIF0500E: A JMS Map Message can not be accessed as an SDO DataGraph. The access of a JMS Map Message through SDO is not supported. Rewrite the application to use supported function. BEAN_PARSE_FAILURE_CWSIF0341=CWSIF0341E: Unable to parse message: exception {0}. An error occured processing a Web Services request, response or fault. See accompanying error messages for further information. JMS_BAD_MODEL_ERROR_CWSIF0713=CWSIF0713E: A DataObject of type {0} is not suitable as the payload of a JMS message. The program is attempting to verify the suitability of a supplied DataObject for forming the payload of a JMS message. Modify the program to supply a DataObject of an appropriate type. SERVICE_MISSING_CWSIF0601=CWSIF0601E: The format string identified a port named {0} within a service with name {1} and namespace {2} at WSDL location {3}. The WSDL was located, but did not contain the named service. The format string did not match the definitions in the WSDL. This may be because the service name or namespace in the format is incorrect or the wrong WSDL has been deployed. Ensure that the service name and namespace in the format string match definitions in the WSDL. JMS_STREAM_WRITE_IO_ERROR_CWSIF0717=CWSIF0717E: An input/output error occurred in the JMS Data Access Service; exception: {0} An input/output error occurred while attempting to write a JMS stream message payload. Examine the linked exception to determine the problem. JMS_WRITE_ERROR_CWSIF0712=CWSIF0712E: The JMS message cannot be serialized, exception: {0} The program is attempting to serialize a JMS message and has failed to do so. Examine the linked exception to determine the problem. XSI_TYPE_ERROR_CWSIF0303=CWSIF0303E: Incorrect xsi:type attribute encountered while processing element name {0}, namespace {1}, xsi:type value {2} The XML element contained an xsi:type attribute, but the value of the attribute could not be processed. Ensure the data in the message is compatible with the XML Schema specification. MESSAGE_FEATURE_CWSIF0353=CWSIF0353E: Failed to locate metadata for message. Service namespace {0}, service name {1}, port name {2}, operation name {3}, message name {4}. The SOAP Parser was unable to locate the message metadata for the given message. Ensure that you have imported WSDL definitions for the message. BEAN_PARSE_FAILURE_CWSIF0323=CWSIF0323E: Unable to determine base type for restriction derived type: type name {0}, namespace {1}. An error occured processing a Web Services request, response or fault. Ensure that the WSDL or XML Schema definitions for the message are correct. BEAN_PARSE_FAILURE_CWSIF0321=CWSIF0321E: Unable to parse message: exception {0}. An error occured processing a Web Services request, response or fault. See accompanying error messages for further information. UNEXPECTED_MESSAGE_TYPE_CWSIF0102=CWSIF0102E: Message type {1} was expected but message type {0} was found. An attempt was made to convert the message from one message type to another message type. This conversion is not supported. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . WRITE_FAILED_CWSIF0213=CWSIF0213E: The message cannot be calculated: exception {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . SOAP_PARSE_FAILURE_CWSIF0271=CWSIF0271E: Unable to parse message: exception {0} An error occured parsing a Web Services message. See accompanying error messages for further information. ERROR_TRANSCODING_TO_BYTES_CWSIF0501=CWSIF0501E: An error occurred while attempting to access a message''s payload datagraph as a byte array. The linked exception is {0}. The serialization of the payload DataGraph failed. Examine the linked exception to determine the problem. NESTED_ERROR_CWSIF0237=CWSIF0237E: An exception was raised while loading included resource. Resource URI: {0}, exception: {1}. The file included a nested resource, and errors were found while loading the nested resource. See accompanying error messages for further information. BAD_HEX_STRING_CWSIF0191=CWSIF0191E: The hexadecimal string {0} is incorrectly formatted for a correlation ID. The string is not a valid hexadecimal correlation ID. It must be of the form ID: followed by an even number of hexadecimal characters only. Correct the string for which the conversion is failing. BLOB_WRITE_FAILURE_CWSIF0253=CWSIF0253E: Unable to write message: exception {0} This exception is unexpected. The cause is not immediately known. See accompanying error messages for further information. FORMAT_NOT_FOUND_CWSIF0211=CWSIF0211E: The message format cannot be identified: exception {0} This exception is unexpected. The cause is not immediately known. If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ .