They’re for two very different purposes: The static initializer block will be called on loading of the class, and will have no access to instance variables or methods. As per @Prahalad Deshpande’s comment, it is often used to create static variables. The non-static initializer block on the other hand is created on object construction only, … Read more
Static initializers are useful as cletus mentioned and I use them in the same manner. If you have a static variable that is to be initialized when the class is loaded, then a static initializer is the way to go, especially as it allows you to do a complex initialization and still have the static … Read more
First of all, there are two types of initialization blocks: instance initialization blocks, and static initialization blocks. This code should illustrate the use of them and in which order they are executed: public class Test { static int staticVariable; int nonStaticVariable; // Static initialization block: // Runs once (when the class is initialized) static { … Read more
The non-static block: { // Do Something… } Gets called every time an instance of the class is constructed. The static block only gets called once, when the class itself is initialized, no matter how many objects of that type you create. Example: public class Test { static{ System.out.println(“Static”); } { System.out.println(“Non-static block”); } public … Read more