- All Superinterfaces:
- Serializable
- All Known Subinterfaces:
- ByteToCharTransformer, ByteTransformer, CharTransformer, ConfigurableTransformer
- All Known Implementing Classes:
- AbstractCommandStringTransformer, Asciifier, Base64, BufferedReaderTransformer, ByteArrayToCharTransformer, ByteCharTransformer, Censor, ChainedCharTransformer, ChecksumFactory.ChecksumTransformer, ChunkedTransformer, CodeSampleFactory.CodeSample, ConfigurableReaderTransformer, ConfigurableStringTransformer, CopyCharTransformer, CP1252Surrogator, DiacriticsRemover, EncryptionTransformerFactory.Decryption, EncryptionTransformerFactory.Encryption, Figlet, Graphviz, Hex, Identifier, InputStreamTransformer, InverseCharTransformer, Javascript, Latin3Surrogator, LinkFinder, LoggerCharTransformer, LowerCaser, MD5, ParagraphTransformerFactory.ParagraphTransformer, Perl, ProcessorCharTransformer, RadixTransformer, ReaderTransformer, RegexpReplacer, ResourceBundleReplacer, RomanTransformer, Rot13, Rot5, Sitestat, Smilies, SpaceReducer, SpaceRemover, SpaceSwallower, Sql, StringTransformer, SubstringFactory.Substring, Swallower, TabToSpacesTransformer, Trimmer, UnicodeEscaper, UpperCaser, Url, UrlEscaper, Xml, XmlEntities, XmlField, XmlField, XsltTransformer, YUICSSCompressor, YUIJavaScriptCompressor
public interface Transformer
extends Serializable
Interface for transformations. Actually, since there are so many
types of transformers (byte/byte, char/char, char/byte), nothing
can be pointed out to be typical for Transformers. This interface
ended up a bit emptier than I anticipated.
A Transformer must be serializable, because it is exposed through bridge (as 'processors').
- Author:
- Michiel Meeuwissen