# US 2010/0251131 A1 · System and method for reusing control tree

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2010/0251131 A1
- Document ID: US20100251131A1
- Status: Published application
- Kind: A1
- Application number: 12/796,547
- Filed: 2010-06-08
- Published: 2010-09-30
- Earliest claimed: 2005-09-22
- Assignees: BEA Systems, Inc.
- Inventors: Christopher Jolley; Purushotham Babu Naidu
- Web page: https://patentgrep.com/patent/US20100251131A1

## CPC

- G06F 16/954: Navigation, e.g. using categorised browsing
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A portal containing a plurality of controls that are represented by a meta control hierarchy representing, wherein each node in the meta control hierarchy holds information of one of the plurality of controls. Upon receiving a request from a user for rendering of the portal, a control hierarchy can be created based on the meta control hierarchy. A portal managing component is operable to retrieve a portion of the meta control hierarchy from a cache and create the remaining portion of the meta control hierarchy that does not exist in cache from an XML markup file of the portal.

## Claims

### Claim 1

A system to provide control hierarchy compression, comprising:
a portal containing a plurality of controls;
a meta control hierarchy representing the plurality of controls on the portal, wherein each node in the meta control hierarchy holds information of one of the plurality of controls;
a control hierarchy created upon a user's request for rendering of the portal; and
a portal managing component operable to perform at least one of:
accepting the user's request for rendering the portal or one of more of its plurality of controls;
retrieving a portion of the meta control hierarchy from a cache;
creating the remaining portion of the meta control hierarchy that does not exist in cache from an XML markup file of the portal;
creating the control hierarchy from the meta control hierarchy;
running a plurality of stages of a control lifecycle on each node in the control hierarchy; and
rendering the portal or one of its plurality of control based on the control hierarchy.

### Claim 2 (depends on 1)

The system according to claim 1, wherein:
the meta control hierarchy and the control hierarchy can be a meta control tree and a control tree, respectively.

### Claim 3 (depends on 2)

The system according to claim 2, wherein:
the portion of the meta control hierarchy can be one or more sub trees.

### Claim 4 (depends on 1)

The system according to claim 1, wherein:
each of the plurality of controls can be one of: a desktop, a main book, a book, a page, and a portlet.

### Claim 5 (depends on 1)

The system according to claim 1, wherein:
the portal may have a single or a multi-level menu.

### Claim 6 (depends on 1)

The system according to claim 1, wherein:
each of the plurality of stages of the control lifecycle can be one of: init, load, loadstate, handlePostback, raiseChangeEvents, preRender, saveState, render and destroy.

### Claim 7 (depends on 1)

The system according to claim 1, wherein:
the user request can be submitted via a mouse click.

### Claim 8 (depends on 1)

The system according to claim 1, wherein:
the portal managing component is further operable to perform at least one of:
storing the portion of the meta control hierarchy created in the cache;
sharing the portion of the meta control hierarchy with another meta control hierarchy for another user's request or for the same user's request; and
removing the portion of the meta control hierarchy from the cache once a session for the user request is finished.

### Claim 9 (depends on 1)

The system according to claim 1, wherein:
the portal can be customized by a user with one or more of the plurality of controls on the portal added or removed.

### Claim 10 (depends on 9)

The system according to claim 9, wherein:
the portal managing component is further operable to perform at least one of the following when the portal is not customized:
retrieving a default meta control hierarchy from the cache if such hierarchy exists; and
creating the default meta control hierarchy and storing it in the cache if such hierarchy does not exist.

### Claim 11

A method to provide control hierarchy compression, comprising:
accepting a user's request for rendering a portal or one or more of its plurality of controls;
retrieving a portion of a meta control hierarchy from a cache, wherein the meta control hierarchy represents the plurality of controls on the portal and each node in the meta control hierarchy holds information of one of the plurality of controls;
creating the remaining portion of the meta control hierarchy that does not exist in cache from an XML markup file of the portal;
creating the control hierarchy from the meta control hierarchy;
running a plurality of stages of a control lifecycle on each node in the control hierarchy; and
rendering the portal or one of its plurality of control based on the control hierarchy.

### Claim 12 (depends on 11)

The method according to claim 11, further comprising:
allowing the meta control hierarchy and the control hierarchy to be a meta control tree and a control tree, respectively.

### Claim 13 (depends on 12)

The system according to claim 12, further comprising:
allowing the portion of the meta control hierarchy to be one or more sub trees.

### Claim 14 (depends on 11)

The method according to claim 11, further comprising:
submitting the user request via a mouse click.

### Claim 15 (depends on 11)

The method according to claim 11, further comprising:
running each node in the control hierarchy with at least one of following stages of the control lifecycle: init, load, loadstate, handlePostback, raiseChangeEvents, preRender, saveState, render and destroy.

### Claim 16 (depends on 11)

The method according to claim 11, further comprising at least one of:
storing the portion of the meta control hierarchy created in the cache;
sharing the portion of the meta control hierarchy with another meta control hierarchy for another user's request or for the same user's request; and
removing the portion of the meta control hierarchy from the cache once a session for the user request is finished.

### Claim 17 (depends on 11)

The method according to claim 11, further comprising:
customizing the portal by adding or removing one or more of the plurality of controls on the portal.

### Claim 18 (depends on 17)

The method according to claim 17, further comprising:
performing at least one of the following when the portal is not customized:
retrieving a default meta control hierarchy from the cache if such hierarchy exists; and
creating the default meta control hierarchy and storing it in the cache if such hierarchy does not exist.

### Claim 19

A machine readable medium having instructions stored thereon that when executed cause a system to:
accept a user's request for rendering a portal or one or more of its plurality of controls;
retrieve a portion of a meta control hierarchy from a cache, wherein the meta control hierarchy represents the plurality of controls on the portal and each node in the meta control hierarchy holds information of one of the plurality of controls;
create the remaining portion of the meta control hierarchy that does not exist in cache from an XML markup file of the portal;
create the control hierarchy from the meta control hierarchy;
run a plurality of stages of a control lifecycle on each node in the control hierarchy; and
render the portal or one of its plurality of control based on the control hierarchy.
