This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
Dear All, I'm up against one of those irritating classpath problems. Let me explain the scenario:
I have an application deployed as a jar file. This application reads a properties file when it fires up. This properties file needs to be placed in a different directory when deployed so that the administrator can edit the properties contained within it. I have tried several ways of reading this file including InputStream l_isAttillaPropertiesInputStream = this.getClass().getClassLoader().getResourceAsStream("AttillaQ.properties");
Currently, the properties file sits in the same directory as the jar file containing the application and the directory is on the classpath. Alas, the InputStream object is still null, i.e. the classloader cannot find the properties file.
How are you running the application? As an executable JAR (with "java -jar myprogram.jar")? If you're doing that, then Java will ignore the CLASSPATH environment variable or any "-classpath" or "-cp" switches on the command line. For executable JARs, you specify the classpath in the manifest file of the JAR.