HierarchyManager interface ...
ItemLifeCycleListener interface allows an implementing
object to be informed about changes on an
Interface for low priority tasks (like text extraction) that can be scheduled later based on the extractor's load
SessionListener interface allows an implementing
object to be informed about changes on a
Factory interface for creating
Data object representing a node.
BatchedItemOperations is an internal helper class that
provides both high- and low-level operations directly on the
Implementation of a
HierarchyManager that caches paths of
The security manager acts as central managing class for all security related operations on a low-level non-protected level.
Utility class used to detect path cycles with as little overhead as possible.
Data object referenced by different
ItemImpl instances that
all represent the same item, i.e.
ItemImpl implements the
ItemManager instance per
Utility class for validating an item against constraints specified by its definition.
RepositoryStub implementation for Apache Jackrabbit.
LazyItemIterator is an id-based iterator that instantiates
Items only when they are requested.
NodeImpl implements the
NodeTypeInstanceHandler is used to provide or initialize
system protected properties (or child nodes).
Data object representing a property.
PropertyImpl implements the
ProtectedItemModifier: An abstract helper class to allow classes
residing outside of the core package to modify and remove protected items.
Internal component context of a Jackrabbit content repository.
Tool for backing up or migrating the entire contents (workspaces, version histories, namespaces, node types, etc.) of a repository to a new repository.
Represents a Repository Descriptor Value (either Value or Value)
The repository manager implementation.
Acts as a global entry point to execute queries and index nodes.
Test Content Loader.
A repository proxy that automatically initializes and shuts down the underlying repository instance when the first session is opened or the last one closed.
Derived security manager implementation that expects that users information is present in each workspace instead of having a single, dedicated "security-workspace" that provides user information.
Implementation of the
Session extension that provides XA support.
HierarchyManager implementation that is also able to
build/resolve paths of those items that have been moved or removed
The following table lists the core JCR interfaces and the corresponding Jackrabbit implementation classes found in this package.
A Jackrabbit repository instance can be created using the static
method. Classes in the
package provide a mechanism for binding a Jackrabbit repository in a
JNDI directory context.
SessionImpl instance is created upon successfully login to the
Session is always tied to the
specified in the
Repository#login(Credentials, String) call. A
workspace represents a persistent tree of repository items (i.e.
Propertys). The items in a workspace are 'visible' to all
sessions accessing it (subject to their access rights, of course).
WorkspaceImpl instance represents a specifc workspace as
seen by the session that accesses it.
Every repository item is uniquely identified by its
ItemId. The id
of a node (
NodeId) consists of the node's uuid. The id of a property
PropertyId) consists of the parent node's uuid and the
name of the property.
SessionImpl instance has its own
The per-session instance of
ItemManager acts as item factory (i.e.
PropertyImpl instances) and
provides item access by item id and item caching.
The data (or state) of an item is represented by the following classes in the
SharedItemStateManager for every workspace.
It provides item state caching and it guarantees that there's only one
(persistent) item state instance for any distinct item id in that workspace.
Every session has its own
SessionItemStateManager that consists
of the session's
TransientItemStateManager and the workspace's
Each item (i.e.
is holding an
ItemState instance. When e.g. a session is modifying
a property by changing the property's value, a new transient item state
is created by the session's
transient state is actually wrapping the (old) shared state (copy on write).
PropertyImpl's state is then replaced by the new transient state.
Transient (i.e. unsaved) modifications are 'session-local', i.e. they are not visible to other sessions. When the modifications are saved they become instantly visible to all sessions accessing the same workspace.
Copyright © 2004–2024 The Apache Software Foundation. All rights reserved.