A collection of errors.
public EBErrorList getErrors(); public void setErrors(EBErrorList errors);
This property is populated with error information. There may be one or more errors.
Common errors defined in the ebMS specifications are listed below for reference.
|Error Code||Short Description||Severity||Category||Description|
|EBMS:0001||ValueNotRecognized||failure||Content||Although the message document is well formed and schema valid, some element/attribute contains a value that could not be recognized and therefore could not be used by the MSH|
|EBMS:0002||FeatureNotSupported||warning||Content||Although the message document is well formed and schema valid, some element/attribute value cannot be processed as expected because the related feature is not supported by the MSH.|
|EBMS:0003||ValueInconsistent||failure||Content||Although the message document is well formed and schema valid, some element/attribute value is inconsistent either with the content of other element/attribute, or with the processing mode of the MSH, or with the normative requirements of the ebMS specification.|
|EBMS:0005||ConnectionFailure||failure||Communication||The MSH is experiencing temporary or permanent failure in trying to open a transport connection with a remote MSH.|
|EBMS:0006||EmptyMessagePartitionChannel||warning||Communication||There is no message available for pulling from this MPC at this moment.|
|EBMS:0007||MimeInconsistency||failure||Unpackaging||The use of MIME is not consistent with the required usage in this specification.|
|EBMS:0008||FeatureNotSupported||failure||Unpackaging||Although the message document is well formed and schema valid, the presence or absence of some element/ attribute is not consistent with the capability of the MSH, with respect to supported features.|
|EBMS:0009||InvalidHeader||failure||Unpackaging||The ebMS header is either not well formed as an XML document, or does not conform to the ebMS packaging rules|
|EBMS:0010||ProcessingModeMismatch||failure||Processing||The ebMS header or another header (e.g. reliability, security) expected by the MSH is not compatible with the expected content, based on the associated P-Mode.|
|EBMS:0011||ExternalPayloadError||failure||Content||The MSH is unable to resolve an external payload reference (i.e. a Part that is not contained within the ebMS Message, as identified by a PartInfo/href URI).|
|EBMS:0101||FailedAuthentication||failure||Processing||The signature in the Security header intended for the "ebms" SOAP actor, could not be validated by the Security module.|
|EBMS:0102||FailedDecryption||failure||Processing||The encrypted data reference the Security header intended for the "ebms" SOAP actor could not be decrypted by the Security Module.|
|EBMS:0103||PolicyNoncompliance||failure||Processing||The processor determined that the message's security methods, parameters, scope or other security policy-level requirements or agreements were not satisfied.|
|EBMS:0201||DysfunctionalReliability||failure||Processing||Some reliability function as implemented by the Reliability module, is not operational, or the reliability state associated with this message sequence is not valid|
|EBMS:0202||DeliveryFailure||failure||Communication||Although the message was sent under Guaranteed delivery requirement, the Reliability module could not get assurance that the message was properly delivered, in spite of resending efforts.|
|EBMS:0301||MissingReceipt||failure||Communication||A Receipt has not been received for a message that was previously sent by the MSH generating this error.|
|EBMS:0302||InvalidReceipt||failure||Communication||A Receipt has been received for a message that was previously sent by the MSH generating this error, but the content does not match the message content (e.g. some part has not been acknowledged, or the digest associated does not match the signature digest, for NRR).|
|EBMS:0303||Decompression-Failure||failure||Communication||An error occurred during the decompression.|