Databases
StackOverflow2013
Postsdbo
PORecursive method works while debugging, but get's stuck when running from a JAR
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORecursive method works while debugging, but get's stuck when running from a JAR
    primarykey
    data
    text
    <p>I have the following methods for recursively retrieving images from a folder:</p> <pre><code>private Collection&lt;Image&gt; GetImages(File file) { Collection&lt;Image&gt; result = new LinkedList&lt;Image&gt;(); if (file.isFile()) { result.add(new Image(file)); return result; } for (File f : file.listFiles(new DirAndImagesFilter())) { if (f.isDirectory()) { { result.addAll(GetImages(f)); } } else { result.add(new Image(f)); } } return result; } </code></pre> <p>and here is DirAndImageFilter code:</p> <pre><code>public class DirAndImagesFilter implements FileFilter { private final static String jpeg = "jpeg"; private final static String jpg = "jpg"; private final static String gif = "gif"; private final static String tiff = "tiff"; private final static String tif = "tif"; private final static String png = "png"; public boolean accept(File file) { if (file.isDirectory()) { return true; } String extension = getExtension(file); if (extension != null) { if (extension.equals(tiff) || extension.equals(tif) || extension.equals(gif) || extension.equals(jpeg) || extension.equals(jpg) || extension.equals(png)) { return true; } else { return false; } } return false; } /* * Get the extension of a file. */ static String getExtension(File f) { String ext = null; String s = f.getName(); int i = s.lastIndexOf('.'); if (i &gt; 0 &amp;&amp; i &lt; s.length() - 1) { ext = s.substring(i + 1).toLowerCase(); } return ext; } </code></pre> <p>}</p> <p>When I am running my application from Netbeans it works fine, but when I run JAR file (which is also generated by Netbeans). My application gets stuck in this method.</p> <p>To my understanding JAR file should behave absolutely the same way as the application running in Netbeans. Or am I missing something here?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USVitalij
    1. USVitalij
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COYou're right that being in a jar should have no impact on the logic. I suspect the difference you're seeing is due to a different working directory being set when you run via the IDE vs running the jar. Can you post the implementation of DirAndImagesFilter? Additionally, you should be using file.list(new DirAndImagesFilter()) since listFiles will only return the files and not the directories.
      singulars
      1. PORecursive method works while debugging, but get's stuck when running from a JAR
      1. USChris
    2. COdid you print System.getProperty("user.dir"); Both times and see what directory youre working on?
      singulars
      1. PORecursive method works while debugging, but get's stuck when running from a JAR
      1. USoguzalb
    3. CO@Chris you are right about file.list. However the strange thing that listFiles was listing both files and folders for me!
      singulars
      1. PORecursive method works while debugging, but get's stuck when running from a JAR
      1. USVitalij
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload