Remote Systems
v6.4.1

com.ibm.etools.systems.core
Class SystemStringTokenizer

java.lang.Object
  extended bycom.ibm.etools.systems.core.SystemStringTokenizer

public class SystemStringTokenizer
extends Object

Similar to java's StringTokenizer, but supports multi-character delimiter versus just single character delimiters. Eg usage is: SystemStringTokenizer tokens = new SystemStringTokenizer(stringToParse, "___"); while (tokens.hasMoreTokens()) String nextToken = tokens.nextToken();


Field Summary
static String copyright
           
 
Constructor Summary
SystemStringTokenizer(String inputString, String delimiter)
          Constructor
 
Method Summary
 int countTokens()
          Return a count of the number of tokens in the input string
 boolean hasMoreTokens()
          Return true if there are more tokens
 String nextToken()
          Return the next token
static Vector tokenize(String inputString, String delimiter)
          Parse a string into tokens.
 
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

SystemStringTokenizer

public SystemStringTokenizer(String inputString,
                             String delimiter)
Constructor

Parameters:
inputString - The string to be tokenized
delimiter - The multi-char string that delimits the tokens. Eg "___"
Method Detail

countTokens

public int countTokens()
Return a count of the number of tokens in the input string


hasMoreTokens

public boolean hasMoreTokens()
Return true if there are more tokens


nextToken

public String nextToken()
Return the next token


tokenize

public static Vector tokenize(String inputString,
                              String delimiter)
Parse a string into tokens.


Remote Systems
v6.4.1

Copyright © 2005 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.