javaws CLI with Icedtea-web

[Chris Lee]

On Jun 30, 2014, at 6:17 PM, Jacob Wisor wrote:

> 
> When setting JRE properties you should not have any proxy properties set in deployment.properties, or you should set proxy settings to DIRECT for JRE's properties to take effect. As Jiri mentioned, property setting and property sharing has not been well tested in IcedTea-Web, so this is me just giving some hints on how you could perhaps workaround this problem.
> 
> Updating to IcedTea-Web 1.5 will not give you much either because - to my knowledge - code concerning this issue has not been touched.

Tthe deployment.propeties file there, but completely empty. I tried using :

"javaws -verbose -J-Dhttp.proxyHost=atlasgw-exp.cern.ch -J-Dhttp.proxyPort=3128 http://dipbrowser.web.cern.ch/dipbrowser/launch.jnlp" 

but, thisgives the same result as before, and it does appear that the settings are direct from the output. ie: 

Selecting proxy for: http://dipbrowser.web.cern.ch/dipbrowser/launch.jnlp
Browser proxy option "4" (Automatic) not supported yet.
Browser selected proxies: [DIRECT]
Selected proxies: [DIRECT]
Selecting proxy for: socket://dipbrowser.web.cern.ch:80

I also tried supplying the application with a different file using -J-Ddeployment.system.config, though that doesn't seem to work either?

> 
> To be honest, I am a little bit baffled that you're relying on web or intranet based JNLP applications to record (highly) valuable experiment data at all. The only possible scenario that I could think of where this would make any sense is to just install some java application locally via JNLP. But, the install feature of JNLP is not supported by IcedTea-Web yet. So, at this point I am a little bit confused about your intent.

We don't use this for any data taking. The application itself is external to our detector which is for all intents and purposes, is cut off from the outside world. The application provides values to certain parameters, which internal operations managers can use to verify externally supplied parameters.  ie: CERN states that water temperature at point A is X degrees. During full operations runs, software updates within the experiment are locked down, and it wouldn't always be possible to update, Oracle JDK as was required with JAVA 7 update 25 for example. 

Though the reason that everything else is usually disabled, is the reason why I was hoping to use a CLI command for this one application instead of changing all the global settings.
> 
> Jacob