|
||||||||||
PREV NEXT | FRAMES NO FRAMES |
SynchronizationAction
implementations
that mutate the RepositoryContentMetadata
as part of their
function.ContentMetadataPersister
.ContentModification
from a pair
of RepositoryContentMetadata
.File
.LocalContentManager
implementation.Identifiable
metadata and also provide efficient lookup capability
based on a child item's id
.SynchronizationAction
implementations.SynchronizationPolicy
.false
Should the item represented by toAdd
that is available
on a newly joining node be accepted for use around the cluster
when the cluster's records show no record of an item with the same path?
Such a case potentially could mean newly joining node was unaware of an
earlier removal that occurred while it was offline and that the cluster
has also purged
from its records
.
toAdd
that is available
on a newly joining node be accepted for use around the cluster
when the cluster's records show no record of an item with the same path?
Such a case potentially could mean newly joining node was unaware of an
earlier removal that occurred while it was offline and that the cluster
has also purged
from its records
.
false
Should the item represented by reincarnation
that is available
on a newly joining node be accepted for use around the cluster when
the cluster's records show an item with the same path was previously
removed? Such a case potentially could mean the newly joining node
was unaware of a removal that occurred while it was offline.
reincarnation
that is available
on a newly joining node be accepted for use around the cluster when
the cluster's records show an item with the same path was previously
removed? Such a case potentially could mean the newly joining node
was unaware of a removal that occurred while it was offline.
false
Should the item represented by toRemove
that is unavailable
on a merging set of nodes be removed from around the cluster when
the cluster's records show an item with the same path? Such a case
potentially could mean the newly joining node was unaware of a new
deployment of the item that occurred while it was offline.
toRemove
that is unavailable
on a merging set of nodes be removed from around the cluster when
the cluster's records show an item with the same path? Such a case
potentially could mean the newly joining node was unaware of a new
deployment of the item that occurred while it was offline.
false
Should the item represented by update
that is available
on a newly joining node be accepted for use around the cluster when the
cluster's records show an item with the same path with a different version?
Such a case potentially could mean the newly joining node was unaware of
changes that occurred while it was offline.
update
that is available
on a newly joining node be accepted for use around the cluster when the
cluster's records show an item with the same path with a different version?
Such a case potentially could mean the newly joining node was unaware of
changes that occurred while it was offline.
false
Should the item represented by toAdd
that is available
on a merging set of nodes be accepted for use around the cluster when the
cluster's records show no record of an item with the same path? Such a
case potentially could mean the merging nodes were unaware of an earlier
removal that occurred while the cluster was split and that the cluster
has also purged
from its records
.
toAdd
that is available
on a merging set of nodes be accepted for use around the cluster when the
cluster's records show no record of an item with the same path? Such a
case potentially could mean the merging nodes were unaware of an earlier
removal that occurred while the cluster was split and that the cluster
has also purged
from its records
.
false
Should the item represented by reincarnation
that is available
on a merging set of nodes be accepted for use around the cluster when the
cluster's records show an item with the same path was previously removed?
Such a case potentially could mean the merging nodes were unaware of a
removal that occurred while the cluster was split.
reincarnation
that is available
on a merging set of nodes be accepted for use around the cluster when the
cluster's records show an item with the same path was previously removed?
Such a case potentially could mean the merging nodes were unaware of a
removal that occurred while the cluster was split.
false
Should the item represented by toRemove
that is unavailable
on a newly joining node be removed from around the cluster when
the cluster's records show an item with the same path? Such a case
potentially could mean the newly joining node was unaware of a new
deployment of the item that occurred while the cluster was split.
toRemove
that is unavailable
on a newly joining node be removed from around the cluster when
the cluster's records show an item with the same path? Such a case
potentially could mean the newly joining node was unaware of a new
deployment of the item that occurred while the cluster was split.
false
Should the item represented by update
that is available
on a merging set of nodes be accepted for use around the cluster when the
cluster's records show an item with the same path with a different version?
Such a case potentially could mean the merging nodes were unaware of
changes that occurred while the cluster was split.
update
that is available
on a merging set of nodes be accepted for use around the cluster when the
cluster's records show an item with the same path with a different version?
Such a case potentially could mean the merging nodes were unaware of
changes that occurred while the cluster was split.
LocalContentManager
that works with the given collection of URIs.
SynchronizationReadAction
that reads from a InputStream
and besides returning ByteChunk
s, also writes the stream contents
to a local file.ProfileSourceMetaData
that indicates a clustered
repository should be used.prepared
.
RepositoryContentMetadata
.IllegalStateException
if not.
RepositoryContentMetadata
with a child
RepositoryRootMetadata
for each of this persister's URIs,
but no RepositoryItemMetadata
s under those roots.
SynchronizationActionContext
for the given cluster-wide
content synchronization.
AbstractSynchronizationPolicy.getRemovalTrackingTime()
, equal to 30 days.
SynchronizationActionContext
subclass that provides additional
contextual information useful to filesystem based actions.SynchronizationReadAction
that reads from a File
.LocalContentManager
that persists to the local filesystem.LocalContentManagerFactory
that creates a
FilesystemLocalContentManager
.SynchronizationWriteAction
that writes to a File
.AbstractSynchronizationPolicy.acceptJoinAddition(RepositoryItemMetadata, RepositoryItemMetadata)
.
AbstractSynchronizationPolicy.acceptJoinReincarnation(RepositoryItemMetadata, RepositoryItemMetadata)
.
AbstractSynchronizationPolicy.acceptJoinRemoval(RepositoryItemMetadata, RepositoryItemMetadata)
.
AbstractSynchronizationPolicy.acceptJoinUpdate(RepositoryItemMetadata, RepositoryItemMetadata)
.
AbstractSynchronizationPolicy.acceptMergeAddition(RepositoryItemMetadata)
.
AbstractSynchronizationPolicy.acceptMergeReincarnation(RepositoryItemMetadata, RepositoryItemMetadata)
.
AbstractSynchronizationPolicy.acceptMergeRemoval(RepositoryItemMetadata, RepositoryItemMetadata)
.
AbstractSynchronizationPolicy.acceptMergeUpdate(RepositoryItemMetadata, RepositoryItemMetadata)
.
VirtualFile
corresponding to the given URI.
key
.
ids
of the
metadata stored in this container.
RepositoryItemMetadata
that will describe an item that
may be added.
LocalContentManager
for the given set of URIs.
SynchronizationActionContext
.
VirtualFile
for the content indicated by item
.
ProfileSourceMetaData
that indicates a clustered
repository that supports hot deployment should be used.ClusteredDeploymentRepository
that will only accept content changes
pulled from the cluster at load
time;
pushing updates to the cluster at load is not support, nor are changes
after load supported.ProfileSourceMetaData
that indicates a clustered
repository that does not support content changes after
DeploymentRepository.load()
is called should be used.SynchronizationPolicy
that does not accept any changes.the list of repository roots
is inconsistent between two RepositoryContentMetadata
objects.SynchronizationAction
that does nothing normally, but restores
a removed directory during the rollback phase.LocalContentManager.getCurrentContentMetadata()
as the "official" content metadata.
SynchronizationAction.complete()
has been invoked.
SynchronizationAction.complete()
has been invoked.
true
to all acceptXXX calls.
ClusteredDeploymentRepository
.LocalContentManager
that understands a
particular type of URI.ContentModification
object from a comparison
of a current snapshot of local repository content to a official snapshot.SynchronizationAction
that makes a directory.SynchronizationWriteAction
that throws the bytes on the
floor.SynchronizationAction
that does nothing.RepositoryItemMetadata.setTimestampAsString(String)
that will
generate a timestamp equal to System.currentTimeMillis().
initialized
.
false
Request that the policy remove any RepositoryItemMetadata
objects
that are listed as removed
if the policy no longer wishes to consider them in its decision making.
RepositoryItemMetadata
objects
that are listed as removed
if the policy no longer wishes to consider them in its decision making.
ContentModification
objects from a comparison
of a current snapshot of a remote node's repository content to the official
snapshot available on this node.SynchronizationRemoteAction
that updates the local metadata
recording the removal.SynchronizationAction
that modifies the node's metadata to insert
a missing RepositoryItemMetadata
that tracks a removed item.SynchronizationAction
that removes a File
.AbstractSynchronizationPolicy.acceptJoinAddition(RepositoryItemMetadata, RepositoryItemMetadata)
.
AbstractSynchronizationPolicy.acceptJoinReincarnation(RepositoryItemMetadata, RepositoryItemMetadata)
.
AbstractSynchronizationPolicy.acceptJoinRemoval(RepositoryItemMetadata, RepositoryItemMetadata)
.
AbstractSynchronizationPolicy.acceptJoinUpdate(RepositoryItemMetadata, RepositoryItemMetadata)
.
AbstractSynchronizationPolicy.acceptMergeAddition(RepositoryItemMetadata)
.
AbstractSynchronizationPolicy.acceptMergeReincarnation(RepositoryItemMetadata, RepositoryItemMetadata)
.
AbstractSynchronizationPolicy.acceptMergeRemoval(RepositoryItemMetadata, RepositoryItemMetadata)
.
AbstractSynchronizationPolicy.acceptMergeUpdate(RepositoryItemMetadata, RepositoryItemMetadata)
.
true
to all acceptXXX calls.
SynchronizationRemoteAction
.SynchronizationAction
can use.SynchronizationAction
that initiates a
process that subsequent actions will drive to comletion.SynchronizationAction
that a
node should handle by telling the other nodes in the cluster to execute the
modification
.SynchronizationAction
used by an
implementation of LocalContentManager
, allowing the content manager
to take the action through a two phase commit process.RepositoryClusteringHandler.lockGlobally()
.
RepositoryClusteringHandler.lockLocally()
.
|
||||||||||
PREV NEXT | FRAMES NO FRAMES |