|
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Objectorg.jboss.system.server.profileservice.repository.clustered.sync.ImmutableSynchronizationPolicy
public class ImmutableSynchronizationPolicy
SynchronizationPolicy
that does not accept any changes.
Constructor Summary | |
---|---|
ImmutableSynchronizationPolicy()
|
Method Summary | |
---|---|
boolean |
acceptJoinAddition(RepositoryItemMetadata toAdd,
RepositoryItemMetadata joinersPrevious)
Always returns 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 . |
boolean |
acceptJoinReincarnation(RepositoryItemMetadata reincarnation,
RepositoryItemMetadata current)
Always returns 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. |
boolean |
acceptJoinRemoval(RepositoryItemMetadata current,
RepositoryItemMetadata joinersItem)
Always returns 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. |
boolean |
acceptJoinUpdate(RepositoryItemMetadata update,
RepositoryItemMetadata current)
Always returns 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. |
boolean |
acceptMergeAddition(RepositoryItemMetadata toAdd)
Always returns 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 . |
boolean |
acceptMergeReincarnation(RepositoryItemMetadata reincarnation,
RepositoryItemMetadata current)
Always returns 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. |
boolean |
acceptMergeRemoval(RepositoryItemMetadata current,
RepositoryItemMetadata mergersView)
Always returns 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. |
boolean |
acceptMergeUpdate(RepositoryItemMetadata update,
RepositoryItemMetadata current)
Always returns 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. |
boolean |
purgeRemovedItems(RepositoryContentMetadata content)
Always returns 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. |
Methods inherited from class java.lang.Object |
---|
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
Constructor Detail |
---|
public ImmutableSynchronizationPolicy()
Method Detail |
---|
public boolean acceptJoinAddition(RepositoryItemMetadata toAdd, RepositoryItemMetadata joinersPrevious)
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
.
acceptJoinAddition
in interface SynchronizationPolicy
toAdd
- the item to addjoinersPrevious
- information, if available, on the timestamp of the
item that was present on the joining node when
it stopped. May be null
, indicating
the joining node was unaware of the item when stopped.
false
public boolean acceptJoinReincarnation(RepositoryItemMetadata reincarnation, RepositoryItemMetadata current)
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.
acceptJoinReincarnation
in interface SynchronizationPolicy
reincarnation
- the new version of the itemcurrent
- the cluster's current version of the item, showing when
it was removed and by whom. The "when" should reflect this
node's time of removal, not the time on the node that originated
the removal.
false
public boolean acceptJoinRemoval(RepositoryItemMetadata current, RepositoryItemMetadata joinersItem)
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.
acceptJoinRemoval
in interface SynchronizationPolicy
current
- the cluster's current version of the itemjoinersItem
- the joining node's view of item to remove. May be null,
indicating the sender is unaware of the item. If not null,
the timestamp of this item should reflect when the item
was removed, if known. If the time the item was removed is
not known, the timestamp should reflect the last known
timestamp of the item that was removed.
false
public boolean acceptJoinUpdate(RepositoryItemMetadata update, RepositoryItemMetadata current)
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.
acceptJoinUpdate
in interface SynchronizationPolicy
update
- the new version of the itemcurrent
- the cluster's current version of the item
false
public boolean acceptMergeAddition(RepositoryItemMetadata toAdd)
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
.
acceptMergeAddition
in interface SynchronizationPolicy
toAdd
- the item to add
false
public boolean acceptMergeReincarnation(RepositoryItemMetadata reincarnation, RepositoryItemMetadata current)
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.
acceptMergeReincarnation
in interface SynchronizationPolicy
reincarnation
- the new version of the itemcurrent
- the cluster's current version of the item, showing when
it was removed and by whom
false
public boolean acceptMergeRemoval(RepositoryItemMetadata current, RepositoryItemMetadata mergersView)
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.
acceptMergeRemoval
in interface SynchronizationPolicy
current
- the cluster's current version of the itemmergersView
- the merging node's view of item to remove. May be null,
indicating the sender is unaware of the item. If not null,
the timestamp of this item should reflect when the item
was removed, if known. If the time the item was removed is
not known, the timestamp should reflect the last known
timestamp of the item that was removed.
false
public boolean acceptMergeUpdate(RepositoryItemMetadata update, RepositoryItemMetadata current)
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.
acceptMergeUpdate
in interface SynchronizationPolicy
update
- the new version of the itemcurrent
- the cluster's current version of the item
false
public boolean purgeRemovedItems(RepositoryContentMetadata content)
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.
Used to prevent perpetual growth in the size of the RepositoryContentMetadata
by eventually purging records of removed items.
purgeRemovedItems
in interface SynchronizationPolicy
content
- the content. Cannot be null
.
false
|
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |