Browse Prior Art Database

Method and System of integrating Launch In Context with Desktop Integrated Java Web Start Applications

IP.com Disclosure Number: IPCOM000183402D
Original Publication Date: 2009-May-21
Included in the Prior Art Database: 2009-May-21
Document File: 3 page(s) / 34K

Publishing Venue

IBM

Abstract

The core idea of this disclosure lies around identifying the mode in which the application is launched and performing the required operation based on this mode. The mode could be either normal launch (which could be launch in context) or could be launch through the desktop integration feature. The mode can be identified by associating unique identifiers for the context parameters passed through the JNLP. These identifiers can be generated dynamically .i.e. GUID?s or can be configured based on things like the user id or the session etc. Using these unique identifiers as reference points it will be possible to identify specific parameters for which the values have changed or parameters for which the values have not changed and perform the required actions based on the needs of the application.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 55% of the total text.

Page 1 of 3

Method and System of integrating Launch In Context with Desktop Integrated Java Web Start Applications

     Java Web Start caches the application locally on the system and allows the user to perform some set of operation and also pass the arguments to the application while launching it. Since all the required resources are stored locally on the system, subsequent launches will be instantaneous. This feature is called the Desktop Integration where the Web Start application is integrated with the user's desktop and the user will be able to use the application directly without actually going through the Web Page.

       Users/Application vendors can provide arguments to the Java Web Start Launcher by adding

element to the JNLP descriptor file. The parameter passed in like this would be used by the launcher every time the application is launched. If the requirement is to use Java Web Start for Launch in Context (Launch by passing runtime parameters based on the user's selection in another application) with desktop integration then this feature becomes a problem since you would not want to have the parameters passed to be used for every launch since the parameter would be specific to the current context. And when the Java Web Start Application is launched through the desktop integration feature it would be required to use the default/desktop context to launch the application. This is a huge limitation while using the Java Web Start technology for deployment as well as launching with context and desktop integration cannot be provided in this case.

A desktop integrated Java Web Start application can be launched in two modes:
1) Web Launch - For the first time the application is downloaded and installed/cached. This generally uses "launch in context" .i.e. with parameters that advice the application to perform certain operations while launching. It could also contain parameters/arguments that are directives to the install/launch program too.
2) Desktop integration - This is generally without any launch in context and would generally just contain regular arguments.

     The arguments that are passed for launch in context would be specific for that particular launch of the application and should not be used for subsequent launches. But since the JNLP file used for launch through desktop integration is the same as that used during the last Web launch, it becomes important to be able to ignore launch in context parameters that have been used earlier. As mentioned earlier the basic idea here is to tag launch in context arguments with unique identifiers that would allow us to identify arguments that are part of the launch in context set and among them the ones that have already been used earlier.

     When the application is launched through Web Launch the arguments of the application are checked and if it contains any launch in context (context sensitive) parameters it is asso...