Hi, well said. To solution could be to have the JNLP file generated by a jsp, but is this an acceptable solution ? I think yes, so this week i could start to work on it.
Tell me if not. Otherwise we could publish a jnlp with an absolute URL, pointing for example to jars in the web site, but could not be the best. This could be useful in other situations, for example I was thinking to create a jnlp extension file (callable from an application jnlp file) that we could distribute for example as standalone jnlp inside our binary and source distributions, so then users could load pivot jars directly from the site, but again I don't know if this is wanted. Probably we need some discussion on this. Bye, Sandro
