Introduction

This article will examine some of the uses that the enum type can be put to. I don't know about you, but I like using enumerators. The percieved usage of the enum type is that they provide a list of possible values and are required for the switch statement. That's it right? Big wrong.

The enum type is a class. By remembering this, the extensibility of an enum is great. It can be used for a whole lot more than simply representing the fixed values for an atribute.

It's Objects All the Way Down

I'll start with a simple premise. An enum type defines a class that has a fixed number of instances. Like any class there can be member variables and methods giving the whole java world in a simple structure. Lets look at a simple example:

public enum Season
{
   SUMMER,
   WINTER,
   AUTUMN,
   SPRING
}

Here is a class, called Season, that has four fixed instances. It's important to remeber this as the fact that you have four objects is what gives the enum its simple structure and its amazing power. Power it is sworn to use for good.

A common use of enums is in switch statements such as this:

String getForcast(Season season)
{
  switch (season)
  {
	 case SUMMER:
	 {
		return "Sun, sun, sun";
	 }
	 case AUTUMN:
	 {
		return "Cold and blustery";
	 }
	 case WINTER:
	 {
		return "Snow and ice";
	 }
	 case SPRING:
	 {
		return "Overcast with showers";
	 }
  }
  return null;
}

"Hang on! The elements of the enumerator are all objects so can't they just have a method to return the forcast?" I hear you cry. Good spot. That is exactly the way to go. A member variable, a method and a simple constructor and off you go:

public enum Season {
   SUMMER("Summer", "Sun, sun, sun"),
   WINTER("Winter", "Snow and ice"),
   AUTUMN("Autumn", "Cold and blustery"),
   SPRING("Spring", "Overcast with showers");

   private final String seasonName;
   private final String forcast;
   private Season(String seasonName, String forcast)
   {
      this.seasonName = seasonName;
      this.forcast = forcast;
      System.out.println("Creating " + this);
   }
   String getForcast()
   {
      return this.forcast;
   }

   public String toString()
   {
      return seasonName + "{" + forcast + '}';
   }
}

I've included a friendly string description and overridden the method toString().

Now, instead of having to write a method outside of Season that takes a value as an argument, the values can be invoked directly to get the value:

String forcast = Season.WINTER.getForcast();

The Immutible Likeness of Being [An Enumeration]

If you're observent the member variables are both marked final. This is not mandated but, and it's a big Jo-Lo one, it is definetly encouraged.

So each enumeration is an object and it can have variables, methods, the whole low-flying acrobatics team. These are not just objects, their special status means they must be treated as immutible objects. They're not quite immutible but it is a good perspective to take.

By being an enum, there is no need for hashCode() and equals() methods. Each instance is unique and its equality is fixed. Because of this nature, it is recommended that you don't change their states.

You Want Functionality With That?

I've shown above the way that enum objects can have properties and methods. Sometimes the behaviour of an action must differ depending on the value of the enum. This can be achieved with an abstract method that is overridden by each enum or by having a functional class provide the behaviour.

The abstract method first:

public enum Season
{

   SUMMER("Summer", "Sun, sun, sun")
   {
      boolean willItRain()
      {
         return false;
      }
   },
   //...
   SPRING("Spring", "Overcast with showers")
   {
      boolean willItRain()
      {
         return true;
      }
   };

   //...

   abstract boolean willItRain();
}

This works but it isn't that extensible and the enumeration class soon becomes clogged if you have just a few of the overrides. It is time to delegate the work to a functional class, enter the enumeration factory method.

We first move all the forcasting out of the enum class. We have a base, SeasonFunctions that is abstract and then four lovely children that can impliment the functionality anyway they see fit:

abstract class SeasonFunctions {
   private final String seasonName;
   private final String forcast;

   SeasonFunctions(String seasonName,
         String forcast)
   {
      this.seasonName = seasonName;
      this.forcast = forcast;
      System.out.println("Creating " + this);
   }
   abstract boolean willItRain();
   abstract int dayTimeHigh();
   abstract int nightTimeLow();

      String getForcast()
   {
      return this.forcast;
   }

   public String toString()
   {
      return "SeasonFunctions{" + this.getSeasonName()  + "}";
   }

   String getSeasonString()
   {
      return this.getSeasonName() + "{" + this.getForcast() + '}';
   }

   private String getSeasonName()
   {
      return this.seasonName;
   }
}

History

Initial submission - more to come.