- MIMEMODELER_ELEMENT_PART_INVALID_ELEMENT_MIME_TYPE
The mime:content part refers to wsdl:part "{0}", defined using element
attribute. Please make sure t
- MIMEMODELER_INVALID_MIME_CONTENT_MISSING_PART_ATTRIBUTE
Ignoring operation "{0}", missing part attribute in mime:content. part attribute
must be present in
- MIMEMODELER_INVALID_MIME_CONTENT_MISSING_TYPE_ATTRIBUTE
Missing type attribute in mime:content in operation "{0}". part attribute must
be present in mime:co
- MIMEMODELER_INVALID_MIME_PART_MORE_THAN_ONE_SOAP_BODY
Ignoring operation "{0}". The Multipart/Related structure has invalid root part:
more than one soap:
- MIMEMODELER_INVALID_MIME_PART_NAME_NOT_ALLOWED
name attribute on wsdl:part in Operation "{0}" is ignored. Its not allowed as
per WS-I AP 1.0.
- MIMEMODELER_WARNING_IGNORINGINVALID_HEADER_PART_NOT_DECLARED_IN_ROOT_PART
Headers not in root mime:part with soap:body, ignoring headers in operation
"{0}"
- WSDLMODELER_20_RPCENC_NOT_SUPPORTED
rpc/encoded wsdl's are not supported in JAXWS 2.0.
- WSDLMODELER_DUPLICATE_FAULT_SOAP_NAME
ignoring fault "{0}" of operation "{1}", soap:fault name "{2}" is not unique
- WSDLMODELER_ERROR_PARTS_NOT_FOUND
parts "{0}" not found in the message "{1}", wrong WSDL
- WSDLMODELER_ERROR_PART_NOT_FOUND
part "{1}" of operation "{0}" could not be resolved!
- WSDLMODELER_INVALID_BINDING_FAULT_EMPTY_MESSAGE
fault "{0}" refers to message "{1}", but the message has no parts
- WSDLMODELER_INVALID_BINDING_FAULT_MESSAGE_HAS_MORE_THAN_ONE_PART
fault "{0}" refers to message "{1}", but the message has more than one parts