JKing
14 years agoOccasional Contributor
%~dp0 doesn't work on Win 7 N 64-bit
I discovered that there is a bug in Windows apparently (Win 7 N 64-bit at least) that prevents the soap ui launcher from working. It gives an error about ClassNotFound and bombs at start up.
The support folks said to use the bundled 32-bit version instead, which I did, and that's where I saw the problem.
After some digging and experimentation, I discovered that the old batch file trick for getting the current path as a string (%~dp0) apparently does not work, so the paths get hosed and it can't find the jre/jdk.
Switching to back the 64-bit version, and ensuring that my JAVA_HOME was set correctly, seems to have cleared the problem. I found no posts here or on google about it, so maybe it's something particular to Win 7 N 64-bit, my particular VM, etc. But wanted to post in case it could save others some suffering.
The support folks said to use the bundled 32-bit version instead, which I did, and that's where I saw the problem.
After some digging and experimentation, I discovered that the old batch file trick for getting the current path as a string (%~dp0) apparently does not work, so the paths get hosed and it can't find the jre/jdk.
Switching to back the 64-bit version, and ensuring that my JAVA_HOME was set correctly, seems to have cleared the problem. I found no posts here or on google about it, so maybe it's something particular to Win 7 N 64-bit, my particular VM, etc. But wanted to post in case it could save others some suffering.