I’ve helped a few colleagues who have had the problem that nothing happens when they try to launch SAB/RAB/DAB from their menu, icon, or whatever calls the *-app-builder.jar file. A tool that has fixed this issue of a computer not recognizing what to do with a .jar file (or doing the wrong thing with a .jar file) is a utility called jarfix.exe published as freeware by Johann Johann Löfflman. As his webpage describes,
“on Windows any program can steal a file type at any time even if it is already associated with a program. Many zip/unzip programs prefer to do this, because a jar is stored in the .zip format. If you doubleclick on a .jar, your pack program opens the file, rather than javaw runs the program, because your pack program ignores the meta information which are also stored in a .jar
You can fix this problem very easy with the small but reliable jarfix.exe program. Just doubleclick on it to restore the .jar association with javaw.exe.”
I’ve seen this problem more than a few times; every time we have an app-builder workshop (which usually include 15-20 participants) we seem to have one or two people whose machines can’t open .jar files correctly. Repairing the file association with this tool has solved the problem a lot of the time, so I wanted to document it here and suggest that it might be good to even include this in the troubleshooting section of the installation instructions.