Applied Design Patterns with Java

Structural :: Bridge (151) {C ch 10}

Example - UML : productList

Example - Java :: Patterns\Structural\Bridge

Pattern Concept: to allow separating a class's interface from its implementation, so that the implementation can be varied or replaced without changing the client class code.

Issues and Consequences of the Bridge pattern include:

• Bridge is meant to keep the interface of a client program intact while changing the actual class that is displayed or used;
• Bridge and its class implementation can be extended separately, and usually without much interaction;
• Bridge allows hiding the implementation details from the client program more easily.

The example Java program is called 'productList'.

The UML diagram is above, and the list of Java files is below:

Catalog Structural Prev Next