Rational Developer for Power Systems Software

Class IFSCacheHandler

  extended by com.ibm.etools.iseries.subsystems.qsys.cache.AbstractCacheHandler
      extended by com.ibm.etools.iseries.subsystems.ifs.cache.IFSCacheHandler

public class IFSCacheHandler
extends AbstractCacheHandler

Cache handler for IFS files subsystem. Currently only caching for the current directory is supported (as it's required by the program verifiers).

Field Summary
static String copyright
Method Summary
static IFSCacheHandler getInstance(IFSFileServiceSubSystem subsystem)
          Singleton access method.
 String loadCurrentDirectory()
          Load the current directory from cache
 void saveCurrentDirectory(String currentDirectory)
          Save the current directory to the cache
static void updateCacheLocation(String newLocation)
          Updates the cache location of every handler
Methods inherited from class com.ibm.etools.iseries.subsystems.qsys.cache.AbstractCacheHandler
addToOutputXNumberOfLines, backupAndDeleteCacheFile, checkCacheSize, getCacheRootDirectory, getListingDetailsFileName, getReader, getWriter, isCachingDisabled, setCacheLocation, skipNumberOfLines, writeFile
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Detail


public static String copyright
Method Detail


public static IFSCacheHandler getInstance(IFSFileServiceSubSystem subsystem)
Singleton access method.


public static void updateCacheLocation(String newLocation)
Updates the cache location of every handler

newLocation - The new location the cache should cache files to now


public String loadCurrentDirectory()
Load the current directory from cache


public void saveCurrentDirectory(String currentDirectory)
Save the current directory to the cache

Rational Developer for Power Systems Software

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.