Registration method for supporting bytecode modification

Abstract

A method is described that comprises receiving from a classfile registration information. The registration information comprises a class name and a different method name for each of the class's methods. Each of the methods are modified with at least one additional byte code instruction to cause, for its respective method, a plug-in module's handler method to provide output function treatment for the respective method. Also, a plug-in pattern is referred to in order to determine which of a plurality of plug-in modules are appropriate for each of the class's methods. The plug-in pattern lists for each of the plug-in modules those of the methods that are to be handled with its corresponding output function treatment.

Description

PRIORITY[0001]Application claims priority to U.S. patent application Ser. No. 10 / 749,686, titled “Registration Method For Supporting Bytecode Modification”, filed Dec. 30, 2003, now U.S. Pat. No. 7,743,367.BACKGROUND[0002]1. Field of the Invention[0003]The field of invention relates generally to the software arts; and, more specifically, to a registration method for supporting bytecode modification.[0004]2. Description of the Related ArtBytecode[0005]Certain software technologies, such a Java, emphasize the use of a special interpreter (which may also be referred to as a “virtual machine”) that allows generic processor instructions to be executed on a particular type of processor. Here, each hardware platform (e.g., each computer) that the generic instructions are expected to “run on” typically includes a virtual machine that is responsible for converting the generic processor instructions (which are typically referred to as “bytecode”) into instructions that are specially targeted ...

AI Technical Summary

Benefits of technology

[0024]This separation of logic components and the user interface provides a more flexible and scalable architecture compared to that provided by the two-tier model. For example, the separation ensures that all clients 230 share a single implementation of business logic 244. If business rules change, changing the current implementation of business logic 244 to a new version may not require updating any client-side program code. In addition, presentation logic 242 may be provided which generates code for a variety of different user interfaces 240, which may be standard browsers such as Internet Explorer® or Netscape Navigator®.

Problems solved by technology

The limitations of the two-tiered architecture illustrated in FIG. 2a become apparent when employed within a large enterprise.

For example, installing and maintaining up-to-date client-side applications on a large number of different clients is a difficult task, even with the aid of automated administration tools.

Moreover, a tight coupling of business logic, presentation logic and the user interface logic makes the client-side code very brittle.

Changing the client-side user interface of such applications is extremely hard without breaking the business logic, and vice versa.

This problem is aggravated by the fact that, in a dynamic enterprise environment, the business logic may be changed frequently in response to changing business rules.

Accordingly, the two-tiered architecture is an inefficient solution for enterprise systems.

Although the multi-tiered system illustrated in FIG. 2b provides a more flexible and scalable architecture, it also results in significant additional complexity.

For example, monitoring, testing and / or debugging multiple clusters of presentation layer servers, business layer servers and databases, and the dependencies between them requires a significant amount of management overhead.

Images