From 807478ab3da057f98a5b51f5f7dab5d2c8b2b7cf Mon Sep 17 00:00:00 2001 From: Ilkka Seppala Date: Sat, 3 Oct 2015 20:27:28 +0300 Subject: [PATCH] Improve Composite Javadoc --- .../src/main/java/com/iluwatar/composite/App.java | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/composite/src/main/java/com/iluwatar/composite/App.java b/composite/src/main/java/com/iluwatar/composite/App.java index 7dfd15443..7bd0e4d01 100644 --- a/composite/src/main/java/com/iluwatar/composite/App.java +++ b/composite/src/main/java/com/iluwatar/composite/App.java @@ -1,10 +1,14 @@ package com.iluwatar.composite; /** - * - * With Composite we can treat tree hierarchies of objects with uniform - * interface ({@link LetterComposite}). In this example we have sentences composed of - * words composed of letters. + * The Composite pattern is a partitioning design pattern. The Composite pattern + * describes that a group of objects is to be treated in the same way as a single + * instance of an object. The intent of a composite is to "compose" objects into + * tree structures to represent part-whole hierarchies. Implementing the Composite + * pattern lets clients treat individual objects and compositions uniformly. + *

+ * In this example we have sentences composed of words composed of letters. All of + * the objects can be treated through the same interface ({@link LetterComposite}). * */ public class App {