org.openrdf.jena
Class LockSesame

java.lang.Object
  org.openrdf.jena.LockSesame

All Implemented Interfaces:

Lock

public class LockSesame
extends Object
implements Lock

I pretend to be a jena-lock, but I am actually just a poor sesame transaction. I HOPE that the internal locking in sesame will avoid any problems.

Author:

grimnes

Field Summary

(package private) Repository	repository
(package private) Transaction	transaction

Fields inherited from interface com.hp.hpl.jena.shared.Lock

READ, WRITE

Constructor Summary

LockSesame(Repository rep)

Method Summary

void	enterCriticalSection(boolean write)
void	leaveCriticalSection()

Methods inherited from class java.lang.Object

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

Field Detail

repository

Repository repository

transaction

Transaction transaction

Constructor Detail

LockSesame

public LockSesame(Repository rep)

Method Detail

enterCriticalSection

public void enterCriticalSection(boolean write)

Specified by:

enterCriticalSection in interface Lock

Parameters:

write - - true implies a read lock,false implies write lock.

leaveCriticalSection

public void leaveCriticalSection()

Specified by:

leaveCriticalSection in interface Lock