The object store interface is the application's route to using
a specific object store implementation. The interface dynamically
binds to an implementation of the right type.
This is the base class from which all object store types are derived.
Note that because object store instances are stateless, to improve
efficiency we try to only create one instance of each type per process.
Therefore, the create and destroy methods are used instead of new
and delete. If an object store is accessed via create it *must* be
deleted using destroy. Of course it is still possible to make use of
- Mark Little (firstname.lastname@example.org)
- $Id: ObjectStore.java 2342 2006-03-30 13:06:17Z $
- JTS 1.0.
Some object store implementations may be running with automatic
sync disabled. Calling this method will ensure that any states are
flushed to disk.
localOSRoot the root of the store.
- the full path of the store. localOSRoot is always a relative
name. NOTE this path always ends in a /
if ((localOSRoot == null) || (localOSRoot.length() == 0))
if ((localOSRoot != null) && (localOSRoot.length() > 0))
Does this store need to do the full write_uncommitted/commit protocol?
true if full commit is needed,
Is the current state of the object the same as that provided as the last
u The object to work on.
tn The type of the object.
st The expected type of the object.
true if the current state is as expected,
Initialise the object store.
Suppress directories of the specified type from
Given a type id which is possibly hidden (e.g., has a ! at the
end), make it a valid Uid so we can return it.