Converting many ‘if else’ statements to a cleaner approach [duplicate]

by

You could have a Converter interface. Then you could create a class for each Mimetype like:

public interface Converter {

    public void convertToMp3();
    public void convertToOgg();

}

public class MpegConverter implements Converter {

    public void convertToMp3() {
        //Code here
    }

    public void convertToOgg() {
        //Code here
    }

}

You would need a class like this for each converter. Then you could set up a map like this:

Map<String, Converter> mimeTypeMap = new HashMap<String, Converter>();

mimeTypeMap.put("audio/mpeg", new MpegConverter());

Then your convertToMp3 method becomes like this:

Converter converter = mimeTypeMap.get(mimeType);
converter.convertToMp3();

Using this approach you could easily add different converters in the future.

All untested, probably doesn’t compile, but you get the idea

More Related Contents:

  1. What is an efficient way to implement a singleton pattern in Java? [closed]
  2. Design Patterns web based applications [closed]
  3. Singletons vs. Application Context in Android?
  4. Design Patterns: Factory vs Factory method vs Abstract Factory
  5. What is the solution for the N+1 issue in JPA and Hibernate?
  6. Long list of if statements in Java
  7. Subclassing a Java Builder class
  8. Spring AOP vs AspectJ
  9. Builder Pattern in Effective Java
  10. What’s Alternative to Singleton
  11. Marker Interfaces in Java?
  12. why business logic should be moved out of JSP?
  13. Best way to build a Plugin system with Java
  14. How to avoid ‘instanceof’ when implementing factory design pattern?
  15. Replacing if else statement with pattern
  16. Visitor pattern’s purpose with examples [duplicate]
  17. Is it bad practice to make a setter return “this”?
  18. How to get all classes names in a package? [duplicate]
  19. In simplest terms, what is a factory?
  20. Benefits and drawbacks of method chaining and a possibility to replace all void return parameters by the object itself
  21. Parcelable and inheritance in Android
  22. Advantages of Java’s enum over the old “Typesafe Enum” pattern?
  23. Java collections covariance problem
  24. The builder pattern and a large number of mandatory parameters
  25. Why Java allows increasing the visibility of protected methods in child class?
  26. What is the difference between a fluent interface and the Builder pattern?
  27. How to create a singleton class
  28. How to hide the internal structure of a Java API to the rest of the world
  29. Law of Demeter with data model objects
  30. Template design pattern in JDK, could not find a method defining set of methods to be executed in order

Leave a Comment