According to me inner class would be shared amongst all the instances of the outer class wereas the static block would be executed for every instance which would lead to multiple constructor call for outer class.

Jacob

I do see where you are coming from, and yes - to be fair, to a certain extent I do agree with what you have said. But somehow I am not a firm believer in judging someone on the basis of 30-40 minutes of interview. As you said, past accomplishments and duties are important to see how the person fits into the job requirement. More important is credible means to verify the same. The pool of questions are more or less limited, and the interviewee is already in a “interview-taking” mode. What if you are stuck at two candidates both of whom you consider to be a “fit”. Probably you are looking at something which separates one from the other. For me, this “something” is the smartness or ‘out-of-box’ thinking [excuse me for this phrase - I know this appeared in the top 10 most cliched phrases in a survey soemtime back ]. Perhaps this is my way of checking that “something” extra, by giving the candidate the opportunity to differentiate himself/ herself.

Cheers,
Anirudh

static{
dateCounterInfoFile = new DateCounterInfoFile();
}

public static Singleton getInstance(){
= return dateCounterInfoFile;
}

since static block will be executed at time of class loading, so instead of creating new static inner class, I felt the above approach is easy. what is your comments