Getting exception in initializing log4j files?

Finally, I was able to solve this. As later guessed it turned out to be an eclipse configuration. In eclipse 3.7, code name indigo, the way libs were being added to the classpath caused this issue.

Finally, I was able to solve this. As later guessed it turned out to be an eclipse configuration. In eclipse 3.7, code name indigo, the way libs were being added to the classpath caused this issue .. First way: Debug Configurations->classpath->bootstarp entries, if Add libs added by selecting "Add Jars" options, THIS DOES NOT Work.

Correct WAY: Define a classpath variable from window->preferences->java->buildpath->classpath variable, say HIBERNATE_LIBS and point it ti libs folder Now, got to Debug Configurations->classpath->bootstarp entries, select "Advanced option" and add the class path variable. This FIXED the issue. I guess this is specific to 3.7, as I upgraded the eclipse version and started getting this issue, First way still works in eclipse 3.2.

Correct way is to use the Maven ;) – kan Aug 31 '11 at 7:20 Yes I use that in production (Not maven, but ant) and as mentioned it was running fine as well.. just as ease of use I tried this from eclipse .. and it broke .. was just curios to fix it up :) – chandanpandey05 Aug 31 '11 at 18:37 You should use Maven, it's not the same as ant, it's more high-level tool for dependency management. The maven project could be imported in the Eclipse to build all classpaths/etc stuff for you automatically, avoiding human errors. – kan Sep 1 '11 at 7:38.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.