Java Jar file: use resource errors: URI is not hierarchical Java Jar file: use resource errors: URI is not hierarchical java java

Java Jar file: use resource errors: URI is not hierarchical


You cannot do this

File src = new File(resourceUrl.toURI()); //ERROR HERE

it is not a file!When you run from the ide you don't have any error, because you don't run a jar file. In the IDE classes and resources are extracted on the file system.

But you can open an InputStream in this way:

InputStream in = Model.class.getClassLoader().getResourceAsStream("/data.sav");

Remove "/resource". Generally the IDEs separates on file system classes and resources. But when the jar is created they are put all together. So the folder level "/resource" is used only for classes and resources separation.

When you get a resource from classloader you have to specify the path that the resource has inside the jar, that is the real package hierarchy.


If for some reason you really need to create a java.io.File object to point to a resource inside of a Jar file, the answer is here: https://stackoverflow.com/a/27149287/155167

File f = new File(getClass().getResource("/MyResource").toExternalForm());


Here is a solution for Eclipse RCP / Plugin developers:

Bundle bundle = Platform.getBundle("resource_from_some_plugin");URL fileURL = bundle.getEntry("files/test.txt");File file = null;try {   URL resolvedFileURL = FileLocator.toFileURL(fileURL);   // We need to use the 3-arg constructor of URI in order to properly escape file system chars   URI resolvedURI = new URI(resolvedFileURL.getProtocol(), resolvedFileURL.getPath(), null);   File file = new File(resolvedURI);} catch (URISyntaxException e1) {    e1.printStackTrace();} catch (IOException e1) {    e1.printStackTrace();}

It's very important to use FileLocator.toFileURL(fileURL) rather than resolve(fileURL), cause when the plugin is packed into a jar this will cause Eclipse to create an unpacked version in a temporary location so that the object can be accessed using File. For instance, I guess Lars Vogel has an error in his article - http://blog.vogella.com/2010/07/06/reading-resources-from-plugin/