Public Member Functions | |
| void | attachmentAvailable (ERAttachmentProcessor<?> processor, ERAttachment attachment) |
| void | attachmentCreated (ERAttachmentProcessor<?> processor, ERAttachment attachment) |
| void | attachmentNotAvailable (ERAttachmentProcessor<?> processor, ERAttachment attachment, String failureReason) |
| void attachmentAvailable | ( | ERAttachmentProcessor<?> | processor, | |
| ERAttachment | attachment | |||
| ) |
Called when an attachment is made available.
| processor | the attachment processor | |
| attachment | the attachment |
| void attachmentCreated | ( | ERAttachmentProcessor<?> | processor, | |
| ERAttachment | attachment | |||
| ) |
Called when an attachment is created (if you want to sneak in and modify the instance).
| processor | the attachment processor | |
| attachment | the attachment |
| void attachmentNotAvailable | ( | ERAttachmentProcessor<?> | processor, | |
| ERAttachment | attachment, | |||
| String | failureReason | |||
| ) |
Called when an attachment is determined to be unavailable. This provides the opportunity to clean up the attachment in whatever way is appropriate for your application. Note: There is currently a failure mode with this method where it will not be called if the application crashes. If it is essential that you process all unavailable attachments, you may want to handle that at application startup by selecting all of the available = false attachments and running your custom processing on them.
| processor | the attachment processor | |
| attachment | the attachment | |
| failureReason | the reason why the attachment is not available |
1.5.8