Abstract: The present invention provides a method, system, and computer program product for providing access to J2EE application servers from non-J2EE application clients. The method comprises: sending data from an application client to a staging area; sending a message from the application client to a J2EE application server, the message notifying the J2EE application server that data is available in the staging area and providing a name of an adapter that can retrieve the data from the staging area; obtaining the adapter using a Message Driven Bean, wherein the Message Driven bean retrieves the data from the staging area using the adapter; and inserting the retrieved data into a database of the J2EE application server using the Message Driven Bean.

Abstract: In accordance with an embodiment of the present invention, a portal environment may include at least one detachable portal page. The portal environment may also include a detach feature or element associated with the at least one detachable portal page. In accordance with another embodiment of the present invention, a method to detach and reattach at least one portal page associated with a portal environment may include detaching a selected portal page in response to activating a detach feature or element. The method may also include reattaching the detached portal page in response to activating a reattach feature or element.

Abstract: A method for increasing server capacity may include causing a program to run in a browser in response to a session on a server. The program may be adapted to spawn a new browser window in response to a web page associated with the session being unloaded. The method may also include destroying all data associated with the session in response to a signal from the spawned browser window. The method may further include returning memory occupied by the data associated with the session to a memory pool.

Abstract: Techniques are disclosed for efficiently updating rendered content (such as content of a Web page) using a “slow-loading” content element, such as a slow-loading image. A reference is embedded within the markup language notation for the content to be rendered, where this reference identifies the source of the slow-loading content element. Delivery of the slow-loading content therefore begins automatically, when the content is rendered. Event handling attributes are specified with the reference, where values of these attributes identify client-side logic to be invoked when the associated event occurs. If the server determines that the rendered content, or some portion thereof, should be asynchronously updated, it abruptly terminates delivery of the slow-loading content. This termination triggers an event handler, which operates to automatically request reloading of the content.

Abstract: A method for maintaining scroll position in a web user interface may include translating a selected scroll position in the web user interface to a pair of scroll coordinates in response to operation of a set scroll position function. The method may also include advancing the web user interface to the selected scroll position in response to each occurrence of an event. The event may include at least one of opening, reloading or refreshing the web user interface or operating a hyperlink in the web user interface.

Abstract: A method to control a portlet associated with a portal page may include deactivating a selected portlet in response to operating a deactivation feature. The method may also include reactivating the selected portlet in response to operating a reactivation feature. The method may also include freezing a portlet content in the selected portlet in response to deactivating the selected portlet. The method may further include disabling hyperlinks, buttons and other inputs to the selected portlet in response to deactivating the selected portlet. The method may further include reconfiguring a portal server to ensure that a portlet content of a selected portlet cannot be affected while the selected portlet is deactivated.

Abstract: A portal environment may include at least one detachable and reattachable portal page. The detachable and reattachable portal page may include a detach feature to detach the portal page from the portal environment. A reattach feature may be provided to reattach a detached portal page to the portal environment. In another embodiment, a method to detach and reattach at least one portal page may include detaching a selected portal page in response to activating a detach feature. The method may also include reattaching the detached portal page in response to activating a reattach feature. The selected, detached portal page may be transferred to a window in response to activating the detach feature. Tunneling communication may be provided between the detached portal page and the portal environment.

Abstract: Techniques are disclosed for controlling where dynamically-added content will be positioned within the layout of a content aggregation view (e.g., for controlling where content that is created by a portlet will be rendered within a portal page). In preferred embodiments, weighting values are assigned to the portlet, and these values are used to determine the portlet's relative placement. The values may be assigned at development time, at deployment time, and/or at run time. Using disclosed techniques, content placement is more predictable and consistent, and related content can be grouped together when rendered even though that content is not simultaneously rendered.

Abstract: A solution for generating a portal page based on a data item. In particular, one or more portlets are selected from a set of available portlets based on the data item. The selected portlet(s) are then included on the portal page, which can be provided to a user device for display. The data item can be provided to a content provider for the portlet in order to generate the display area for the portlet. Information on the user and/or user device can be used when selecting the one or more portlets for inclusion on the portal page.

Abstract: A solution for generating a portal page based on a data item. In particular, one or more portlets are selected from a set of available portlets based on the data item. The selected portlet(s) are then included on the portal page, which can be provided to a user device for display. The data item can be provided to a content provider for the portlet in order to generate the display area for the portlet. Information on the user and/or user device can be used when selecting the one or more portlets for inclusion on the portal page.

Abstract: A method to control a portlet associated with a portal page may include deactivating a selected portlet in response to operating a deactivation feature. The method may also include reactivating the selected portlet in response to operating a reactivation feature. The method may also include freezing a portlet content in the selected portlet in response to deactivating the selected portlet. The method may further include disabling hyperlinks, buttons and other inputs to the selected portlet in response to deactivating the selected portlet. The method may further include reconfiguring a portal server to ensure that a portlet content of a selected portlet cannot be affected while the selected portlet is deactivated.

Abstract: The present invention provides a methodology for maintaining user sessions using cookie updation. A method in accordance with an embodiment of the present invention includes: periodically updating a value in a session cookie using a program implemented in a source code of a web page; stopping the updating of the value when a user navigates away from the web page; and automatically logging the user out of the web page if the value is determined to be invalid by a web server.

Abstract: Techniques are disclosed for efficiently updating rendered content (such as content of a Web page) using a “slow-loading” content element, such as a slow-loading image. A reference is embedded within the markup language notation for the content to be rendered, where this reference identifies the source of the slow-loading content element. Delivery of the slow-loading content therefore begins automatically, when the content is rendered. Event handling attributes are specified with the reference, where values of these attributes identify client-side logic to be invoked when the associated event occurs. If the server determines that the rendered content, or some portion thereof, should be asynchronously updated, it abruptly terminates delivery of the slow-loading content. This termination triggers an event handler, which operates to automatically request reloading of the content.

Abstract: A system and method is provided for displaying a selection based action bar to a user that the user is able to use to perform actions using selected data. A user selects one or more displayed selections using a selection device. After the user selections have been made, the system determines which actions can be used with the selected data. Graphical components that correspond to the allowed actions are placed in an action bar and the action bar is displayed proximate to at least one of the user's selections. The action bar is not removed and remains visible as a result of the user scrolling display or performing unrelated actions. Providing a persistent action bar in location proximate to the user's selection helps the user maintain focus on the selected data. In addition, the selection based action bar can be used as a visual placeholder are marking mechanism.

Abstract: Improved caching of content at caching proxy (“CP”) servers is disclosed. In one aspect, negotiations occur before content is dynamically distributed, whereby an entity such as a Web server selects content and at least one target CP server, and sends a content distribution request to each target, describing the content to be distributed. Preferably, the selection is made by dynamically prioritizing content based on historical metrics. In another aspect, a CP server that receives a content distribution request during these negotiations determines its response to the distribution request. Preferably, content priority of already-cached content is compared to priority of the content described by the content distribution request when making the determination. In yet another aspect, a CP server selectively determines whether to cache content during cache miss processing.

Abstract: Improved caching of content at caching proxy (“CP”) servers is disclosed. In one aspect, negotiations occur before content is dynamically distributed, whereby an entity such as a Web server selects content and at least one target CP server, and sends a content distribution request to each target, describing the content to be distributed. Preferably, the selection is made by dynamically prioritizing content based on historical metrics. In another aspect, a CP server that receives a content distribution request during these negotiations determines its response to the distribution request. Preferably, content priority of already-cached content is compared to priority of the content described by the content distribution request when making the determination. In yet another aspect, a CP server selectively determines whether to cache content during cache miss processing.

Abstract: A system and method is provided for displaying a selection based action bar to a user that the user is able to use to perform actions using selected data. A user selects one or more displayed selections using a selection device. After the user selections have been made, the system determines which actions can be used with the selected data. Graphical components that correspond to the allowed actions are placed in an action bar and the action bar is displayed proximate to at least one of the user's selections. The action bar is not removed and remains visible as a result of the user scrolling display or performing unrelated actions. Providing a persistent action bar in location proximate to the user's selection helps the user maintain focus on the selected data. In addition, the selection based action bar can be used as a visual placeholder are marking mechanism.

Abstract: Techniques are disclosed for efficiently updating rendered content (such as content of a Web page) using a “slow-loading” content element, such as a slow-loading image. A reference is embedded within the markup language notation for the content to be rendered, where this reference identifies the source of the slow-loading content element. Delivery of the slow-loading content therefore begins automatically, when the content is rendered. Event handling attributes are specified with the reference, where values of these attributes identify client-side logic to be invoked when the associated event occurs. If the server determines that the rendered content, or some portion thereof, should be asynchronously updated, it abruptly terminates delivery of the slow-loading content. This termination triggers an event handler, which operates to automatically request reloading of the content.

Abstract: A system and method that provides platform independent retrieval of software component data is provided. The discovered system and method manage conflicts, co-requisites, and pre-requisites associated with installing a software component by including such information in a software description which is retrieved in a platform-neutral manner. The system and method can be initiated by the target computer system or it can be driven by a application server that connects to the target computer system through a computer network. In a target initiated environment, the target computer system resolves conflict and co-/pre-requisite issues identified in the component description before installing the component software. In a server-initiated process, the server resolves the identified conflict and co-/pre-requisite issues on behalf of the target system and installs the software component on the target system.