Calling getResourceAsStream to locate property files

Question

I'm attempting to create a link between Oracle and an external application using an API provided by the vendor.
This APi has a number of settings that I'd rather keep as properties so I don't have to compile custom code for dev / test / prod.
I'm attempting to use the getResourceAsStream function locate the prop file. It works fine as a stand alone - but when I run it out of OJVM - can't locate the prop file.
Load Java shows the prop file in my user_objects list - I just can't seem to get OJVM to let my code know where it is.
Here's part of the constructor of the class doing the heavy lifting:
Properties settings = new Properties(default);
try {
InputStream sf = this.getClass().getResourceAsStream("ll_util.properties");
settings.load(sf);
Any help appreciated!

Answer 1

Hi Guys,
I am trying to connect to mysql/oracle database using property file "jdbc.properties" to provide information like driver, url, user name, password etc
When i put this file within the same package ( com.db in this case ) : I can successfully connect to the database ,
But when I put this file somewhere else say C:\resources\jdbc.properties I could not locate the property file
I am using following line of code
When property file withing the same directory as Class
InputStream in = QueryTest.class.getResourceAsStream("jdbc.properties");
Works
So what's your problem?
But
When property file is at C:/resources/ folder
Why would you want to put it here?
InputStream in = QueryTest.class.getResourceAsStream(PATH);
getting null value in InputStream object 'in'
I think i am not correctly putting the PATH. Can anybody help me with the Java way of putting the PATH to locate
resource file at C:/resources/ folder
Thanks in Advance :)
You haven't mentioned whether you are using named packages or the default, unnamed one.
The getClass().getResourceAsStream(propfile) method of java searches all files in the current directory as well as the jar file in which the class file resides.Presumable C:\resources doesn't fit in the first category (it obviously doen't fit in the second).
In any event, since properties files usually contain the initial configurations for an application, they are essential to the app and should be loaded in the jar, along with the class files, unless there are other compelling reasons.