java.lang.Object
org.apache.derby.client.am.Lob
- All Implemented Interfaces:
- UnitOfWorkListener
- Direct Known Subclasses:
- Blob, Clob
- public abstract class Lob
- extends java.lang.Object
- implements UnitOfWorkListener
|
Constructor Summary |
protected |
Lob(Agent agent)
|
STRING
public static final int STRING
- See Also:
- Constant Field Values
ASCII_STREAM
public static final int ASCII_STREAM
- See Also:
- Constant Field Values
UNICODE_STREAM
public static final int UNICODE_STREAM
- See Also:
- Constant Field Values
CHARACTER_STREAM
public static final int CHARACTER_STREAM
- See Also:
- Constant Field Values
BINARY_STREAM
public static final int BINARY_STREAM
- See Also:
- Constant Field Values
BINARY_STRING
public static final int BINARY_STRING
- See Also:
- Constant Field Values
agent_
protected Agent agent_
dataType_
protected int dataType_
sqlLength_
protected long sqlLength_
lengthObtained_
protected boolean lengthObtained_
Lob
protected Lob(Agent agent)
finalize
protected void finalize()
throws java.lang.Throwable
- Description copied from class:
java.lang.Object
- Called on an object by the Virtual Machine at most once,
at some point after the Object is determined unreachable
but before it is destroyed. You would think that this
means it eventually is called on every Object, but this is
not necessarily the case. If execution terminates
abnormally, garbage collection does not always happen.
Thus you cannot rely on this method to always work.
For finer control over garbage collection, use references
from the
java.lang.ref package.
Virtual Machines are free to not call this method if
they can determine that it does nothing important; for
example, if your class extends Object and overrides
finalize to do simply super.finalize().
finalize() will be called by a java.lang.Thread that has no
locks on any Objects, and may be called concurrently.
There are no guarantees on the order in which multiple
objects are finalized. This means that finalize() is
usually unsuited for performing actions that must be
thread-safe, and that your implementation must be
use defensive programming if it is to always work.
If an Exception is thrown from finalize() during garbage
collection, it will be patently ignored and the Object will
still be destroyed.
It is allowed, although not typical, for user code to call
finalize() directly. User invocation does not affect whether
automatic invocation will occur. It is also permitted,
although not recommended, for a finalize() method to "revive"
an object by making it reachable from normal code again.
Unlike constructors, finalize() does not get called
for an object's superclass unless the implementation
specifically calls super.finalize().
The default implementation does nothing.
sqlLength
public long sqlLength()
throws SqlException
listenToUnitOfWork
public void listenToUnitOfWork()
- Specified by:
listenToUnitOfWork in interface UnitOfWorkListener
completeLocalCommit
public void completeLocalCommit(java.util.Iterator listenerIterator)
- Specified by:
completeLocalCommit in interface UnitOfWorkListener
completeLocalRollback
public void completeLocalRollback(java.util.Iterator listenerIterator)
- Specified by:
completeLocalRollback in interface UnitOfWorkListener
getAgent
public Agent getAgent()
checkForClosedConnection
void checkForClosedConnection()
throws SqlException
completeLocalRollback
void completeLocalRollback()
completeLocalCommit
void completeLocalCommit()
JAVADOC | 
SOURCE | 
DOWNLOAD | NESTED | FIELD | CONSTR | METHOD