# US 7,614,039 B2 · Backing files for portal element controls > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 7,614,039 B2 - Document ID: US7614039B2 - Status: Granted - Kind: B2 - Application number: 11/131,578 - Filed: 2005-05-18 - Published: 2006-03-30 - Granted: 2009-11-03 - Earliest claimed: 2004-05-21 - Assignees: BEA Systems, Inc. - Inventors: Chris Jolley - Web page: https://patentgrep.com/patent/US7614039B2 ## CPC - H04L 63/102: {Entity profiles} - G06F 16/958: Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking - H04L 67/56: Provisioning of proxy services (store-and-forward switching systems in data switching networks H04L12/54) - H04L 67/567: Integrating service provisioning from a plurality of service providers - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Backing files and backing contexts can be associated with portal elements controls for the construction of a portal. The backing files and backing contexts can allow interactions with the portal element controls before rendering. In one embodiment, developers are allowed to have access to backing files and backing contexts. The backing files allows developer code to be run before rendering. The backing contexts allow the setting and getting of information from the portal element controls. ## Claims ### Claim 1 A system including a portal including: means for constructing a portal using a portal element control with lifecycle methods, the portal element control being associated with a backing file; and means for using backing file code of the backing file in at least one lifecycle method of the portal element control before the rendering of the portal element; wherein the portal has a number of portal controls including a page control, a desktop control and a portlet control and wherein at least some of the portal controls have an associated backing file that contains code provided by developers to be run for an associated portal control; and wherein the system including at least one processor to run the portal. ### Claim 2 (depends on 1) The system of claim 1, wherein multiple portal element controls have backing files. ### Claim 3 (depends on 1) The system of claim 1, wherein a new instance of the backing file is created for each request. ### Claim 4 (depends on 1) The system of claim 1, wherein a backing context allows access to methods to affect state information of the portal element control before the rendering of the portal element. ### Claim 5 (depends on 4) The system of claim 4, wherein the backing file uses the backing context. ### Claim 6 (depends on 4) The system of claim 4, wherein the backing context allows access to get methods. ### Claim 7 (depends on 4) The system of claim 4, wherein the backing context allows access to set methods. ### Claim 8 (depends on 1) The system of claim 1, wherein the backing file includes business logic. ### Claim 9 (depends on 1) The system of claim 1, wherein backing file modifies the portal element display. ### Claim 10 (depends on 1) The system of claim 1, wherein a portal element skeleton JSP is used by the portal element control during the rendering of the portal element. ### Claim 11 A computer implemented method comprising: constructing a portal using a portal element control with lifecycle methods, the portal element control being associated with a backing file; and using backing file code of the backing file in at least one lifecycle method of the portal element control before the rendering of the portal element; wherein the portal has a number of portal controls including a page control, a desktop control and a port let control and wherein at least some of the portal controls have an associated backing file that contains code provided by developers to be run for an associated portal control. ### Claim 12 (depends on 11) The computer implemented method of claim 11, wherein multiple portal element controls have backing files. ### Claim 13 (depends on 11) The computer implemented method of claim 11, wherein a new instance of the backing file is created for each request. ### Claim 14 (depends on 11) The computer implemented method of claim 11, wherein a backing context allows access to methods to affect state information of the portal element control before the rendering of the portal element. ### Claim 15 (depends on 14) The computer implemented method of claim 14, wherein the backing file uses the backing context. ### Claim 16 (depends on 14) The computer implemented method of claim 14, wherein the backing context allows access to get methods. ### Claim 17 (depends on 14) The computer implemented method of claim 14, wherein the backing context allows access to set methods. ### Claim 18 (depends on 11) The computer implemented method of claim 11, wherein the backing file includes business logic. ### Claim 19 A machine storage medium having instructions stored thereon that when executed by a processor cause a system to: construct a portal using a portal element control with lifecycle methods, the portal element control being associated with a backing file; and use backing file code of the backing file in at least one lifecycle method of the portal element control before the rendering of the portal element; wherein the portal has a number of portal controls including a page control, a desktop control and a portlet control and wherein at least some of the portal controls have an associated backing file that contains code provided by developers to be run for an associated portal control. ### Claim 20 (depends on 19) The machine readable medium of claim 19, wherein multiple portal element controls have backing files.