Uses of Class
org.jboss.system.server.profileservice.repository.clustered.metadata.RepositoryItemMetadata

Packages that use RepositoryItemMetadata
org.jboss.system.server.profileservice.repository.clustered   
org.jboss.system.server.profileservice.repository.clustered.local   
org.jboss.system.server.profileservice.repository.clustered.local.file   
org.jboss.system.server.profileservice.repository.clustered.metadata   
org.jboss.system.server.profileservice.repository.clustered.sync   
 

Uses of RepositoryItemMetadata in org.jboss.system.server.profileservice.repository.clustered
 

Methods in org.jboss.system.server.profileservice.repository.clustered that return RepositoryItemMetadata
 RepositoryItemMetadata RepositoryClusteringHandler.addDeploymentContent(String vfsPath, InputStream contentIS)
          Read the content from the given input stream and add it to the repository across the cluster.
 

Uses of RepositoryItemMetadata in org.jboss.system.server.profileservice.repository.clustered.local
 

Methods in org.jboss.system.server.profileservice.repository.clustered.local that return RepositoryItemMetadata
 RepositoryItemMetadata AbstractLocalContentManager.getItemForAddition(String vfsPath)
           
 RepositoryItemMetadata LocalContentManager.getItemForAddition(String vfsPath)
          Gets a RepositoryItemMetadata that will describe an item that may be added.
 

Methods in org.jboss.system.server.profileservice.repository.clustered.local with parameters of type RepositoryItemMetadata
 RepositoryContentMetadata AbstractLocalContentManager.getContentMetadataForAdd(RepositoryItemMetadata toAdd, InputStream contentIS)
           
 RepositoryContentMetadata LocalContentManager.getContentMetadataForAdd(RepositoryItemMetadata toAdd, InputStream contentIS)
          Generate content metadata that would reflect what the metadata would look like if an item with path vfsPath were added.
 org.jboss.virtual.VirtualFile AbstractLocalContentManager.getVirtualFileForItem(RepositoryItemMetadata item)
           
 org.jboss.virtual.VirtualFile LocalContentManager.getVirtualFileForItem(RepositoryItemMetadata item)
          Get a VirtualFile for the content indicated by item.
 

Uses of RepositoryItemMetadata in org.jboss.system.server.profileservice.repository.clustered.local.file
 

Methods in org.jboss.system.server.profileservice.repository.clustered.local.file with parameters of type RepositoryItemMetadata
static File FileUtil.getFileForItem(URI rootURI, RepositoryItemMetadata item)
           
 

Uses of RepositoryItemMetadata in org.jboss.system.server.profileservice.repository.clustered.metadata
 

Methods in org.jboss.system.server.profileservice.repository.clustered.metadata that return RepositoryItemMetadata
 RepositoryItemMetadata RepositoryRootMetadata.getItemMetadata(List<String> path)
           
 

Methods in org.jboss.system.server.profileservice.repository.clustered.metadata that return types with arguments of type RepositoryItemMetadata
 Collection<RepositoryItemMetadata> RepositoryRootMetadata.getContent()
           
 

Methods in org.jboss.system.server.profileservice.repository.clustered.metadata with parameters of type RepositoryItemMetadata
 void RepositoryRootMetadata.addItemMetadata(RepositoryItemMetadata md)
           
 int RepositoryItemMetadata.compareTo(RepositoryItemMetadata o)
           
 boolean RepositoryItemMetadata.isChildOf(RepositoryItemMetadata other)
          Gets whether this item is a child of another item.
 

Method parameters in org.jboss.system.server.profileservice.repository.clustered.metadata with type arguments of type RepositoryItemMetadata
 void RepositoryRootMetadata.setContent(Collection<RepositoryItemMetadata> content)
           
 

Constructors in org.jboss.system.server.profileservice.repository.clustered.metadata with parameters of type RepositoryItemMetadata
RepositoryItemMetadata(RepositoryItemMetadata toCopy)
          Copy constructor.
 

Uses of RepositoryItemMetadata in org.jboss.system.server.profileservice.repository.clustered.sync
 

Methods in org.jboss.system.server.profileservice.repository.clustered.sync that return RepositoryItemMetadata
 RepositoryItemMetadata ContentModification.getItem()
           
protected static RepositoryItemMetadata AbstractSynchronizationAction.getMarkedRemovedItem(ContentModification base)
           
protected static RepositoryItemMetadata AbstractContentModificationGenerator.getMarkedRemovedItem(RepositoryItemMetadata base)
           
 RepositoryItemMetadata AbstractContentModificationGenerator.GeneratedModifications.getPreapprovedAddParent()
           
 RepositoryItemMetadata AbstractContentModificationGenerator.GeneratedModifications.getPrerejectedRemoveParent()
           
 

Methods in org.jboss.system.server.profileservice.repository.clustered.sync with parameters of type RepositoryItemMetadata
protected abstract  boolean AbstractSynchronizationPolicy.acceptAddition(RepositoryItemMetadata toAdd, RepositoryItemMetadata joinersPrevious, boolean merge)
           
 boolean SynchronizationPolicy.acceptJoinAddition(RepositoryItemMetadata toAdd, RepositoryItemMetadata joinersPrevious)
          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 ImmutableSynchronizationPolicy.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 AbstractSynchronizationPolicy.acceptJoinAddition(RepositoryItemMetadata toAdd, RepositoryItemMetadata joinersPrevious)
           
 boolean SynchronizationPolicy.acceptJoinReincarnation(RepositoryItemMetadata reincarnation, RepositoryItemMetadata current)
          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 ImmutableSynchronizationPolicy.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 AbstractSynchronizationPolicy.acceptJoinReincarnation(RepositoryItemMetadata reincarnation, RepositoryItemMetadata current)
           
 boolean SynchronizationPolicy.acceptJoinRemoval(RepositoryItemMetadata current, RepositoryItemMetadata joinersItem)
          Should the item represented by toRemovethat 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 ImmutableSynchronizationPolicy.acceptJoinRemoval(RepositoryItemMetadata current, RepositoryItemMetadata joinersItem)
          Always returns false Should the item represented by toRemovethat 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 AbstractSynchronizationPolicy.acceptJoinRemoval(RepositoryItemMetadata current, RepositoryItemMetadata joinersItem)
           
 boolean SynchronizationPolicy.acceptJoinUpdate(RepositoryItemMetadata update, RepositoryItemMetadata current)
          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 ImmutableSynchronizationPolicy.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 AbstractSynchronizationPolicy.acceptJoinUpdate(RepositoryItemMetadata update, RepositoryItemMetadata current)
           
 boolean SynchronizationPolicy.acceptMergeAddition(RepositoryItemMetadata toAdd)
          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 ImmutableSynchronizationPolicy.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 AbstractSynchronizationPolicy.acceptMergeAddition(RepositoryItemMetadata toAdd)
           
 boolean SynchronizationPolicy.acceptMergeReincarnation(RepositoryItemMetadata reincarnation, RepositoryItemMetadata current)
          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 ImmutableSynchronizationPolicy.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 AbstractSynchronizationPolicy.acceptMergeReincarnation(RepositoryItemMetadata reincarnation, RepositoryItemMetadata current)
           
 boolean SynchronizationPolicy.acceptMergeRemoval(RepositoryItemMetadata current, RepositoryItemMetadata mergersView)
          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 ImmutableSynchronizationPolicy.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 AbstractSynchronizationPolicy.acceptMergeRemoval(RepositoryItemMetadata current, RepositoryItemMetadata mergersView)
           
 boolean SynchronizationPolicy.acceptMergeUpdate(RepositoryItemMetadata update, RepositoryItemMetadata current)
          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 ImmutableSynchronizationPolicy.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 AbstractSynchronizationPolicy.acceptMergeUpdate(RepositoryItemMetadata update, RepositoryItemMetadata current)
           
protected abstract  boolean AbstractSynchronizationPolicy.acceptReincarnation(RepositoryItemMetadata reincarnation, RepositoryItemMetadata current, boolean merge)
           
protected abstract  boolean AbstractSynchronizationPolicy.acceptRemoval(RepositoryItemMetadata current, RepositoryItemMetadata sendersView, boolean merge)
           
protected abstract  boolean AbstractSynchronizationPolicy.acceptUpdate(RepositoryItemMetadata update, RepositoryItemMetadata current, boolean merge)
           
protected static RepositoryItemMetadata AbstractContentModificationGenerator.getMarkedRemovedItem(RepositoryItemMetadata base)
           
protected abstract  void AbstractContentModificationGenerator.handleAddition(String rootName, RepositoryItemMetadata item, AbstractContentModificationGenerator.GeneratedModifications mods)
           
protected  void LocalContentModificationGenerator.handleAddition(String rootName, RepositoryItemMetadata item, AbstractContentModificationGenerator.GeneratedModifications mods)
           
protected  void RemoteContentModificationGenerator.handleAddition(String rootName, RepositoryItemMetadata item, AbstractContentModificationGenerator.GeneratedModifications mods)
           
protected abstract  void AbstractContentModificationGenerator.handleAddition(String rootName, RepositoryItemMetadata modified, RepositoryItemMetadata base, AbstractContentModificationGenerator.GeneratedModifications mods)
           
protected  void LocalContentModificationGenerator.handleAddition(String rootName, RepositoryItemMetadata modified, RepositoryItemMetadata base, AbstractContentModificationGenerator.GeneratedModifications mods)
           
protected  void RemoteContentModificationGenerator.handleAddition(String rootName, RepositoryItemMetadata item, RepositoryItemMetadata removedVersion, AbstractContentModificationGenerator.GeneratedModifications mods)
           
protected abstract  void AbstractContentModificationGenerator.handleChangeFromDirectory(String rootName, RepositoryItemMetadata base, RepositoryItemMetadata modified, AbstractContentModificationGenerator.GeneratedModifications mods)
           
protected  void LocalContentModificationGenerator.handleChangeFromDirectory(String rootName, RepositoryItemMetadata base, RepositoryItemMetadata modified, AbstractContentModificationGenerator.GeneratedModifications mods)
           
protected  void RemoteContentModificationGenerator.handleChangeFromDirectory(String rootName, RepositoryItemMetadata base, RepositoryItemMetadata modified, AbstractContentModificationGenerator.GeneratedModifications mods)
           
protected abstract  void AbstractContentModificationGenerator.handleChangeToDirectory(String rootName, RepositoryItemMetadata base, RepositoryItemMetadata modified, AbstractContentModificationGenerator.GeneratedModifications mods)
           
protected  void LocalContentModificationGenerator.handleChangeToDirectory(String rootName, RepositoryItemMetadata base, RepositoryItemMetadata modified, AbstractContentModificationGenerator.GeneratedModifications mods)
           
protected  void RemoteContentModificationGenerator.handleChangeToDirectory(String rootName, RepositoryItemMetadata base, RepositoryItemMetadata modified, AbstractContentModificationGenerator.GeneratedModifications mods)
           
protected abstract  void AbstractContentModificationGenerator.handleDirectoryTimestampModification(String rootName, RepositoryItemMetadata base, RepositoryItemMetadata modified, AbstractContentModificationGenerator.GeneratedModifications mods)
           
protected  void LocalContentModificationGenerator.handleDirectoryTimestampModification(String rootName, RepositoryItemMetadata base, RepositoryItemMetadata modified, AbstractContentModificationGenerator.GeneratedModifications mods)
           
protected  void RemoteContentModificationGenerator.handleDirectoryTimestampModification(String rootName, RepositoryItemMetadata base, RepositoryItemMetadata modified, AbstractContentModificationGenerator.GeneratedModifications mods)
           
protected  void AbstractContentModificationGenerator.handleMatch(String rootName, RepositoryItemMetadata base, RepositoryItemMetadata modified, AbstractContentModificationGenerator.GeneratedModifications mods)
           
protected abstract  void AbstractContentModificationGenerator.handleMissing(String rootName, RepositoryItemMetadata item, AbstractContentModificationGenerator.GeneratedModifications mods)
           
protected  void LocalContentModificationGenerator.handleMissing(String rootName, RepositoryItemMetadata item, AbstractContentModificationGenerator.GeneratedModifications mods)
           
protected  void RemoteContentModificationGenerator.handleMissing(String rootName, RepositoryItemMetadata item, AbstractContentModificationGenerator.GeneratedModifications mods)
           
protected abstract  void AbstractContentModificationGenerator.handleRemoval(String rootName, RepositoryItemMetadata base, AbstractContentModificationGenerator.GeneratedModifications mods)
           
protected  void LocalContentModificationGenerator.handleRemoval(String rootName, RepositoryItemMetadata item, AbstractContentModificationGenerator.GeneratedModifications mods)
           
protected  void RemoteContentModificationGenerator.handleRemoval(String rootName, RepositoryItemMetadata item, AbstractContentModificationGenerator.GeneratedModifications mods)
           
protected abstract  void AbstractContentModificationGenerator.handleSimpleModification(String rootName, RepositoryItemMetadata base, RepositoryItemMetadata modified, AbstractContentModificationGenerator.GeneratedModifications mods)
           
protected  void LocalContentModificationGenerator.handleSimpleModification(String rootName, RepositoryItemMetadata base, RepositoryItemMetadata modified, AbstractContentModificationGenerator.GeneratedModifications mods)
           
protected  void RemoteContentModificationGenerator.handleSimpleModification(String rootName, RepositoryItemMetadata base, RepositoryItemMetadata modified, AbstractContentModificationGenerator.GeneratedModifications mods)
           
 void AbstractContentModificationGenerator.GeneratedModifications.setPreapprovedAddParent(RepositoryItemMetadata preapprovedAddParent)
           
 void AbstractContentModificationGenerator.GeneratedModifications.setPrerejectedRemoveParent(RepositoryItemMetadata prerejectedRemoveParent)
           
 

Constructors in org.jboss.system.server.profileservice.repository.clustered.sync with parameters of type RepositoryItemMetadata
AbstractContentModificationGenerator.GeneratedModifications(RepositoryItemMetadata preapprovedAddParent, Stack<ContentModification> preapprovedRemoveParent, Stack<ContentModification> prerejectedAddParent, RepositoryItemMetadata prerejectedRemoveParent)
           
ContentModification(ContentModification.Type type, String rootName, RepositoryItemMetadata item)
           
 



Copyright © 2009 JBoss, a division of Red Hat, Inc.. All Rights Reserved.