Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.rse.ui.resources
Class QSYSDownloadConflict

java.lang.Object
  extended by java.lang.Throwable
      extended by java.lang.Exception
          extended by com.ibm.etools.iseries.rse.ui.resources.QSYSDownloadConflict
All Implemented Interfaces:
Serializable

public class QSYSDownloadConflict
extends Exception

See Also:
Serialized Form

Field Summary
static String copyright
           
 
Constructor Summary
QSYSDownloadConflict(IFile local, IQSYSMember remote, long remoteModifiedStamp, boolean remoteNewer)
          Constructor
 
Method Summary
 IFile getLocalFile()
           
 IQSYSMember getRemoteMember()
           
 long getRemoteModifiedTimestamp()
           
 boolean isRemoteNewer()
           
 
Methods inherited from class java.lang.Throwable
fillInStackTrace, getCause, getLocalizedMessage, getMessage, getStackTrace, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
 

Field Detail

copyright

public static String copyright
Constructor Detail

QSYSDownloadConflict

public QSYSDownloadConflict(IFile local,
                            IQSYSMember remote,
                            long remoteModifiedStamp,
                            boolean remoteNewer)
Constructor

Method Detail

getLocalFile

public IFile getLocalFile()

getRemoteMember

public IQSYSMember getRemoteMember()

isRemoteNewer

public boolean isRemoteNewer()

getRemoteModifiedTimestamp

public long getRemoteModifiedTimestamp()

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.