From 516b127d217cfe5eff4cf0aea0d6edc843b6cd83 Mon Sep 17 00:00:00 2001 From: Ilkka Seppala Date: Sat, 3 Oct 2015 21:11:19 +0300 Subject: [PATCH] Improved Facade Javadoc --- facade/src/main/java/com/iluwatar/facade/App.java | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/facade/src/main/java/com/iluwatar/facade/App.java b/facade/src/main/java/com/iluwatar/facade/App.java index 0d8eccd4b..37cda0281 100644 --- a/facade/src/main/java/com/iluwatar/facade/App.java +++ b/facade/src/main/java/com/iluwatar/facade/App.java @@ -2,9 +2,15 @@ package com.iluwatar.facade; /** * - * Facade ({@link DwarvenGoldmineFacade}) provides simpler interface to subsystem. + * The Facade design pattern is often used when a system is very complex or difficult + * to understand because the system has a large number of interdependent classes or + * its source code is unavailable. This pattern hides the complexities of the larger + * system and provides a simpler interface to the client. It typically involves a single + * wrapper class which contains a set of members required by client. These members access + * the system on behalf of the facade client and hide the implementation details. *

- * http://en.wikipedia.org/wiki/Facade_pattern + * In this example the Facade is ({@link DwarvenGoldmineFacade}) and it provides a simpler + * interface to the goldmine subsystem. * */ public class App {