Abstract: Optimizing an application to reduce local memory usage. At least one executable class file of the application can be instrumented with analysis code, the executable class file including bytecode. The class file can be executed on a virtual machine, wherein during execution the analysis code generates data related to the application's use of local memory. The data related to the application's use of the local memory can be analyzed to generate a memory profile analysis. Based on the memory profile analysis, at least one portion of the bytecode can be automatically revised to reduce an amount of the local memory used by the application.

Abstract: A method of optimizing an application to reduce local memory usage. The method can include instrumenting at least one executable class file of the application with analysis code, the executable class file including bytecode. The method also can include executing the class file on a virtual machine, wherein during execution the analysis code generates data related to the application's use of local memory. The method further can include, via a processor, analyzing the data related to the application's use of the local memory to generate a memory profile analysis. The method further can include, based on the memory profile analysis, automatically revising at least one portion of the bytecode to reduce an amount of the local memory used by the application.

Abstract: A method of optimizing an application to reduce local memory usage. The method can include instrumenting at least one executable class file of the application with analysis code, the executable class file including bytecode. The method also can include executing the class file on a virtual machine, wherein during execution the analysis code generates data related to the application's use of local memory. The method further can include, via a processor, analyzing the data related to the application's use of the local memory to generate a memory profile analysis. The method further can include, based on the memory profile analysis, automatically revising at least one portion of the bytecode to reduce an amount of the local memory used by the application.

Abstract: A method and apparatus for providing a pluggable and extendable J2EE architecture are provided. The method and apparatus provide mechanisms for defining extension points within modules of the J2EE application and mechanisms for defining plug-in or extension modules that may be integrated into the J2EE application via these extension points. In addition, a mechanism for merging the plug-in or extension modules into the J2EE application at deployment is provided such that all of the information necessary for generating instantiations of the plug-in or extension modules is integrated into the J2EE application configuration files. As a result, an integrated J2EE application is made possible from a modularized and extendable development of the J2EE application.

Abstract: System, method and computer program product for monitoring the status of components in a data processing system that improves the accessibility of JMX monitoring information in web content. The system includes a mechanism for acquiring a text representation of component status for display as ALT and TITLE content associated with each status image. Because the component status is displayed in a manner that is indistinguishable from ALT/TITLE text that has already been statically included in an image attribute, user experience is improved for users with and without accessibility needs.

Abstract: A method, system and computer program product are provided to allow the status of components obtained through JMX queries to be loaded asynchronously in web content such that the status value of each component is displayed as soon as it becomes available, without having to wait for the completion of any other query.

Abstract: Method, system and computer program product are provided to increase the efficiency of the development of Java Enterprise Edition (J2EE) applications. A project may be divided into modules which may be developed by independent teams. The files within each module are classified as independent of resources in other modules or dependent. Independent files may be packaged into a single, integrated web application archive (WAR) file without further processing. Corresponding dependent files are compared and any conflicts are resolved. The resulting files may then be packaged into the WAR file.