I don't think we can't do that if we want to use the new features of webstart 1.5. To use those features I think the "spec" attribute in the jnlp has to be set to 1.5 which will make the jnlp file itself not load in 1.4.
Did you see the jira issue on this? http://www.telscenter.org/jira/browse/OWL-270 Scott Stephen Bannasch wrote: > How about delivering a jnlp that can startup on 1.4 but checks for > 1.5 at startup. Perhaps something like this: > > The initial code displays a startup screen and checks for 1.5 and > displays a warning and upgrade instructions if 1.5 is not installed. > Make all the jar resources that are not needed for this functionality > use lazier loading so that the splash and warning appear quickly even > when starting with an empty webstart cache. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
