International Business Machines Corporation

Matthew Alexander Webster

Fraser P Bohm

Andrew Simon Clement

Andrew Dean Wharmby

Edward J Slattery

John Simon Tilling

Matthew P Chapman

Stephen P Bolton

Richard Kenneth McGuire

Sian Suzanne January

Ian J Mitchell

Philip Ivor Wakelin

Robert Francis Berry

Joseph R Winchester

Benjamin D Cox

Ivan D Hargreaves

David E Knibb

Nicholas Harry Huismans

Winchester R Joseph

Philipp Breitbach

Jonathan James Davies

Helen L Beeken

Helen Louise Hawkins

Operating an online transaction processing system to perform an application including a first module call by performing the following steps (not necessarily in the following order): (i) assigning a dedicated search path to the application, where the search path specifies an ordered set of location(s) for searching for module code, the set of location(s) includes at least a first dynamic module library and the first dynamic module library is ahead of any other locations which may be included in the dedicated search path; (ii) running the application through the transaction processing system; (iii) receiving the first module call, from the running of the application, specifying a requested module using a requested module name; and (iv) in response to the module call, locating the requested module based on the requested module name and the dedicated search path.

Application multi-versioning in a traditional language environment

A method and system are provided for aspect scoping in a modularity runtime. The method includes declaring a set of aspects of a bundle as public aspects in a first aspect configuration file, and filtering the aspect configuration files imported by a bundle to the files from bundles on which the importing bundle has a dependency. The method includes declaring a set of aspects of a bundle as private aspects in a second aspect configuration file. At weaving of aspects at a bundle, the weaving includes: any aspects defined as private aspects; any aspects defined as public aspects; any imported aspects; and any first configuration files from exporting bundles are declared.

Aspect scoping in a modularity runtime

A method is provided for operating a program code object in conjunction with an application context in an application server environment. The method includes identifying a program code object in the application server environment and identifying an application context enabling the provision of a service. The application context is not directly accessible by the program code object. An entry point of the program code object is identified and a tag identifier referencing the application context is associated with the entry point. When executing the program code object in the application server environment, the tag identifier is used to access the application context.

Operating a program code object in conjunction with an application context

Methods and systems of generating product configuration files may involve receiving an identification of a set of features for a software product via a file editor interface. The lowest version of the software product that supports the set of features may be determined, wherein a configuration file can be generated based on the lowest version. In one example, the configuration file identifies the set of features and includes the lowest version as an attribute of the configuration file.

Automatic selection of lowest configuration feature level by functionality exploited

A bundle entering a set of starting and active bundles within a bundle framework is detected by a controller bundle executed by a processor. A determination is made as to whether a manifest of the bundle includes an extension header that identifies at least one legacy application. In response to determining that the manifest of the bundle includes the extension header that identifies the at least one legacy application, at least one application proxy object is created for at least one defined entry point class of the at least one legacy application identified by the extension header. The created at least one application proxy object is registered as a service within a service registry of the bundle framework.

Legacy application integration within a bundle framework

A method of operating a data processing system comprises running a source code editor, displaying source code in a graphical interface of the source code editor, and displaying a summary box, the summary box comprising a list of one or more aspects affecting the source code. The system is configured so that on receipt of a user input corresponding to an aspect listed in the summary box there is displayed one or more cross-reference markers of the selected aspect in the graphical interface of the source code editor.

Method of operating a data processing system

Operating an integrated development environment in a data processing system comprising running a source code editor, displaying source code in a graphical interface of the source code editor, displaying at least one cross-reference marker, the at least one cross-reference marker indicating crosscutting in the source code, receiving an input, changing one or more cross-reference markers, and highlighting the one or more changed cross-reference marker.

Depicting changes to structures in an integrated development environment

A method of obtaining trace data with respect to a running software program includes accessing a method in a call stack, the call stack including a sequentially ordered list of methods called during the running of the software program. If the accessed method in the call stack falls between a minimum trace offset and a maximum trace offset where the minimum trace offset and the maximum trace offset define a trace window, obtaining trace data for the method and outputting it to an output stream which is then collected into a trace data storage. If the trace data in the trace data storage meets predetermined adaptation rules then changing the position in the call stack of at least one of the minimum trace offset and the maximum trace offset.

Method, system and computer program product for tracing software methods

Provided is a JIT compiler that changes the status of run-time determined software routines between being activated and deactivated in an application program. Conditional statements which are used at run-time to determine whether such a routine has been activated or deactivated are presented as discrete conditions that always evaluate to a known result by using an invariant flag in the compiled bytecode. The JIT compiler optimises an application program by excluding discrete condition checks. Consequently, if the branch of the discrete condition that will never execute includes a run-time determined software routine, then the routine will be excluded from the JIT compilation and will not form part of the JIT compiled native machine code. A run-time class or code replacement facility is used as a means of activating or deactivating a run-time determined software routine at run-time by changing the value of the invariant flag of said routine.

Method and apparatus for activating/deactivating run-time determined software routines in Java compiled bytecode applications

A system is provided which comprises multiple Java virtual machines (VMs). Each VM is capable of running a plurality of threads. The system includes at least one object which is shared between the VMs so that it is accessible from two or more VMs, and at least one non-shared object which is accessible only from a single VM. In order to perform a lock operation on a shared object, it is first detecting that an object is a shared object. In a preferred embodiment, this is accomplished by locating a predefined value in a particular lock data word in the object. In response to the detection, a monitor is used to control local access to the shared object for the thread that is requesting the object. The monitor is on the same VM as the requesting thread. In addition, a data structure, which may be a proxy object, is updated in order to associate the monitor with the shared object.

Object locking in a shared VM environment

A computer system includes multiple class loaders for loading program class files into the system. A constraint checking mechanism is provided wherein a first class file loaded by a first class loader makes a symbolic reference to a second class file loaded by a second class loader, the symbolic reference including a descriptor of a third class file. The constraint mechanism requires that the first and second class files agree on the identity of the third class file and stores a list of constraints as a set of asymmetric relationships between class loaders. Each stored constraint, for a class loader which loaded a class file that contains a symbolic reference to another class file, includes a first parameter denoting the class loader which loaded the class file to which the symbolic references is made; and a second parameter denoting a class file which is identified by a descriptor in said symbolic reference.

System and method for class loader constraint checking

A virtual machine in an object-oriented system includes an interpreter. In order to provide trace information from a program about specific method calls, a user defines a selection of methods to be traced. As the program runs on the interpreter, it is determined, whether or not the method is included within the selection to be traced. For those methods included within the selection, trace information about the method call is outputted. A method block is associated with each method and is used by the interpreter to invoke the method. For each method within the user-defined selection, a flag is set within the method block associated with the method. The status of this flag is checked when the interpreter invokes a method, in order to determine whether or not the method is included within the selection.

Growing community of inventors

Hook, United Kingdom

Matthew Alexander Webster