This documentation differs from the official API.
Jadeite adds
extra features to the API including:
variable font sizes,
constructions examples,
placeholders for classes and methods, and auto-generated “See Also” links.
Additionally it
is missing some items found in standard Javadoc documentation, including:
generics type information,
“Deprecated” tags and comments,
“See Also” links,
along with other minor differences.
Please send any questions or feedback to
bam@cs.cmu.edu.
javax.mail.search
class AddressStringTerm
- All Implemented Interfaces:
- Serializable
- Direct Known Subclasses:
- FromStringTerm, RecipientStringTerm
public abstract class AddressStringTerm
extends StringTerm
This abstract class implements string comparisons for Message
addresses.
Note that this class differs from the AddressTerm
class
in that this class does comparisons on address strings rather than
Address objects.
Constructor Summary |
protected |
Constructor.
|
Method Summary |
boolean |
Equality comparison.
|
protected boolean |
Check whether the address pattern specified in the constructor is
a substring of the string representation of the given Address
object.
|
AddressStringTerm
protected AddressStringTerm(String pattern)
-
Constructor.
- Parameters:
pattern
- the address pattern to be compared.
equals
public boolean equals(Object obj)
-
Equality comparison.
- Overrides:
equals
in class StringTerm
- Parameters:
obj
match
protected boolean match(Address a)
-
Check whether the address pattern specified in the constructor is
a substring of the string representation of the given Address
object.
Note that if the string representation of the given Address object
contains charset or transfer encodings, the encodings must be
accounted for, during the match process.
- Parameters:
a
- The comparison is applied to this Address object.
- Returns:
- true if the match succeeds, otherwise false.
This documentation differs from the official API.
Jadeite adds
extra features to the API including:
variable font sizes,
constructions examples,
placeholders for classes and methods, and auto-generated “See Also” links.
Additionally it
is missing some items found in standard Javadoc documentation, including:
generics type information,
“Deprecated” tags and comments,
“See Also” links,
along with other minor differences.
Please send any questions or feedback to
bam@cs.cmu.edu.