Re: [thredds] Calling ToolsUI webstart application

• To: Nathan Potter <npotter@xxxxxxxxxxx>
• Subject: Re: [thredds] Calling ToolsUI webstart application
• From: John Caron <caron@xxxxxxxxxxxxxxxx>
• Date: Sun, 15 Apr 2012 18:14:09 -0600

apologies:

use netCDFtoolsExtraJars.jnlp

i will correct docs

On 4/15/2012 6:10 PM, Nathan Potter wrote:

John,

I stoked that you're changing this, but I think there may some issues. I tried 
the file as listed here:

http://www.unidata.ucar.edu/projects/THREDDS/tech/tds4.2/reference/Viewers.html#embedding

And I got:

com.sun.deploy.net.FailedDownloadException: Unable to load resource: 
http://www.unidata.ucar.edu/software/netcdf-java/current/webstart/netcdfToolsExtraJars.jnlp
        at 
com.sun.deploy.net.DownloadEngine.actionDownload(DownloadEngine.java:1416)
        at 
com.sun.deploy.net.DownloadEngine.getCacheEntry(DownloadEngine.java:1569)
        at 
com.sun.deploy.net.DownloadEngine.getCacheEntry(DownloadEngine.java:1547)
        at 
com.sun.deploy.net.DownloadEngine.getResourceCacheEntry(DownloadEngine.java:1654)
        at 
com.sun.deploy.net.DownloadEngine.getCachedFile(DownloadEngine.java:661)
        at 
com.sun.javaws.LaunchDownload.downloadExtensionsHelper(LaunchDownload.java:711)
        at 
com.sun.javaws.LaunchDownload.downloadExtensions(LaunchDownload.java:654)
        at com.sun.javaws.Launcher.prepareLaunchFile(Launcher.java:702)
        at com.sun.javaws.Launcher.prepareAllResources(Launcher.java:592)
        at com.sun.javaws.Launcher.prepareToLaunch(Launcher.java:335)
        at com.sun.javaws.Launcher.prepareToLaunch(Launcher.java:207)
        at com.sun.javaws.Launcher.launch(Launcher.java:124)
        at com.sun.javaws.Main.launchApp(Main.java:451)
        at com.sun.javaws.Main.continueInSecureThread(Main.java:283)
        at com.sun.javaws.Main$1.run(Main.java:116)
        at java.lang.Thread.run(Thread.java:680)


Here's my JNLP:

<?xml version="1.0" encoding="utf-8"?>
<jnlp spec="1.0+" 
codebase="http://www.unidata.ucar.edu/software/netcdf-java/current/webstart";>

    <information>
      <title>NetCDF Tools UI</title>
      <vendor>Unidata</vendor>
      <homepage href="http://www.unidata.ucar.edu/software/netcdf-java/"/>
      <description kind="short">GUI interface to netCDF-Java / Common Data 
Model</description>
      <icon href="nc.gif"/>
      <offline-allowed/>
    </information>

    <security>
      <all-permissions/>
    </security>

   <resources>
    <j2se version="1.6+" max-heap-size="1024m"/>
    <jar href="netcdfUI.jar"/>
    <extension name="netcdfUI Extra" href="netcdfToolsExtraJars.jnlp"/>
    </resources>

    <application-desc main-class="ucar.nc2.ui.ToolsUI">
      <argument>{catalogURL}#{datasetID}</argument>
    </application-desc>
</jnlp>



Nathan




On Apr 15, 2012, at 4:58 PM, John Caron wrote:

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:

http://www.unidata.ucar.edu/projects/THREDDS/tech/tds4.2/reference/Viewers.html#embedding

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

Thanks for the suggestion!

John.


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

Greetings

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:
http://www.unidata.ucar.edu/software/idv/current/webstart/IDV/idvbase.jnlp

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 
application.

http://autoplot.org/jnlp.cgi?uri=http://cdaweb.gsfc.nasa.gov/sp_phys/data/fast/acf/1998/fa_k0_acf_19980102_v01.cdf

Any thoughts about this?


Thanks,

Nathan



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




_______________________________________________
thredds mailing list
thredds@xxxxxxxxxxxxxxxx
For list information or to unsubscribe,  visit: 
http://www.unidata.ucar.edu/mailing_lists/

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

• Follow-Ups:
  • Re: [thredds] Calling ToolsUI webstart application
    • From: Nathan Potter

• References:
  • [thredds] NetCDF-ToolsUI, IDV
    • From: Nathan Potter
  • [thredds] Calling ToolsUI webstart application
    • From: John Caron
  • Re: [thredds] Calling ToolsUI webstart application
    • From: Nathan Potter