From cdd586ec7cc3e7d83bcec61235ce7e010d3115ff Mon Sep 17 00:00:00 2001 From: Ilkka Seppala Date: Sat, 3 Oct 2015 12:40:24 +0300 Subject: [PATCH] Improve Bridge Javadoc --- bridge/src/main/java/com/iluwatar/bridge/App.java | 3 +++ 1 file changed, 3 insertions(+) diff --git a/bridge/src/main/java/com/iluwatar/bridge/App.java b/bridge/src/main/java/com/iluwatar/bridge/App.java index e8774caea..972f49b2f 100644 --- a/bridge/src/main/java/com/iluwatar/bridge/App.java +++ b/bridge/src/main/java/com/iluwatar/bridge/App.java @@ -2,6 +2,9 @@ package com.iluwatar.bridge; /** * + * The Bridge pattern can also be thought of as two layers of abstraction. With Bridge, + * you can decouple an abstraction from its implementation so that the two can vary independently. + *

* In Bridge pattern both abstraction ({@link MagicWeapon}) and implementation * ({@link MagicWeaponImpl}) have their own class hierarchies. The interface of the * implementations can be changed without affecting the clients.