Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.comm.filters
Class ISeriesFilterStringTokenizer

java.lang.Object
  extended by com.ibm.etools.iseries.comm.filters.ISeriesFilterStringTokenizer

public class ISeriesFilterStringTokenizer
extends Object

A tokenizer (like ISeriesStringTokenizer) which would parse quoted values as one token, but would also break up brackets eg. () as individual tokens. (Which ISeriesStringTokenizer wasn't doing)


Field Summary
static String Copyright
           
 
Constructor Summary
ISeriesFilterStringTokenizer(String s)
           
 
Method Summary
 String getParameterValue_UpperCase()
          For a parameter value which is not a quoted value, uppercase it.
 String getParameterValue()
          Common routine to return a parameter value from inside brackets
 String nextToken()
           
static String upperCase_UnquotedValue(String value)
          For a value which is not a quoted value, uppercase it.
 
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

ISeriesFilterStringTokenizer

public ISeriesFilterStringTokenizer(String s)
Method Detail

nextToken

public String nextToken()

upperCase_UnquotedValue

public static String upperCase_UnquotedValue(String value)
For a value which is not a quoted value, uppercase it.

Returns:

getParameterValue_UpperCase

public String getParameterValue_UpperCase()
For a parameter value which is not a quoted value, uppercase it.

Returns:

getParameterValue

public String getParameterValue()
Common routine to return a parameter value from inside brackets

Returns:

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.