title: Proper singleton design?
body: <blockquote>
    <p><strong>Possible Duplicate:</strong><br>
    <a href="https://stackoverflow.com/questions/70689/efficient-way-to-implement-singleton-pattern-in-java">Efficient way to implement singleton pattern in Java</a>  </p>
  </blockquote>
  
  
  
  <p>I have a singleton class that acts as a state saver for my application. For instance if I have a view that has some data, I just pacakge the data to a saved state serializable object and pass it to my singleton for retrival later. This all seems natural and proper, but I have deviated from the singleton example on <a href="http://en.wikipedia.org/wiki/Singleton_pattern" rel="nofollow noreferrer">Wiki</a>. Intead of having a get instance method that will let me retrieve the instance and call methods though the instance, I instead just set every method to static and use the class statically.</p>
  
  <p>Is this bad form? Is there a performance lose?</p>
  
  <p>Thanks for any tips ~Aedon</p>