org.camunda.bpm.engine.impl.persistence.entity

Class ByteArrayManager

java.lang.Object

org.camunda.bpm.engine.impl.persistence.AbstractManager

org.camunda.bpm.engine.impl.persistence.entity.ByteArrayManager

All Implemented Interfaces:

Session

public class ByteArrayManager
extends AbstractManager

Author:

Joram Barrez

Constructor Summary

Constructors

Constructor and Description
ByteArrayManager()

Method Summary

Methods

Modifier and Type	Method and Description
void	deleteByteArrayById(String byteArrayEntityId) Deletes the ByteArrayEntity with the given id from the database.

Methods inherited from class org.camunda.bpm.engine.impl.persistence.AbstractManager

checkAuthorization, close, configureQuery, delete, deleteAuthorizations, deleteDefaultAuthorizations, flush, getAttachmentManager, getAuthorizationManager, getByteArrayManager, getCaseDefinitionManager, getCaseExecutionManager, getCaseInstanceManager, getCommandContext, getCurrentAuthentication, getDbEntityManager, getDbSqlSession, getDeploymentManager, getEventSubscriptionManager, getHistoricActivityInstanceManager, getHistoricCaseActivityInstanceManager, getHistoricCaseInstanceManager, getHistoricDetailManager, getHistoricIncidentManager, getHistoricJobLogManager, getHistoricProcessInstanceManager, getHistoricTaskInstanceManager, getHistoricVariableInstanceManager, getIdentityInfoManager, getIdentityLinkManager, getJobDefinitionManager, getJobManager, getProcessDefinitionManager, getProcessInstanceManager, getResourceAuthorizationProvider, getResourceManager, getSession, getTaskManager, getUserOperationLogManager, getVariableInstanceManager, insert, isAuthorizationEnabled, saveDefaultAuthorizations

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

ByteArrayManager

public ByteArrayManager()

Method Detail

deleteByteArrayById

public void deleteByteArrayById(String byteArrayEntityId)

Deletes the ByteArrayEntity with the given id from the database. Important: this operation will NOT do any optimistic locking, to avoid loading the bytes in memory. So use this method only in conjunction with an entity that has optimistic locking!.