java-web-start

To start our legacy application, we use java WebStart via a jnlp. We would like to support 64-bit Java clients but one of our libraries is architecture dependent. We thought of doing something like: <resources> <j2se version="1.6+" sun.arch.data.model="64"/> <jar href="/apps/swt-3.7M5-win32-win32-x86_64_s.jar" download="eager" /> </resources> <resources> <j2se version="1.6+" /> <jar href="/apps/swt-3.7M5-win32-win32-x86_s.jar" download="eager" /> </resources> This is not working because the parameter sun.arch.data.model="64" is used to set the parameter instead of testing on it. Any ideas?

I have a Java Web Start application, which I used to start through a shortcut: "C:\Program Files\Java\jdk1.7.0_67\bin\javaws.exe" -J-Dfile.encoding=UTF-8 -J-Xdebug -J-Xnoagent -J-Xrunjdwp:transport=dt_socket,server=n,suspend=y,address=8200" http://xxx/yyy/zzz.jnlp But after installing JDK 1.8 it all stopped working, my javaws don't see any of additional X||D params. I tried this way: setenv JAVAWS_VM_ARGS "-Dfile.encoding=UTF-8 -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=n,suspend=y,address=8200" "C:\Program Files\Java\jdk1.8.0_25\bin\javaws.exe" http://pont/dms/InstallDMS_debug

Up until recently, I was able to launch/open JNLP files in Firefox using Java web start . Don't know what happened all of a sudden JNLP files stopped launching, a splash screen appears saying Java Starting... and then nothing happens. Even the Java Console in the browser and javacpl.cpl applet doesn't open. Tried all possibilities: removed all older version and installed the latest JRE (java version "1.6.0_17"), still it doesn't work. Done some googling for this problem, people suggested to start javaws.exe with -viewer option but same behavior (a splash screen appears saying "Java Starting...

So I will be using Java Web Start to deploy the java application. When exporting to a Runnable Jar, there are three options in eclipse Helios. Extract required libraries into JAR Package required libraries into JAR Copy required libraries into sub folder next to JAR. What are differences, and how will they affect my .jnlp file? If it's a single jar, isn't it easier because I wouldn't have to write all the different paths to all the libraries it uses? If there are changes in both the library and the application, a single jar would be a better solution? Or would I need <jar href=''> for each

I read on the web that Java version 7u51 (to be released in January 2014) will no longer accept Java Webstart applications that are self-signed by me. Is that true? In case it is true, do I have any chance to build a workaround for my JNLP application, so that I am able to start the application even after January 2014? I have seen that the option to suppress the security warnings because of the usage of a self-signed certificate was removed in 7u40. Matt McHenry Yes, this is true. This blog entry from Oracle has the details. As I understand it, you have three options for continuing to work: