Singleton Pattern: Using Enum Version

Question

I do not understand how to implement the Enum Version of the Singleton pattern. Below is an example of implementing "traditional" approach using the Singleton pattern. I would like to change it to use the Enum version but I am not sure how.

public class WirelessSensorFactory implements ISensorFactory{

    private static WirelessSensorFactory wirelessSensorFactory;

    //Private Const
    private WirelessSensorFactory(){
        System.out.println("WIRELESS SENSOR FACTORY");
    }

    public static WirelessSensorFactory getWirelessFactory(){

        if(wirelessSensorFactory==null){
            wirelessSensorFactory= new WirelessSensorFactory();
        }

        return wirelessSensorFactory;
    }

}

Another form of implementing the Singleton pattern using an Enum, it was introduced in java 1.5 — user3287264
– user3287264, Commented May 18, 2014 at 10:55
thanks now I see what you mean. Try this link: stackoverflow.com/questions/18425693/… — kviiri
– kviiri, Commented May 18, 2014 at 10:56

JB Nizet · Accepted Answer · 2014-05-18 10:57:17Z

37

public enum WirelessSensorFactory {
    INSTANCE;

    // all the methods you want
}

Here's your singleton: an enum with only one instance.

Note that this singleton is thread-safe, while yours is not: two threads might both go into a race condition or visibility problem and both create their own instance of your singleton.

answered May 18, 2014 at 10:57

JB Nizet

694k94 gold badges1.3k silver badges1.3k bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

user3287264 Over a year ago

Thanks, How would i then use this class within a main method?

JB Nizet Over a year ago

As any other enum: WirelessSensorFactory.INSTANCE.someMethod()

user3287264 Over a year ago

Yeah, so only one instance of the class can only ever be used, is a multiton implemented in the same way?

SSC Over a year ago

This is also safe from allowing multiple objects from deserilization as well as reflection.

OldCurmudgeon · Accepted Answer · 2015-06-05 13:02:52Z

The standard pattern is to have your enum implement an interface - this way you do not need to expose any more of the functionality behind the scenes than you have to.

// Define what the singleton must do.
public interface MySingleton {

    public void doSomething();
}

private enum Singleton implements MySingleton {

    /**
     * The one and only instance of the singleton.
     *
     * By definition as an enum there MUST be only one of these and it is inherently thread-safe.
     */
    INSTANCE {

                @Override
                public void doSomething() {
                    // What it does.
                }

            };
}

public static MySingleton getInstance() {
    return Singleton.INSTANCE;
}

hovanessyan · Accepted Answer · 2014-05-18 11:08:09Z

5

Online reference of the Effective Java chapter here.

public enum WirelessSensorFactory implements ISensorFactory { // change CLASS to ENUM here

        INSTANCE; //declare INSTANCE of the Enum

        //private static WirelessSensorFactory wirelessSensorFactory;

        // Remove the private construct - it's Enum, 
        // so you don't need to protect instantiations of the class
          //private WirelessSensorFactory(){
          //   System.out.println("WIRELESS SENSOR FACTORY");
          //}

        // You don't need to check if instance is already created, 
        // because it's Enum, hence you don't need the static var
          //public WirelessSensorFactory getWirelessFactory(){
          //    if(wirelessSensorFactory==null){
          //        wirelessSensorFactory= new WirelessSensorFactory();
          //    }
          //    return wirelessSensorFactory;
          //}

        /*
         * All other methods you need and 
         * implementation of all the Factory methods from your interface
         */

}

Usage:

WirelessSensorFactory.INSTANCE.<any public method>

edited May 18, 2014 at 11:08

answered May 18, 2014 at 11:02

hovanessyan

31.6k6 gold badges59 silver badges84 bronze badges

2 Comments

user3287264 Over a year ago

Thanks, How would i then use this class within a main method?

hovanessyan Over a year ago

@RNI2013 I included example usage.

kennySystemExit · Accepted Answer · 2014-05-18 11:00:44Z

3

It is explained here: http://javarevisited.blogspot.sk/2012/07/why-enum-singleton-are-better-in-java.html So, it can be simple done like this:

public enum EasySingleton{
    INSTANCE;
}

and also with using abstract factory design pattern:

public class Singleton{
    //initailzed during class loading
    private static final Singleton INSTANCE = new Singleton();

    //to prevent creating another instance of Singleton
    private Singleton(){}

    public static Singleton getSingleton(){
        return INSTANCE;
    }
}

answered May 18, 2014 at 11:00

kennySystemExit

3292 gold badges5 silver badges23 bronze badges

Comments

Uresh K · Accepted Answer · 2017-01-25 02:09:09Z

0

It is much easier than the all other Singleton creation version : -

public enum WirelessSensorFactory {

        INSTANCE;

        //private static WirelessSensorFactory wirelessSensorFactory;

        //Private Const
        //private WirelessSensorFactory(){

            //System.out.println("WIRELESS SENSOR FACTORY");

       // }


      //  public static WirelessSensorFactory getWirelessFactory(){

            //if(wirelessSensorFactory==null){

               // wirelessSensorFactory= new WirelessSensorFactory();
           // }

           // return wirelessSensorFactory;
       // }

}

edited Jan 25, 2017 at 2:09

Uresh K

1,13611 silver badges17 bronze badges

answered Mar 31, 2016 at 9:25

Mukesh

5961 gold badge10 silver badges13 bronze badges

Comments

Fruchtzwerg · Accepted Answer · 2016-07-20 11:38:30Z

-1

Following is a sample of singlton class,

public class SingletonClass {
    private static SingletonClass singletonInstance = null;

    private SingletonClass() {      
    }

    public static SingletonClass getSingletonInstance() {       
        if(singletonInstance == null) {
            synchronized (SingletonClass.class) {
                if(singletonInstance == null) {
                  singletonInstance = new SingletonClass();
                }
            }
        }
        return singletonInstance;
    }
}

This snippet will workout in the multithreaded environment too as it applies lock on the class.

edited Jul 20, 2016 at 11:38

Fruchtzwerg

11.4k12 gold badges44 silver badges57 bronze badges

answered Jul 20, 2016 at 11:02

SUKHDEV PATIL

275 bronze badges

4 Comments

impeto Over a year ago

This is wrong. The way the code is, it only works in multithreaded SINGLE core CPU systems. In multicore system this method is faulty. There is no "happens-before" link between the writes and reads.

Mitra Over a year ago

Make singletonInstance volatile to guarantee happens-before

SUKHDEV PATIL Over a year ago

Yeah...needed a object to be volatile, private volatile static SingletonClass singletonInstance = null;

hackjutsu Over a year ago

As discussed before, volatile is required.

Collectives™ on Stack Overflow

Singleton Pattern: Using Enum Version

6 Answers 6

4 Comments

Comments

2 Comments

Comments

Comments

4 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

6 Answers 6

4 Comments

Comments

2 Comments

Comments

Comments

4 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related