Posted by scwells72
on July 25, 2007 at 1:39 PM PDT
We've been using Web Start to deliver our application for quite a while now, but always on a 1.5 JRE. Now we want to support folks who have a 1.6 JRE, but we still need to run in a 1.5 JRE. That's easy to specify in the JNLP file, but we're running into an issue. When the browser requests the JNLP file from our site, the user is authenticated and we place the current session ID into the JNLP file as a command-line argument so that we can RPC (using Spring remoting over HTTP) back to the server. Again, this has always worked fine.
However, now that I'm trying to have Web Start 1.6 hand off to a 1.5 JRE, I'm running into an issue. The issue comes about because there's one request for the JNLP file by the browser using the proper session cookie, but then there are additional (three, actually?!) requests by 1.6 Web Start before the application actually launches, and in the process of those additional requests, the session ID is lost because the requests are coming from another process/user agent, namely 1.6 Web Start.
Does anyone know why these additional requests are being made and whether I can configure something--through JNLP and/or the JnlpDownloadServlet in web.xml--to ensure that the version of the JNLP file downloaded by the browser will be the version that is used to launch the actual application?
Thanks in advance,