Java201.com

• Resistance is Futile: How to Make Your Java Objects Conform with the Adapter Pattern by Barry Burd, Michael P. Redlich   - [Clicks: 34]
  Ever have a nice, useful piece of code, that you couldn't easily use in an existing application because of a mismatched interface? The Adapter design pattern helps you align interfaces so that code won't go to waste.
  http://javaboutique.internet.com/tutorials/adapter/ - Sep, 2006
• Manufacturing Java Objects with the Factory Method Design Pattern by Barry Burd, Michael P. Redlich   - [Clicks: 40]
  You need to instantiate certain objects from a pool of related objects, but you won't know which ones until runtime. Find out how the factory method design pattern can help you write this code.
  http://javaboutique.internet.com/tutorials/factory/ - Aug, 2006
• Lazy Loading is Easy: Implementing a Rich Domain Model by Johannes Brodwall   - [Clicks: 32]
  Lazy loading--not fetching data until it's needed--is an approach that gets a lot of developers nodding their heads in agreement, even if they don't actually try implementing it themselves. But as Johannes Broadwall reports, it's not hard to do, and conveys some genuine benefits.
  [Includes sample code]
  http://today.java.net/pub/a/today/2006/07/13/lazy-loading-is-easy.html - Jul, 2006
• Pipeline to Visitor Design Pattern by Waleed Hassan   - [Clicks: 47]
  This article presents a new design pattern, Pipeline to Visitor, that handles the issue of building SW components in a way that makes the SW maintainable.
  http://www.theserverside.com/tt/articles/article.tss?l=PipelineVisitor - Jun, 2006
• Keeping Your Java Objects Informed with the Observer Design Pattern by Barry Burd, Michael P. Redlich   - [Clicks: 29]
  Tightly coupling your Java objects can result in all sorts of headaches when you need extend your app. Find out how the Observer design pattern can help keep your classes ready to provide information to any new objects that may come along.
  http://javaboutique.internet.com/tutorials/observer/ - Jun, 2006
• All About the Singleton Design Pattern by Sridhar M S   - [Clicks: 41]
  Using the Singleton pattern allows you to have a class distribute the only instance of itself. This restricts instantiation of a class to one, which can be useful when you require exactly one object to coordinate actions across an application.
  http://javaboutique.internet.com/tutorials/singleton/ - May, 2006
• Handling events from native objects in Java code by Sachin Agrawal, Vijil Chenthamarakshan   - [Clicks: 22]
  When you need to use objects written in other languages, communications between a native event source and Java listeners can be tricky -- especially in multithreaded environments. This article helps you deal with traditional native libraries effectively by using a design pattern for transparently handling event communication from native code to the JVM.
  [Includes sample code]
  http://www-128.ibm.com/developerworks/java/library/j-jniobs/index.html - Jan, 2006
• Generically chain dynamic proxies by Srijeeb Roy   - [Clicks: 59]
  Most developers already know how to decorate a business object and add additional behavior to it at runtime. The Gang of Four (GoF) Decorator pattern helps developers achieve this functionality. Under the reflection package, J2SE 1.3 introduced the dynamic proxy, which dynamically decorates business objects. Additionally, chaining dynamic proxies can add multiple behaviors to business objects dynamically at runtime. More specifically, these types of additional behaviors are addressed by aspect-oriented programming (AOP). This article is not intended as an in-depth discussion on AOP; rather, it focuses on generically chaining the dynamic proxies so that the developer can implement some AOP concepts in a framework-driven way. If a project is already using some existing AOP framework, then the developer does not need to worry about implementing a custom framework. But developers who, for whatever reason, do not use these frameworks in their projects can still get the advantage of chaining dynamic proxies in an effective way with little effort.
  [Includes source code]
  http://www.javaworld.com/javaworld/jw-01-2006/jw-0130-proxy.html - Jan, 2006
• Avoid Excessive Subclassing with the Decorator Design Pattern by Barry Burd, Michael P. Redlich   - [Clicks: 56]
  Ever have a fairly simple application become so complex over time that you found yourself dealing with class names like AdminstrativeAssistantAndBloodDriveCanvasser"? Find out how proper use of the Decorator design pattern provides your apps with a more complex model without overcomplicating your coding.
  http://javaboutique.internet.com/tutorials/decorator/ - Jan, 2006

[Top]