Finding a good design pattern for Java

by

If you have different sets of fields in different versions and want to create a class to proceed them all, you should take a look at Builder design pattern.
https://en.wikipedia.org/wiki/Builder_pattern#Java

More Related Contents:

  1. What is an efficient way to implement a singleton pattern in Java? [closed]
  2. What components are MVC in JSF MVC framework?
  3. Implementing Singleton with an Enum (in Java)
  4. What is the “Execute Around” idiom?
  5. MVC pattern on Android
  6. Abstract class vs Interface in Java
  7. Subclassing a Java Builder class
  8. Converting many ‘if else’ statements to a cleaner approach [duplicate]
  9. When should we use Observer and Observable?
  10. What’s Alternative to Singleton
  11. Marker Interfaces in Java?
  12. Why do we need immutable class?
  13. why business logic should be moved out of JSP?
  14. Singleton Design Pattern: Pitfalls [closed]
  15. Replacing if else statement with pattern
  16. Java – Learning MVC [closed]
  17. Favor composition over inheritance [duplicate]
  18. Using Command Design pattern
  19. How to implement a FSM – Finite State Machine in Java
  20. Parcelable and inheritance in Android
  21. should a db connection be a singleton?
  22. Advantages of Java’s enum over the old “Typesafe Enum” pattern?
  23. Creation of Objects: Constructors or Static Factory Methods
  24. Java Singleton Pattern
  25. Java collections covariance problem
  26. Why use a singleton instead of static methods?
  27. The builder pattern and a large number of mandatory parameters
  28. When would the garbage collector erase an instance of an object that uses Singleton pattern?
  29. What is the difference between a Singleton pattern and a static class in Java? [duplicate]
  30. How to improve the builder pattern?

Leave a Comment