views:

4172

answers:

1

Is it possible to add a relative directory (ie, foo/bar/plugh) to the java classpath and use

InputStream in = getClassLoader().getResourceAsStream("xyzzy.properties");

To fetch foo/bar/plugh/xyzzy.properties?

My classpath looks like this:

foo.jar;foo/bar/plugh;xyz.jar

And I am able to use classes and resources from both foo and xyz jars but not from the plugh directory. In those cases, in is always null.

I can't get this to work and am not sure if this is just unsupported, I am missing something subtle or if I'm doing something wrong. Do I need to use an absolute path?

+3  A: 

Maybe I'm misunderstanding what you're trying to do, but if you have a folder in your classpath, that means all the files underneath it should be in the classpath as well. If not, you can always pass each .properties file on the class path.

But either way, since the file/folder that contains the file is in the classpath, you should just be able to do:

InputStream in = new FileInputStream("classpath:xyz.properties")

And since "foo/bar/plugh" is in the classpath, one of the places it will look for xyz.properties is in "foo/bar/plugh".

Alex Beardsley
For some reason this isn't working for me when my app runs via a batch file build by codehaus maven appassmebler. Absolute paths work but relative ones don't.
sal
The only thing I can think of is if the relative path you have in your classpath is being resolved based on where the program is run. For example if I have the batch file in the C:\myapp\bin directory, the "base" path might be C:\myapp\bin, not C:\myapp. If that is the case, it would be trying to resolve "C:\myapp\bin\foo\bar\plugh\xyz.properties".
Alex Beardsley
It worked for me with the absolute path of the directory. But it is very strange because I tried before with the code:<code>InputStream in = getClassLoader().getResourceAsStream("xyzzy.properties");</code>What is the difference between these two methods?Thanks.
David García González
Is there any way to get this properties with the method:ResourceBundle.getBundle("xyz");Thanks.
David García González
@David I think as long as "xyz.properties" is in your classpath, it should get picked up with getBundle()
Alex Beardsley
@Nalandial looks like the the base directory was not what I expected it to be. Problem solved
sal