Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.remotebuild
Class RBMarking

java.lang.Object
  extended by com.ibm.etools.iseries.remotebuild.RBMarking

public class RBMarking
extends Object

An RBMarking specifies the operations that are to attempted or the successful operations that have been completed on a RBResourceDelta during the synchronization process.


Field Summary
 boolean pushContents
           
 boolean pushCreate
           
 boolean pushDelete
           
 boolean pushProperties
           
 boolean pushSourceType
           
 boolean pushVerify
           
 
Constructor Summary
RBMarking()
           
 
Method Summary
 void add(RBMarking marking)
          Combines a marking with this one by or'ing the settings of the markings.
 RBMarking copy()
           
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Field Detail

pushDelete

public boolean pushDelete

pushCreate

public boolean pushCreate

pushVerify

public boolean pushVerify

pushSourceType

public boolean pushSourceType

pushContents

public boolean pushContents

pushProperties

public boolean pushProperties
Constructor Detail

RBMarking

public RBMarking()
Method Detail

copy

public RBMarking copy()
Returns:
a new marking that is a copy of the previous marking. This is typically used to ensure that all deltas have markings that are unique instances instead of accidentally shared.

add

public void add(RBMarking marking)
Combines a marking with this one by or'ing the settings of the markings. Thus, if this marking has a pushDelete mark clear, and the parameter marking has that mark set, after the operation the pushDelete mark will be set.

Parameters:
marking - the marking that will be "or"ed with the current marking.

Rational Developer for Power Systems Software
V7.6

Copyright 2011 IBM Corp. All Rights Reserved.

Note: This documentation is for part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.