Today, I faced this issue in Java coding. I needed to load an XML file which was in my classpath but not in the same directory as the classes. The deliverable was a jar and the properties and the configuration XML files were in a different folder and were appended to the classpath at the runtime. The issue was that the file could not be located through the the statement<\/p>\n
String fileName = getClass.getSystemResource(“config.xml”).getFile;<\/p>\n
Then I thought that it checks relative to the current class and so used the statement<\/p>\n
String fileName = ClassLoader.getSystemResource(“config.xml”).getFile;<\/p>\n
But then, it wouldn’t still recognize the file. The reason is the same, it checks relative to the classes folder. I did not want to get the classpath from the system and browse through it for the config file since the class path could get larger. A couple of google searches and a little research later, I found the solution. The workaround is by using the following statement<\/p>\n
String fileName = Thread.currentThread().getContextClassLoader().getResource(“config.xml”).getFile;<\/p>\n
It only makes sense since in the above statement, you get hold of the context class loader and find the path in the entire classpath…<\/p>\n