Skip to main content

Java Design Patterns

Introduction :
Design patterns represent the best practices used by experienced object-oriented software developers. Design patterns are solutions to general problems that software developers faced during software development. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations.
These solutions were obtained by trial and error by numerous software developers over quite a substantial period of time.
In 1994, four authors Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides published a book titled Design Patterns - Elements of Reusable Object-Oriented Software which initiated the concept of Design Pattern in Software development.These authors are collectively known as Gang of Four (GOF).
As per the design pattern reference book Design Patterns - Elements of Reusable Object-Oriented Software, there are 23 design patterns which can be classified in three categories:

  1. Creational (the way of creating objects)
  2. Structural (simplifies the structure by identifying the relationships)
  3. Behavioral (interaction between the objects should be in such a way that they can easily talk to each other and still should be loosely coupled)

Creational Patterns :
These design patterns provide a way to create objects while hiding the creation logic, rather than instantiating objects directly using new operator. This gives more flexibility to the program in deciding which objects need to be created for a given use case.
It provides instantiation mechanisms, making it easier to create objects in a way that suits the situation.
There are following 6 types of Creational design patterns
  1. Factory Method : loose-coupling, defines an interface or abstract class for creating an object but let the subclasses decide which class to instantiate. 
  2. Abstract Factory : create families of related to objects but without specifying their concrete sub-classes
  3. Singleton : only one instance and provides a global point of access to it
  4. Prototype : cloning of an existing object instead of creating new one and can also be customized as per the requirement.
  5. Builder : construct a complex object from simple objects using step-by-step approach
  6. Object Pool : to reuse the object that are expensive to create 
Structural Patterns :
These design patterns concern class and object composition. Concept of inheritance is used to compose interfaces and define ways to compose objects to obtain new functionalities. It generally deal with relationships between entities, making it easier for these entities to work together.
There are following 7 types of structural design patterns.
  1. Adapter   : Adapting an interface into another according to client expectation.
  2. Bridge    :       Separating abstraction (interface) from implementation.
  3. Composite : Allowing clients to operate on hierarchy of objects.
  4. Decorator : Adding functionality to an object dynamically.
  5. Facade  :       Providing an interface to a set of interfaces.
  6. Flyweight :   Reusing an object by sharing it.
  7. Proxy :         Representing another object.
Behavioral Patterns :
These design patterns are specifically concerned with communication between objects.These are used in communications between entities and make it easier and more flexible for these entities to communicate.
  1. Chain of Responsibility 
  2. Command 
  3. Interpreter 
  4. Iterator 
  5. Mediator 
  6. Memento 
  7. Observer
  8. State
  9. Strategy
  10. Template
  11. Visitor  

Comments

Popular posts from this blog

Oracle ADF Interview questions

Why ADF ?     Oracle ADF (Application Development Framework) is state of the art technology to rapidly build enterprise application. ADF is a mature J2EE development framework and many other products under Oracle Fusion Middleware stack are build upon ADF 11g. ADF provides variety of inbuilt components that minimizes the need to write code allowing users to focus more on features and business aspects of the application. With WebCenter and SOA plugins, we can also integrate WebCenter Services and SOA into your application making it rich and extensible. Explain about JSF lifecycle ? The six phases of the JSF application lifecycle are as follows (note the event processing at each phase): -Restore view -Apply request values; process events -Process validations; process events -Update model values; process events -Invoke application; process events -Render response Immediate=true : A command button that does not provide ...

The file store "WLS_DIAGNOSTICS" could not be opened

WLS_DIAGNOSTIC ERROR weblogic.store.PersistentStoreException: [Store:280073]The file store "WLS_DIAGNOSTICS" could not be opened because it contained a file with the invalid version 1. A file of version 2 was expected. When you get this error while running your application on internal weblogic server delete the following file WLS_DIAGNOSTICS000000.DAT search the file in following path C:\jdev_work\system11.1.1.5.37.60.13\DefaultDomain this file is in DefaultDomain folder of your jdev. and delete the WLS_DIAGNOSTICS000000.DAT file . and run your applicatuon

Overview Editor for bc4j.xcfg

This is used to customize the configuration settings for the application pool, connection pool, and transactions. Select the Application Module, then select a configuration from the Configurations list. You can specify a Default Configuration from the dropdown to use with selected application module. Edit the name of the configuration in Details. Its having 3 tabs 1.Database and Scalability 2. Properties 3. Custom Properties Database and Scalability Tab : In Database and Scalability you can mention the JDBC data source definition for each application module. You can choose to connect to a JDBC data source or to a JDBC URL.The default connection type is the default data source. A data source is a vendor-independent encapsulation of a database server connection on the application server. 1. Data sources ( JNDI name) offer advantages over a JDBC URL connection because the data source can be tuned, reconfigured, or remapped without changing the deployed application. 2. JDB...