gaspersic/java-design-patterns
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Made changes according to feedback issue #258

Browse Source
This commit is contained in:
amit2103
2015-10-09 23:20:58 +05:30
parent eb22febdfc
commit 9d0673af0a
2 changed files with 1 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
monostate/index.md
View File

@@ -14,7 +14,7 @@ tags: Java
**Applicability:** Use the Monostate pattern when **Applicability:** Use the Monostate pattern when
* The same state must be shared across all instances of a class. * The same state must be shared across all instances of a class.
* Typically this pattern might be used everywhere a SingleTon might be used. Singleton usage however is not transparent, Monostate usage is. * Typically this pattern might be used everywhere a Singleton might be used. Singleton usage however is not transparent, Monostate usage is.
* Monostate has one major advantage over singleton. The subclasses might decorate the shared state as they wish and hence can provide dynamically different behaviour than the base class. * Monostate has one major advantage over singleton. The subclasses might decorate the shared state as they wish and hence can provide dynamically different behaviour than the base class.
**Typical Use Case:** **Typical Use Case:**

1
monostate/src/main/java/com/iluwatar/monostate/Request.java
View File

@@ -10,7 +10,6 @@ public class Request {
public final String value; public final String value;
public Request(String value) { public Request(String value) {
super();
this.value = value; this.value = value;
} }
} }