|
|||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
TxLockManager
manages locks with locktype
'dcr:transaction
'.
todo: removing all expired locks
todo: 'local' and 'global' are not accurate terms in the given context > replace
todo: the usage of the 'global' transaction is not according to the JTA specification,
which explicitely requires any transaction present on a servlet to be completed before
the service method returns. Starting/completing transactions on the session object,
which is possible with the jackrabbit implementation is a hack.
todo: review of this transaction part is therefore required. Is there a use-case
for those 'global' transactions at all...
Method Summary | |
ActiveLock |
getLock(Type type,
Scope scope,
TransactionResource resource)
Return the lock applied to the given resource or null |
void |
releaseLock(TransactionInfo lockInfo,
String lockToken,
TransactionResource resource)
Release the lock identified by the given lock token. |
Methods inherited from interface org.apache.jackrabbit.webdav.lock.LockManager |
createLock, getLock, hasLock, refreshLock, releaseLock |
Method Detail |
public void releaseLock(TransactionInfo lockInfo, String lockToken, TransactionResource resource) throws DavException
lockInfo
- lockToken
- resource
-
DavException
public ActiveLock getLock(Type type, Scope scope, TransactionResource resource)
null
type
- scope
- resource
-
null
LockManager.getLock(org.apache.jackrabbit.webdav.lock.Type, org.apache.jackrabbit.webdav.lock.Scope, org.apache.jackrabbit.webdav.DavResource)
|
|||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |