[thredds] Calling ToolsUI webstart application

Hi Nathan:

We have changed the way applications like Hyrax can call the ToolsUI webstart application, in order to insulate from changes in the webstart jnlp file.

We are using IDV style JNLP files, and using a "current" directory that we can switch when needed without breaking other applications.

Details are here:


This can be used now, let me know if you see any problems.

Thanks for the suggestion!


On 3/15/2012 1:04 PM, Nathan Potter wrote:


I have some questions regarding the way that IDV and ToolsUI are deployed via webstart. I 
have been caching the prototype .jnlp files in my distribution and modifying the 
arguments as needed on a per request basis. This implementation lacks flexibility when 
the application host site upgrades to a newer version (and removes the older one). I see 
that on motherlode the IDV jnlp bundle now references a "current" version of 
the codebase (http://www.unidata.ucar.edu/software/idv/current/webstart)  and that the 
resources (jar files) are loaded based on content held at the application site:

This seem like a much more flexible plan. Is it something that will also be 
done for NetCDF-ToolsUI?

Alternatively, someone pointed me at the way that AutoPlot handles it's jnlp 
generation. They host the application files and a cgi that you pass the 
arguments to as part of the query string, it hands back a JNLP with the 
arguments filled out and pointing to their most recent version  of the AutoPlot 


Any thoughts about this?



= = =
Nathan Potter                        ndp at opendap.org
OPeNDAP, Inc.                        +1.541.231.3317

thredds mailing list
For list information or to unsubscribe,  visit: 

  • 2012 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the thredds archives: