With the introduction of the CharSequence interface,the String class is no longer the lowest-common-denominatorfor character data, and yet String argumentsare still a pervasive requirement throughout the API.

All API methods currently specifying String argumentsshould be relaxed to CharSequence arguments unlessthey require immutability, equals(), hashCode(),or other String-specific behavior.

This change would not affect any existing code.

Here are a few candidate methodsfound by simply searching the API for the string,err, I mean the CharSequence ;-)
---> "(String"

StringTokenizer.nextToken(String delim)

[ other methods in java.lang, javax.swing, etc removed from this list ]