Abstract: A method for managing authentication of user interface elements in a user interface can be provided. The method can include displaying a plurality of widgets in the web browser and sending an HTTP request for data to a web site, wherein the HTTP request is sent via an XMLHttpRequest API. The method can further include receiving from the web site a 401 HTTP status code associated with a custom “WWW-Authenticate” header value indicating that the HTTP request is unauthorized for communication with the web site and detecting the custom “WWW-Authenticate” header value. The method can further include displaying in a first widget of the plurality of widgets a text field for entering user credentials. The method can further include sending to the web site an HTTP request including the user credentials entered by a user, wherein the HTTP request is sent via the XMLHttpRequest API.

Abstract: Memory management for object oriented applications during run time includes loading an object oriented application into a computer memory. The object oriented application includes a plurality of nodes in a classification tree, the nodes including key value pairs. The nodes are aggregated in the classification tree by a computer. The aggregating includes eliminating redundant keys and creating a composite node. The composite node is loaded into the computer memory. The plurality of nodes in the classification tree are removed from the computer memory in response to loading the composite node into the computer memory.

Abstract: Memory management for object oriented applications during run time includes loading an object oriented application into a computer memory. The object oriented application includes a plurality of nodes in a classification tree, the nodes including key value pairs. The nodes are aggregated in the classification tree by a computer. The aggregating includes eliminating redundant keys and creating a composite node. The composite node is loaded into the computer memory. The plurality of nodes in the classification tree are removed from the computer memory in response to loading the composite node into the computer memory.

Abstract: According to exemplary embodiments, a method is provided for versioning classes in an OSGi-enables J2EE environment. A first version of code is packaged into a first OSGi (Open Service Gateway initiative) bundle, and the first version of code is marked for export. A second version of code is packaged into a second OSGi bundle, and the second version of code is not marked for export. A determination is made whether an application needs the first version of code or the second version of code. If the application needs the first version of code, a classloader hierarchy is constructed using existing classloaders. If the application needs the second version of code, a new classloader is created which is able to load application classes and unversioned application server classes normally, while only loading the correct version of versioned code.

Abstract: A method for managing authentication of user interface elements in a user interface can be provided. The method can include displaying a plurality of widgets in the web browser and sending an HTTP request for data to a web site, wherein the HTTP request is sent via an XMLHttpRequest API. The method can further include receiving from the web site a 401 HTTP status code associated with a custom “WWW-Authenticate” header value indicating that the HTTP request is unauthorized for communication with the web site and detecting the custom “WWW-Authenticate” header value. The method can further include displaying in a first widget of the plurality of widgets a text field for entering user credentials. The method can further include sending to the web site an HTTP request including the user credentials entered by a user, wherein the HTTP request is sent via the XMLHttpRequest API.

Abstract: According to exemplary embodiments, a method is provided for versioning classes in an OSGi-enables J2EE environment. A first version of code is packaged into a first OSGi bundle, and the first version of code is marked for export. A second version of code is packaged into a second OSGi bundle, and the second version of code is not marked for export. A determination is made whether an application needs the first version of code or the second version of code. If the application needs the first version of code, a classloader hierarchy is constructed using existing classloaders. If the application needs the second version of code, a new classloader is created which is able to load application classes and unversioned application server classes normally, while only loading the correct version of versioned code.