Originally posted by Cristian Negresco:
Hello,
You need to offer different dynamically created jnlp files to different users.
Thanks for the suggestion.
I think that is probably the way to go, but it isn't quite perfect with the
java 1.4 version of webstart.
Ignoring authenticaion for the moment, I made a simple
jsp page called "test.jnlp" that looks something like this:
(Most of the jnlp omitted for clarity)
For those who don't read jsp files, what this does is generate a separate jnlp file depending on whether you access it as "test.jsp?size=1" or "test.jsp?size=2". In each case, the href parameter is set to refer back to the same dynamically-generated jnlp file.
This works perfectly on the version of webstart that comes with JDK1.5 (tested on Windows).
But on JDK1.4 (tested on Linux), the web-start application manager still considers "test.jsp?size=1" and "test.jsp?size=2" to be two separate applications, so for JDK1.4 there is no improvement using dynamic generation of jnlp relative to our old version of using separate jnlp files like "test_1.jnlp" and 'test_2.jnlp".
We could omit the href="..." portion of the dynamic jnlp file. (It is optional.) But then our application doesn't show-up in the javaws application manager at all, the user can't create a shortcut to the application, and no dynamic-updating is done, and we don't want that to lose those features.
So, if I knew that all the customers were using JDK1.5, then I would update to this system. But until then, I think I will stick to the ugly old method with 5 separate jnlp files.
Unless, of course, anyone has any better suggestions....
Thanks.