Skip to main content

Creational Design Patterns-Factory Method Pattern


Design Patterns can be categorized under the following Heads
  1. Creational
  2. Structural
  3. Behavioral


This section deals with the creational design patterns,

Creational Patterns
The creational patterns aim to separate a system from how its objects are created, composed, and represented.
Creational Patterns can be classified as follows
1. Abstract Factory
2. Builder
3. Factory
4. Prototype
5. Singleton

Creational patterns encapsulate the knowledge about which classes a system uses, but they hide the details of how the instances of these classes are created and put together.


Factory Method Pattern

The Factory Method pattern is a way of creating objects, but letting subclasses decide exactly which class to instantiate.

Various subclasses might implement the interface; the Factory Method instantiates the appropriate subclass based on information supplied by the client or extracted from the current state.

Define an interface for creating an object, but let subclasses decide which class to instantiate. Factory Method lets a class defer instantiation to subclasses.

Example:
The Example presented below is a basic document creation factory, where different types of documents(Resumes, Reports etc.) can be created using the Factory Pattern

public abstract class DocPage
  {
     public string Header
     {

         set { Header = "P.Solutions"; }
    
     }
     public string Footer
     {

         set { Footer = "Confidential Document"; }

     }

  }

  class SkillSetPage : DocPage
  {
   
  }

  class EducationalDetailsPage : DocPage

  {

  }

  class ExperienceSummaryPage : DocPage

  {

  }
  class BriefInrtoPage : DocPage

  {

  }

  class FindingsPage : DocPage

  {

  }
 
  class ConclusionPage : DocPage

  {

  }

 class SummaryPage : DocPage

  {

  }

 class BibliographyPage : DocPage
  {

  }



//The 'Creator' abstract class. This is class that acts as creator of  Documents, depending upon the requirements


 public abstract class Document
  {

    private List<DocPage> _pages = new List<DocPage>();

     // Constructor calls abstract Factory method

    public Document()
    {

      this.CreatePages();

    }

  public List<DocPage> Pages
    {
      get { return _pages; }
    }
    // Factory Method

    public abstract void CreatePages();

  }

  // 'ConcreteCreator' classes. These Classes  are called in by Client , hieding the details as to how the classes produce documnents

 public class Resume : Document
  {
    // Factory Method implementation

    public override void CreatePages()
    {
      Pages.Add(new SkillsPage());
      Pages.Add(new EducationPage());
      Pages.Add(new ExperiencePage());
    }

  }

 
  /// A 'ConcreteCreator' class

  ///

  class Report : Document

  {
   // Factory Method implementation
    public override void CreatePages()
    {

      Pages.Add(new IntroductionPage());

      Pages.Add(new ResultsPage());

      Pages.Add(new ConclusionPage());

      Pages.Add(new SummaryPage());

      Pages.Add(new BibliographyPage());

    }

  }

All in Place, Let’s now call these classes to get the documents.

protected void Page_Load(object sender, EventArgs e)
    {
          
        Resume rs = new Resume();
        Response.Write("");
        foreach( DocPage dp in rs.Pages)
        {
           Response.Write("
");
            Response.Write(dp.GetType().Name);
       
        }
       
     
   }

 
When called, as shown above, Following pages become part of Resume document.
SkillsPage
EducationPage
ExperiencePage 


Please note that instead of the abstract classes, Interface is generally considered for implementing the Factory pattern. In case you feel the need, feel free to modify the code for using interfaces.

For further understanding  implementation of the pattern in .Net, go to the following link.
 http://aspalliance.com/1751_Exemplifying_the_Factory_Method_Pattern_inside_the_NET_Framework.all

Hope this was helpful,

Till next time. Happy Coding!!
 



Comments

Post a Comment

Popular posts from this blog

Asp.Net 4.0: An Overview-Part-III

This is the last post in the series which will explore the following new features of ASP.Net 4.0  Performance Monitoring for Individual Applications in a Single Worker Process Web.config File Refactoring Permanently Redirecting a Page Expanding the Range of Allowable URLs Performance Monitoring for Individual Applications in a Single Worker Process It is a common practice to host multiple ASP.NET applications in a single worker process, In order to increase the number of Web sites that can be hosted on a single server. This practice results in difficulties for server administrators to identify an individual application that is experiencing problems. ASP.NET 4 introduces new resource-monitoring functionality introduced by the CLR. To enable this functionality, following XML configuration snippet is added to the aspnet.config configuration file.(This file is located in the directory where the .NET Framework is installed ) <?xml version="1.0" encoding="UTF-8...
Post a Comment
Read more

WCF-REST Services-Part-II

HOW REST is implemented in WCF Part-I of the series explored the REST conceptually and this post will explore how REST is implemented in WCF. For REST implementation in WCF, 2 new attributes namely WebGetAttribute and WebInvokeAttribute are introduced in WCF along with a URI template mechanism that enables you to declare the URI and verb to which each method is going to respond. The infrastructure comes in the form of a binding ( WebHttpBinding ) and a behavior ( WebHttpBehavior ) that provide the correct networking stack for using REST. Also, there is some hosting infrastructure help from a custom Service¬Host ( WebServiceHost ) and a ServiceHostFactory ( WebServiceHostFactory ). How WCF Routes messages WCF routes network messages to methods on instances of the classes defined as implementations of the service. Default behavior ( Dispatching ) for WCF is to do this routing based on the concept of action. For this dispatching to work, an action needs to be present in ev...
Post a Comment
Read more

WPF Routing

WPF (3.5) introduced the concept of Routing that made the event routing easies in the scenarios where it was tedious to handle events. Consider a scenario where there are a number of Hyperlinks in a Panel that direct to separate locations on Click. Now if this is done in normal programming, each hyperlink will have to have code for execution. It would be easier and cleaner if we could handle the hyperlinks in the container (the Panel) that handles the click and redirects to appropriate location. WPF handles the events with the following 3 strategies. Direct events are like ordinary .NET events. They originate in one element and don’t pass to any other. For example, MouseEnter is a direct event. Bubbling events are events that travel up the containment hierarchy. For example, MouseDown is a bubbling event. It is raised first by the element that is clicked. Next, it is raised by that element’s parent, and then by that element’s parent, and so on, until WPF reaches the top of the e...
Post a Comment
Read more