Browse Prior Art Database

Runtime Class Finder

IP.com Disclosure Number: IPCOM000027886D
Original Publication Date: 2004-Apr-09
Included in the Prior Art Database: 2004-Apr-09
Document File: 1 page(s) / 31K

Publishing Venue

IBM

Abstract

The proposed system aims to make development of Java applications easier so developers can overcome NoClassDefFound errors with the help of tooling.

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

Page 1 of 1

Runtime Class Finder

The proposed system aims to make development of Java* applications easier so developers can overcome NoClassDefFound errors with the help of tooling. When developing Java applications, it is common to receive NoClassDefFound runtime errors when a auxiliary class that is needed by a Java application is not found. The proposed system aims to make development of Java applications easier so developers can overcome such NoClassDefFound errors with the help of tooling.

The systems will have a code inspection daemon run in the background of a Java application that is executed within an integrated development environment (IDE). This tool will help programmers find the necessary auxiliary helper Java Application Archives (JARs) that are needed to run the Java application successfully.

When a NoClassDefFound runtime error occurs, the code inspection Daemon will take note of what class could not be found. At this point, a tool such as AlphaWorks's JAR Classfinder could be presented to the user (see http://www.alphaworks.ibm.com/tech/jarclassfinder).

Using the tool, the class path of the application can be modified by a plugin. Since JAR Classfinder takes a while to search for a given class, the plugin can be modified to use a small footprint database to store information about what classes are found in JARs. Accordingly, the process of locating a given class can be expedited.

The system might best be described with a series of events that take place:
1)...