Method for portlet instance support in a graphical user interface

• US 7,934,163 B2
• Filed: 02/27/2004
• Issued: 04/26/2011
• Est. Priority Date: 02/28/2003
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Bergman, Robert, Allamaraju, Subrahmanyam, Beartusk, Brodi, Jolley, Christopher, Naidu, Purushotham Babu, D'Ambrosia, James, Murnock, George, Musson, Scott, Sawant, Sameer, Hetzel, Stephen, Frender, Kevin Blair
• Primary Examiner(s): Huynh; Ba
• Assistant Examiner(s): Hassan; Rashedul
• Application Number:
  US10/788,801
• Publication Number:
  US 20050108034A1
• Time in Patent Office: 2,615 Days
• Field of Search: 715/700, 715/762, 715/742, 715/760
• US Class Current: 715/762
• CPC Class Codes: G06F 3/0482 Interaction with lists of selectable items, e.g. menus
• CPC Class Codes: G06F 3/0483 Interaction with page-structured environments, e.g. book metaphor
• CPC Class Codes: G06F 8/38 for implementing user interfaces
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces

Abstract

A method for responding to a request, comprising accepting the request, mapping the request to a control tree wherein the control tree is a logical representation of a graphical user interface (GUI) and wherein the control tree includes a set of controls which are related hierarchically to one another, advancing the control tree through at least one lifecycle stage based on the request, wherein the control tree includes at least one portlet control that represents at least one portlet, providing the request to a portlet container that contains the at least one portlet, and aggregating the output of each of the at least one portlets and providing the output to the GUI.

Claims

1. A method for supporting a portal application, comprising:

accepting a request, at a container on one or more web servers, from a user that interacts with a graphical user interface (GUI) of a web application at a client side;

mapping the request to a control tree factory, wherein the control tree factory is operable to

obtain an XML stream from different sources;

parse the XML stream into a Document Object Model (DOM) tree; and

generate a control tree in the container from the DOM tree based on the request, wherein the control tree is a logical representation of the graphical user interface (GUI), wherein the control tree includes a set of controls, each of which controls represents at least one of a graphical element and a functional element in the GUI;

associating at least one control in the control tree with another control in the control tree using an event notification mechanism, wherein the event notification mechanism allows the at least one control to register with the another control in the control tree for events that the another control raises;

advancing the control tree through at least one lifecycle stage in a sequence of one or more lifecycles, wherein the at least one control in the control tree operates to be updated once the at least one control receives an event notification from the another control in the control tree through the event notification mechanism;

aggregating the output of each control of the set of controls in the control tree to produce a response based on the request; and

providing the response to the GUI.

2. The method of claim 1 further comprising:

creating a metadata representation of the control tree; and

generating a class to construct the control tree based on the metadata representation.

3. The method of claim 1 further comprising:

allowing the request to be a hypertext transfer protocol request (HTTP); and

allowing the request to originate from a web browser.

4. The method of claim 1, further comprising:

providing the response to a web browser.

5. The method of claim 1 further comprising:

advancing the control tree through the at least one lifecycle stage by an interchangeable lifecycle component.

6. The method of claim 1 further comprising:

allowing each one of the set of controls to have an interchangeable persistence mechanism.

7. The method of claim 1 further comprising:

allowing each one of the set of controls to render itself according to a theme.

8. The method of claim 1 further comprising:

advancing one of the set of controls through the series of at least one lifecycle stage in parallel with another of the controls.

9. The method of claim 1 further comprising:

allowing a lifecycle stage to be one of;

init, load state, create child controls, load, raise events, pre-render, render, save state, unload and dispose.

10. The method of claim 1 further comprising:

allowing the response to be a hypertext transfer protocol (HTTP) response.

11. The method of claim 1 further comprising:

allowing controls to raise events and respond to events.

12. The method of claim 1 further comprising:

allowing each one of the set of controls to be one of;

Book, Page, Window, Menu, Layout, Portlet, Theme, Placeholder, Shell, LookAndFeel, Desktop, Body, Footer, Header, Head, Titlebar, ToggleButton, TreeView, TreeViewWithRadioButtons.

25. The method of claim 1, further comprising:

allowing the one or more lifecycles of the control tree to be provided and managed by the container and to be modified by the container, and wherein one or more controls in the control tree can save their states at a particular stage in the one or more lifecycles and can then reload these states at a later stage in the one or more lifecycles.

26. The method of claim 1, further comprising:

associating, via each container, a context object with the control tree factory, wherein each context object provide access to the protocol and application framework that is associated with that container.

27. The method of claim 1, wherein:

the control tree factory uses one or more meta data to construct statically created controls at initialization of the control tree, wherein dynamically created controls are created in the control tree in reaction to state, context, and events during a control tree lifecycle.

13. A machine readable storage medium having instructions stored thereon that when executed by a processor cause a system to:

accept a request, at a container on one or more web servers, from a user that interacts with a graphical user interface (GUI) of a web application;

map the request to a control tree factory, wherein the control tree factory is operable to

obtain an XML stream from different sources;

parse the XML stream into a Document Object Model (DOM) tree; and

generate a control tree in the container from the DOM tree based on the request, wherein the control tree is a logical representation of the graphical user interface (GUI), wherein the control tree includes a set of controls, each of which controls represents at least one of a graphical element and a functional element in the GUI;

associate at least one control in the control tree with another control in the control tree using an event notification mechanism, wherein the event notification mechanism allows the at least one control to register with the another control in the control tree for events that the another control raises;

advance the control tree through at least one lifecycle stage in a sequence of one or more lifecycles, wherein the at least one control in the control tree operates to be updated once the at least one control receives an event notification from the another control in the control tree through the event notification mechanism;

aggregate the output of each of the set of controls to produce a response based on the request; and

provide the response to the GUI.

14. The machine readable medium of claim 13, further comprising instructions that when executed cause the system to:

create a metadata representation of the control tree; and

generate a class to construct the control tree based on the metadata representation.

15. The machine readable medium of claim 13 wherein:

the request is a hypertext transfer protocol request (HTTP); and

the request originates from a web browser.

16. The machine readable medium of claim 13, further comprising instructions that when executed cause the system to:

provide the response to a web browser.

17. The machine readable medium of claim 13 wherein:

the control tree is advanced through the at least one lifecycle stage by an interchangeable lifecycle component.

18. The machine readable medium of claim 13 wherein:

each one of the set of controls can have an interchangeable persistence mechanism.

19. The machine readable medium of claim 13 wherein:

each one of the set of controls can render itself according to a theme.

20. The machine readable medium of claim 13 wherein:

one of the set of controls can advance through the series of at least one lifecycle stage in parallel with another of the controls.

21. The machine readable medium of claim 13 wherein:

a lifecycle stage is one of;

init, load state, create child controls, load, raise events, pre-render, render, save state, unload and dispose.

22. The machine readable medium of claim 13 wherein:

the response is a hypertext transfer protocol (HTTP) response.

23. The machine readable medium of claim 13 wherein:

controls can raise events and respond to events.

24. The machine readable medium of claim 13 wherein:

each one of the set of controls can be one of;

Book, Page, Window, Menu, Layout, Portlet, Theme, Placeholder, Shell, LookAndFeel, Desktop, Body, Footer, Header, Head, Titlebar, ToggleButton, TreeView, TreeViewWithRadioButtons.

28. A method for supporting a portal application, comprising:

accepting a request, at a container on one or more web servers, from a user that interacts with a graphical user interface (GUI) of a web application at a client side;

mapping the request to a control tree factory, wherein the control tree factory is operable to

obtain an XML stream from different sources;

parse the XML stream into a Document Object Model (DOM) tree; and

generate a control tree in the container from the DOM tree based on the request, wherein the control tree is a logical representation of the graphical user interface (GUI), wherein the control tree includes a set of controls, each of which controls represents at least one of a graphical element and a functional element in the GUI, wherein at least one said control is a desktop control that contains one or more personalized view of the portal application, wherein the desktop control contains at least a booklet control and a look-and-feel control, wherein the booklet control represents a set of pages linked by a page navigator and the look-and-feel control determines the appearance of the one or more personalized view of the portal application;

associating the booklet control with the look-and-feel control using an event notification mechanism, wherein the event notification mechanism allows the look-and-feel control to register with the booklet control in the control tree for events that the booklet control raises;

advancing the control tree through at least one lifecycle stage in a sequence of one or more lifecycles, wherein the look-and-feel control operates to be updated once the look-and-feel control receives an event notification from the booklet control in the control tree through the event notification mechanism;

aggregating the output of each control of the set of controls in the control tree to produce a response based on the request; and

providing the response to the GUI.