設計模式概覽圖
雖然圖已經很老了，但是很直觀，有收藏價值。
更好的一個網站，詳細的介紹設計模式： http://www.oodesign.com/
另一個站點： http://www.javacamp.org/designPattern/
http://stackoverflow.com上一個帖子，總結了Java SE和 Java EE中實現的設計模式。
以及Design Patterns in the JDK
還有PDF版的
design pattern
JDK中設計模式的實現
Creational patterns
Abstract factory (recognizeable by creational methods returning the factory itself which in turn can be used to create another abstract/interface type)
javax.xml.parsers.DocumentBuilderFactory#newInstance()javax.xml.transform.TransformerFactory#newInstance()javax.xml.xpath.XPathFactory#newInstance()java.lang.StringBuilder#append()(unsynchronized)java.lang.StringBuffer#append()(synchronized)java.nio.ByteBuffer#put()(also onCharBuffer,ShortBuffer,IntBuffer,LongBuffer,FloatBufferandDoubleBuffer)javax.swing.GroupLayout.Group#addComponent()- All implementations of
java.lang.Appendable java.util.Calendar#getInstance()java.util.ResourceBundle#getBundle()java.text.NumberFormat#getInstance()java.nio.charset.Charset#forName()java.net.URLStreamHandlerFactory#createURLStreamHandler(String)(Returns singleton object per protocol)java.lang.Object#clone()(the class has to implementjava.lang.Cloneable)java.lang.Runtime#getRuntime()java.awt.Desktop#getDesktop()java.util.Arrays#asList()java.io.InputStreamReader(InputStream)(returns aReader)java.io.OutputStreamWriter(OutputStream)(returns aWriter)javax.xml.bind.annotation.adapters.XmlAdapter#marshal()and#unmarshal()- None comes to mind yet. A fictive example would be
new LinkedHashMap(LinkedHashSet<K>, List<V>)which returns an unmodifiable linked map which doesn’t clone the items, but uses them. Thejava.util.Collections#newSetFromMap()andsingletonXXX()methods however comes close. java.awt.Container#add(Component)(practically all over Swing thus)javax.faces.component.UIComponent#getChildren()(practically all over JSF UI thus)- All subclasses of
java.io.InputStream,OutputStream,ReaderandWriterhave a constructor taking an instance of same type. java.util.Collections, thecheckedXXX(),synchronizedXXX()andunmodifiableXXX()methods.javax.servlet.http.HttpServletRequestWrapperandHttpServletResponseWrapperjavax.faces.context.FacesContext, it internally uses among others the abstract/interface typesLifeCycle,ViewHandler,NavigationHandlerand many more without that the enduser has to worry about it (which are however overrideable by injection).javax.faces.context.ExternalContext, which internally usesServletContext,HttpSession,HttpServletRequest,HttpServletResponse, etc.java.lang.Integer#valueOf(int)(also onBoolean,Byte,Character,ShortandLong)java.lang.reflect.Proxyjava.rmi.*, the whole API actually.java.util.logging.Logger#log()javax.servlet.Filter#doFilter()- All implementations of
java.lang.Runnable - All implementations of
javax.swing.Action java.util.Patternjava.text.Normalizer- All subclasses of
java.text.Format - All subclasses of
javax.el.ELResolver - All implementations of
java.util.Iterator(thus among others alsojava.util.Scanner!). - All implementations of
java.util.Enumeration java.util.Timer(allscheduleXXX()methods)java.util.concurrent.Executor#execute()java.util.concurrent.ExecutorService(theinvokeXXX()andsubmit()methods)java.util.concurrent.ScheduledExecutorService(allscheduleXXX()methods)java.lang.reflect.Method#invoke()java.util.Date(the setter methods do that,Dateis internally represented by alongvalue)- All implementations of
java.io.Serializable - All implementations of
javax.faces.component.StateHolder java.util.Observer/java.util.Observable(rarely used in real world though)- All implementations of
java.util.EventListener(practically all over Swing thus) javax.servlet.http.HttpSessionBindingListenerjavax.servlet.http.HttpSessionAttributeListenerjavax.faces.event.PhaseListenerjavax.faces.lifecycle.LifeCycle#execute()(controlled byFacesServlet, the behaviour is dependent on current phase (state) of JSF lifecycle)java.util.Comparator#compare(), executed by among othersCollections#sort().javax.servlet.http.HttpServlet, theservice()and alldoXXX()methods takeHttpServletRequestandHttpServletResponseand the implementor has to process them (and not to get hold of them as instance variables!).javax.servlet.Filter#doFilter()- All non-abstract methods of
java.io.InputStream,java.io.OutputStream,java.io.Readerandjava.io.Writer. - All non-abstract methods of
java.util.AbstractList,java.util.AbstractSetandjava.util.AbstractMap. javax.servlet.http.HttpServlet, all thedoXXX()methods by default sends a HTTP 405 “Method Not Allowed” error to the response. You’re free to implement none or any of them.
</ul>
Builder (recognizeable by creational methods returning the instance itself)
</ul>
Factory method (recognizeable by creational methods returning an implementation of an abstract/interface type)
</ul>
Prototype (recognizeable by creational methods returning a different instance of itself with the same properties)
</ul>
Singleton (recognizeable by creational methods returning the same instance (usually of itself) everytime)
</ul>
Structural patterns
Adapter (recognizeable by creational methods taking an instance of different abstract/interface type and returning an implementation of own/another abstract/interface type which decorates/overrides the given instance)
</ul>
Bridge (recognizeable by creational methods taking an instance of different abstract/interface type and returning an implementation of own abstract/interface type which delegates/uses the given instance)
</ul>
Composite (recognizeable by behavioral methods taking an instance of same abstract/interface type into a tree structure)
</ul>
Decorator (recognizeable by creational methods taking an instance of same abstract/interface type which adds additional behaviour)
</ul>
Facade (recognizeable by behavioral methods which internally uses instances of different independent abstract/interface types)
</ul>
Flyweight (recognizeable by creational methods returning a cached instance, a bit the “multiton” idea)
</ul>
Proxy (recognizeable by creational methods which returns an implementation of given abstract/interface type which in turn delegates/uses a different implementation of given abstract/interface type)
</ul>
The Wikipedia example is IMHO a bit poor, lazy loading has actually completely nothing to do with the proxy pattern at all.
Behavioral patterns
Chain of responsibility (recognizeable by behavioral methods which (indirectly) invokes the same method in another implementation of same abstract/interface type in a queue)
</ul>
Command (recognizeable by behavioral methods in an abstract/interface type which invokes a method in an implementation of a different abstract/interface type which has been encapsulated by the command implementation during its creation)
</ul>
Interpreter (recognizeable by behavioral methods returning a structurally different instance/type of the given instance/type; note that parsing/formatting is not part of the pattern, determining the pattern and how to apply it is)
</ul>
Iterator (recognizeable by behavioral methods sequentially returning instances of a different type from a queue)
</ul>
Mediator (recognizeable by behavioral methods taking an instance of different abstract/interface type (usually using the command pattern) which delegates/uses the given instance)
</ul>
Memento (recognizeable by behavioral methods which internally changes the state of the whole instance)
</ul>
Observer (or Publish/Subscribe) (recognizeable by behavioral methods which invokes a method on an instance of another abstract/interface type, depending on own state)
</ul>
State (recognizeable by behavioral methods which changes its behaviour depending on the instance’s state which can be controlled externally)
</ul>
Strategy (recognizeable by behavioral methods in an abstract/interface type which invokes a method in an implementation of a different abstract/interface type which has been passed-in as method argument into the strategy implementation)
</ul>
Template method (recognizeable by behavioral methods which already have a “default” behaviour definied by an abstract type)
</ul>
Visitor (recognizeable by two different abstract/interface types which has methods definied which takes each the other abstract/interface type; the one actually calls the method of the other and the other executes the desired strategy on it)
本文由用戶 jopen 自行上傳分享，僅供網友學習交流。所有權歸原作者，若您的權利被侵害，請聯系管理員。
轉載本站原創文章，請注明出處，并保留原始鏈接、圖片水印。
本站是一個以用戶分享為主的開源技術平臺，歡迎各類分享！