I assume the problem is comming up with a URL that is compatible with the "internal references" of the jar. What's the best way (or working way even!) of obtaining the path to files within the jar ? Thanks in advance

J2EE Web Developer

John Luckcuck
Greenhorn

Joined: Apr 18, 2002
Posts: 7

posted Apr 18, 2002 03:59:00

0

I've resolved this issue by using : URL url = this.getClass().getResource("/config/fbn.props"); properties.load(url.openStream()); But maybe using a properties file was a little OTT in the first place :roll:

That's the way to do it -- the URL you get back will have the jar: pseudo-protocol and cannot be converted into a File. Using getResourceAsStream can simplify your code slightly. - Peter

John Luckcuck
Greenhorn

Joined: Apr 18, 2002
Posts: 7

posted Apr 18, 2002 06:57:00

0

Cheers Peter, I've decided to stick with my properties file and leave it outside the jar (which is sensible) to allow users to pre-configure their client / server without having to specify command line parameters. Of course, I wont be ignoring the command line parameters, the properties file will merely define my defaults. Any extra command line parameters will overwrite those used in the properties file.