Exception Signatures
Operations may throw exceptions. In cases where the underlying Java code throws exceptions that are anticipated, these are translated into xUML exception signatures. For unexpected (not anticipated) exception in the Java code, you may receive a generic xUML exception. The anticipated exceptions and their codes are listed below.
Type/Domain | Code | Description |
|---|---|---|
|
| the connection to host cannot be established |
|
| a to-be-sent-attachment has no content |
|
| a binary to-be-sent-attachment has no filename |
|
| at least one recipient or the sender has an invalid address |
|
| the connected host does not provide the requested protocol |
|
| general uncaught exception while sending |
|
| a generically defined operation is not implemented for a specific protocol (e.g. sendMessage() via IMAP) |
|
| connection specifies an unknown/unsupported protocol |
|
| a specific folder cannot be found or is not supported |
|
| a requested attribute of messages is not supported (raised for exchange only) |
|
| message cannot be retrieved (raised for exchange only) |
|
| native message cannot be concerted to Mail class |
|
| raw message content is not available |
|
| general uncaught exception while retrieving |
|
| messaging exception while retrieving attached nested messages |
|
| general uncaught exception while deleting |
|
| a message cannot be found by its ID |
|
| general uncaught exception while moving |
|
| signature of signed content could not be verified |
|
| the specified keystore could not be loaded |
|
| PGP public key ring cannot be loaded |
|
| cryptographic operation failed due to IO exception, usually a provided key is not in PEM format |
|
| cryptographic pgp related exception |
|
| IPgpKeyProvider not registered or returned NULL, i.e. key could not be retrieved |
Related Content
Related Content: