Uses of Class
com.atlassian.jira.issue.attachment.AttachmentRuntimeException

Packages that use AttachmentRuntimeException

com.atlassian.jira.issue.attachment

Uses of AttachmentRuntimeException in com.atlassian.jira.issue.attachment

Subclasses of AttachmentRuntimeException in com.atlassian.jira.issue.attachment

class	AttachmentCleanupException Represents a situation where attachments could not be cleaned up.
class	AttachmentDeleteException Represents a case where there was an deleting reading the attachment (e.g.
class	AttachmentMoveException Represents a case where there was an error moving the attachment.
class	AttachmentReadException Represents a case where there was an error reading the attachment (e.g.
class	AttachmentStorageUnavailableException Represents a case where the attachment storage subsystem is unavailable e.g.
class	AttachmentWriteException Represents a case where writing attachment data has failed (e.g.
class	NoAttachmentDataException Represents a case where there is an Attachment record in the database, but no underlying data.
class	TemporaryAttachmentStorageUnavailableException Represents a case where the storage subsystem for temporary attachments (e.g.

Methods in com.atlassian.jira.issue.attachment that throw AttachmentRuntimeException

void	DefaultAttachmentDataBulkImport.importAttachmentDataFrom(ReadOnlyFileBasedAttachmentStore source, int concurrency, com.atlassian.fugue.Option<com.atlassian.util.concurrent.Effect<Attachment>> onCompleteAttachment)
void	AttachmentDataBulkImport.importAttachmentDataFrom(ReadOnlyFileBasedAttachmentStore source, int concurrency, com.atlassian.fugue.Option<com.atlassian.util.concurrent.Effect<Attachment>> onCompleteAttachment) Import attachment data from the specified file system source with specified concurrency, and an optional effect that is run after each attachment is imported (e.g.