When do we need decorator pattern?
When is it necessary to use the decorator pattern? If possible, give me a real world example that is well-suited for the pattern.
Answer
The Streams in Java - subclasses of InputStream and OutputStream are perfect examples of the decorator pattern.
As an example, writing a file to disk:
File toWriteTo = new File("C:\\temp\\tempFile.txt");
OutputStream outputStream = new FileOutputStream(toWriteTo);
outputStream.write("Sample text".getBytes());
Then should you require some extra functionality regarding the writing to disk:
File toWriteTo = new File("C:\\temp\\tempFile.txt");
OutputStream outputStream =
new GZIPOutputStream(new FileOutputStream(toWriteTo));
outputStream.write("Sample text".getBytes());
By simply "chaining" the constructors, you can create quite powerful ways of writing to disk. The beauty in this way is that you can add different (in this example) OutputStream implementations later on. Also, each implementation doesn't know how the others work - they all just work to the same contract. This also makes testing each implementation very easy in isolation.
There are plenty of "real world" examples of where the decorator pattern can be used. Off the top of my head, some examples:
- Reading and writing to disk (above)
- Construction of UI elements, such as adding scrollbars on to text areas etc
Head First Design Patterns has some more "real world" examples. It seems that O'Reilly has their sample chapter, which is on Decorator Pattern, for free; Google showed up this link: PDF