Browse Prior Art Database

Wrapper for the Java Application Launcher for the windows

IP.com Disclosure Number: IPCOM000012393D
Publication Date: 2003-May-04
Document File: 7 page(s) / 385K

Publishing Venue

The IP.com Prior Art Database

Abstract

Applications written in Java are launched using the "Java" tool. It does so by starting the Java Runtime Environment, loading the specified class and then invoking that class's main method. The java tool must be initiated in a command line interface shell. Here mypackage.Main is the class that contains the main method that needs to be invoked. The java runtime searches for the "mypackage.Main" class in three sets of locations, the bootstrap class path, the installed extensions, and the user class path. Developers normally use the user class path to specify the location from where the main class and the associated classes have to be loaded. Every time a new session of the command line interpreter is started, the above process must be repeated. An alternative would be to write a dos based script to perform the above operations. The user then would launch the application by double clicking on the batch file. This however is not consistent with the way windows applications are launched. The invention describes an application that hides the complexities involved in launching a java application from the user, and provides a consistent launch mechanism as that of any standard windows application.

This text was extracted from a Microsoft Word document.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 24% of the total text.

FIELD OF TECHNOLOGY:(e.g., CT, MR, Ultrasound, X-Ray)

Java Software Applications.

INVENTION TITLE:Provide a unique, descriptive title.� If you write this disclosure in a language other than English, please provide a title in English as well.� Si vous rédigez en français, merci de proposer un titre en anglais et un titre en français.

Wrapper for the Java Application Launcher for the windows

PROBLEM/BACKGROUND:Describe how the invention works and how it solves the problem posed above.�

Applications written in Java are launched using the “Java” tool. It does so by starting the Java Runtime Environment, loading the specified class and then invoking that class’s main method. The java tool must be initiated in a command line interface shell as shown below:

Here mypackage.Main is the class that contains the main method that needs to be invoked. The java runtime searches for the “mypackage.Main” class in three sets of locations, the bootstrap class path, the installed extensions, and the user class path. Developers normally use the user class path to specify the location from where the main class and the associated classes have to be loaded. This is specified as sown below:

where “main.jar” is the jar file that contains the main class.

Every time a new session of the command line interpreter is started, the above process must be repeated. An alternative would be to write a dos based script to perform the above operations. The user then would launch the application by double clicking on the batch file. This however is not consistent with the way windows applications are launched.

The invention describes an application that hides the complexities involved in launching a java application from the user, and provides a consistent launch mechanism as that of any standard windows application.

INVENTION DESCRIPTION:Describe how the invention works and how it solves the problem posed above.�

The application uses a set of configuration files to provide for one time configuration of the settings that are required before the main java application is launched. The files used are “launcher.cfg”, “classpath.cfg”, “path.cfg”, “system.cfg” and “apps.cfg”. Also used are two batch file “start.bat” and “end.bat” to provide for dos based scripting.� The “start.bat” is used before the java application is launched; the “end.bat” is used just before the launcher terminates. The launcher also provides for restart mechanism through the use of “launcher.tmp” file.

Shown below is a flowchart that describes the usage of these files.

The contents of each of the files are described below.

 

Launcher.cfg

This files defines the executable that needs to be run (java/javaw in case of java applications) along with its launch time settings and the command line parameters. Shown below is the content of a sample “launcher.cfg” file:

#------------------------------------------------------BEGIN-------------------------------...