When we have Static class, what is the need for Singleton design pattern. I tried googling, but didn't get satisfactory answer.
Please tell me if anybody knows the exact diff
Welcome to the Java Programming Forums
The professional, friendly Java community. 21,500 members and growing!
The Java Programming Forums are a community of Java programmers from all around the World. Our members have a wide range of skills and they all have one thing in common: A passion to learn and code Java. We invite beginner Java programmers right through to Java professionals to post here and share your knowledge. Become a part of the community, help others, expand your knowledge of Java and enjoy talking with like minded people. Registration is quick and best of all free. We look forward to meeting you.
>> REGISTER NOW TO START POSTING
Members have full access to the forums. Advertisements are removed for registered users.
When we have Static class, what is the need for Singleton design pattern. I tried googling, but didn't get satisfactory answer.
Please tell me if anybody knows the exact diff
Define your terms. What is a static class? What is a singleton?
Useful links: How to Ask Questions the Smart Way | Use Code Tags | Java Tutorials
Static Void Games - Play indie games, learn from game tutorials and source code, upload your own games!
Singleton class need to have only one instance per JVM at any given time.
In Static class we can directly access the methods/variables without creating a instance of it.
Then why singleton is required if we can achieve it through static cl
Singletons allow you the all the benefits of using object oriented programming (inheritance, polymorphism, etc.). This lets you re-use much of the existing code base.
ex.: A class which counts how many times an ActionEvent is dispatched from various components (doesn't have to be a Singleton, but just pretend it is ).
public class ActionCounter implements ActionListener { private int counter = 0; public static ActionCounter INSTANCE = new ActionCounter(); private ActionCounter() {} public synchronized void actionPerformed(ActionEvent e) { ++counter; } public int getCounter() { return counter; } }
The two different patterns simply allow you to think about your code from a different mind set.