Skip to main content

Factory Design Pattern - Java

Factory Design Pattern

Factory Design Pattern works as per it's name. As one Factory can generate various types of items but of a specific category. Like, Car Factory ( Nissan Car Factory ) can create cars like, Micra, Sunny, Evalia but it can't create Duster. Because,Duster can be created by Renault Car Factory.



So, with the same concept, A company can create a various types of Employees. Like, Developer, Admin , Developer Manager. But, only Developer can be Dev Manager.




Here is the Complete example of creating the Company with all the Employee details.

Class Company.java
/**
 * Parent Class of all Class. Employee is Base class of all types of Employee.
 *
 * @author Hari
 *
 */
abstract class Employee {
 public abstract void getMyDetails();
}
/**
 * Admin is child class of the Employee class.
 *
 * @author Hari
 */
class Admin extends Employee {
 public void getMyDetails() {
  System.out.println("I'm admin");
 }
}
/**
 * Developer is another child class of Employee Class
 *
 * @author Hari
 */
class Developer extends Employee {
 public void getMyDetails() {
  System.out.println("I'm Developer");
 }
}
/**
 * DevManager is the Class derived from Developer.s
 *
 * @author Hari
 *
 */
class DevManager extends Developer {
 public void getMyDetails() {
  super.getMyDetails();
  System.out.println("I'm Manager");
 }
}
/**
 * Enum Type id defined to get the argument as specific type of the class
 *
 * @author Hari
 *
 */
enum EmployeeType {
 ADMIN, DEVELOPER, DEV_MANAGER
}
/**
 * Company Class is Factory. Company can create any type of the Employee.
 *
 * @author Hari
 *
 */
public class Company {
 /**
  * Method to create a Employee.
  *
  * @param employeeType
  * @return
  */
 public static Employee hireEmployee(EmployeeType employeeType) {
  Employee e = null;
  switch (employeeType) {
  case ADMIN:
   e = new Admin();
   break;
  case DEVELOPER:
   e = new Developer();
   break;
  case DEV_MANAGER:
   e = new DevManager();
   break;
  }
  return e;
 }
}

Comments

Popular posts from this blog

Could not launch the product because the associated workspace is currently in use by another Eclipse application

If you are seeing following error at the beginning of the Eclipse or any RCP based product then here is the solution: Error Message: "Could not launch the product because the associated workspace is currently in use by another Eclipse application." or “Workspace in use or cannot be created chose a different one.” Solution :  go to workspace location remove file <workspace location>/.metadata/.lock Reason: Through eclipse, user can create multiple Workspace locations. One Workspace location can be edited by one user at a time. A workspace contains the data related to various project configuration and local file storage. To avoid multiple users to access the same workspace, eclipse is maintaining a ".lock" file inside the Workspace. Eclipse will remove this ".lock" file when you will close the Eclipse. But in some cases, the Eclipse will crash due to some error, due to which it could not able to remove ".lock" file from

HHH000424: Disabling contextual LOB creation as createClob() method threw error : java.lang.reflect.InvocationTargetException

HHH000424: Disabling contextual LOB creation as createClob() method threw error : java.lang.reflect.InvocationTargetException If you get following error while connecting to your Database with Spring boot, try the suggested solution below: 2018 - 11 - 25 15 : 28 : 50.078 INFO 5335 --- [ main] o. h . e . j . e . i . LobCreatorBuilderImpl : HHH000424: Disabling contextual LOB creation as createClob() method threw error : java. lang . reflect . InvocationTargetException java. lang . reflect . InvocationTargetException : null at sun. reflect . NativeMethodAccessorImpl . invoke0 (Native Method) ~[na: 1.8 . 0 _161] at sun. reflect . NativeMethodAccessorImpl . invoke (NativeMethodAccessorImpl. java : 62 ) ~[na: 1.8 . 0 _161] at sun. reflect . DelegatingMethodAccessorImpl . invoke (DelegatingMethodAccessorImpl. java : 43 ) ~[na: 1.8 . 0 _161] at java. lang . reflect . Method . invoke (Method. java : 498 ) ~[na: 1.8 . 0 _161] at org. hibernate . engin

Use these Eclipse RCP Testing tools before your code goes to LIVE

Use these Eclipse RCP Testing tools before your code goes to LIVE Testing is most important part of any software development lifecycle. There are different type of testing required before Eclipse RCP tool is released to productions. Eclipse RCP is very easy to test with the these testing tools: UI Testing: RCP Testing Tool RCP Testing Tool is a project for GUI testing automation of Eclipse-based applications. RCPTT is fully aware about Eclipse Platform's internals, hiding this complexity from end users and allowing QA engineers to create highly reliable UI tests at great pace. SWT Bot SWTBot is an open-source Java based UI/functional testing tool for testing SWT, Eclipse and GEF based applications.  SWTBot provides APIs that are simple to read and write. The APIs also hide the complexities involved with SWT and Eclipse. This makes it suitable for UI/functional testing by everyone, not just developers. SWTBot also provides its own set of ass