Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.services.ifs.files
Class IFSFileSystemFilter

java.lang.Object
  extended by com.ibm.etools.iseries.services.ifs.files.UniversalFileSystemFilter
      extended by com.ibm.etools.iseries.services.ifs.files.IFSFileSystemFilter
All Implemented Interfaces:
FilenameFilter

public class IFSFileSystemFilter
extends UniversalFileSystemFilter


Field Summary
static String Copyright
           
 
Fields inherited from class com.ibm.etools.iseries.services.ifs.files.UniversalFileSystemFilter
allowDirs, allowFiles, caseSensitive, filter, folderNameMatcher, includeFilesOrFolders, matcher
 
Constructor Summary
IFSFileSystemFilter(String str, boolean files, boolean folders)
           
 
Method Summary
 boolean accept(IFSFile file)
          Method required by IFSFileFilter interface, used by IFSFile.list() Tests if a specified file should be included in a file list.
 
Methods inherited from class com.ibm.etools.iseries.services.ifs.files.UniversalFileSystemFilter
accept, setListValues, setListValues
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Field Detail

Copyright

public static final String Copyright
See Also:
Constant Field Values
Constructor Detail

IFSFileSystemFilter

public IFSFileSystemFilter(String str,
                           boolean files,
                           boolean folders)
Method Detail

accept

public boolean accept(IFSFile file)
Method required by IFSFileFilter interface, used by IFSFile.list() Tests if a specified file should be included in a file list.

Parameters:
file - IFSFile object
Returns:
true if and only if the name should be included in the file list; false otherwise.

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.