|
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Objectgoodsjpi.Metaobject
goodsjpi.BasicMetaobject
goodsjpi.PessimisticMetaobject
PessimisticMetaobject
for pessimistic scheme of synchronization.
Or would it be realistic.
Or Multiple Reader, one writer.
Field Summary |
Fields inherited from class goodsjpi.Metaobject |
CONSTRUCTOR, EXCEPTION, MUTATOR, VARIABLE |
Constructor Summary | |
PessimisticMetaobject()
|
Method Summary | |
void |
beginReadAccess(Persistent obj)
beginReadAccess is a no-op. |
void |
beginWriteAccess(Persistent obj)
beginWriteAccess locks the object. |
void |
endAccess(Persistent obj)
endAccess adds the object to the cahce managers transaction list |
Methods inherited from class goodsjpi.Metaobject |
modify, mutator |
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
Constructor Detail |
public PessimisticMetaobject()
Method Detail |
public void beginWriteAccess(Persistent obj)
beginWriteAccess
locks the object. That is, the objects storage
manager is requested to objeain the lock from the server.
beginWriteAccess
in class Metaobject
obj
- a Persistent
to be modified.public void beginReadAccess(Persistent obj)
beginReadAccess
is a no-op. So, no locking for read's. Multiple
readers, one writer.
beginReadAccess
in class Metaobject
obj
- a Persistent
object to be read.public void endAccess(Persistent obj)
endAccess
adds the object to the cahce managers transaction list
endAccess
in class Metaobject
obj
- a Persistent
value
|
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |