Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve robustness of OME Web Start launcher #18

Open
ctrueden opened this issue Jan 9, 2014 · 0 comments
Open

Improve robustness of OME Web Start launcher #18

ctrueden opened this issue Jan 9, 2014 · 0 comments

Comments

@ctrueden
Copy link
Member

ctrueden commented Jan 9, 2014

To launch VisBio from the OME web interface via Java Web Start, OME generates a JNLP document on the fly. This document contains the list of JARs necessary for VisBio to launch. But whenever the list changes, OME loses the ability to launch VisBio properly (it generates JNLP documents with an old list of JARs).

The following changes will eliminate this problem:

  1. Starting with next version of OME 2.6, bundle a stable version of VisBio that will always work with that version of OME. Provide an option in the OME installer to switch between using the bundled VisBio version (served via HTTP from the local OME server), or the latest version available (served from LOCI's web site).
  2. Introduce a JNLP template on the LOCI web site that the OME installation can access, which indicates the proper form the JNLP document should take in order to successfully launch the latest version of VisBio.

Migrated-From: http://dev.loci.wisc.edu/trac/software/ticket/75

@ghost ghost assigned ctrueden Jan 9, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant