System and method for dynamic data binding in distributed applications

• US 7,650,276 B2
• Filed: 02/17/2004
• Issued: 01/19/2010
• Est. Priority Date: 02/26/2003
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: O'Neil, Edward K., Olander, Daryl B.
• Primary Examiner(s): Hudspeth; David R
• Assistant Examiner(s): Jackson; Jakieda R
• Application Number:
  US10/780,300
• Publication Number:
  US 20040250241A1
• Time in Patent Office: 2,163 Days
• Field of Search: 704/8, 704/3
• US Class Current: 704/8
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking

Abstract

A system and method for dynamically binding a user interface to information, comprising specifying with a first language a first action; specifying with a second language a first data source associated with the first action; rendering output with a third language based at least partially on the first action; wherein the second language is embedded in the first language; and wherein the first action can set or get the first data source.

Claims

1. A method for dynamically binding a user interface to information stored in a data source, comprising:

displaying a user interface, wherein the user interface is operable to

display information in a web page, wherein the information is stored in a first data source on a business object,

collect additional information from a user, and

store the additional information in the first data source on the business object;

providing a data binding tag that defines

a rendering boundary within the web page for rendering the information, and

rules to be applied when the information is rendered, wherein the data binding tag includes a plurality of attributes;

specifying, by the data binding tag, a first action which includes reading or updating the information stored in the first data source, wherein at least one of the attributes is associated with the first action;

specifying the first data source associated with the first action using a script; and

rendering each item in the first data source on the web page in the user interface with a markup language according to the boundary and the rules defined by the data binding tag and based on the first action, including evaluation of the script.

2. The method of claim 1 wherein:

the data binding tag allows for the specification of JavaServer Page action elements.

3. The method of claim 1 wherein:

the scripting language is based on the Javascript language.

4. The method of claim 1 wherein:

the first data source identifies one of;

     1) an object field;

     2) an object property; and

     3) an Extensible Markup Language document element.

5. The method of claim 4 wherein:

an object is a JavaBean.

6. The method of claim 1 wherein:

the first data source is one of;

     1) an array;

     2) a list;

     3) a map.

7. The method of claim 1 wherein:

the markup language can include at least one of;

Hypertext Markup Language (HTML), Dynamic HTML, Extensible HTML, and Extensible Markup Language.

8. The method of claim 1 wherein:

the first action can have at least one child action.

9. The method of claim 8 wherein:

the at least one child action can refer to the first data source with a context defined by the first action.

10. The method of claim 8 wherein:

the at least one child action can perform at least one of the following actions on the first data source;

     1) set;

     2) get;

     3) sort; and

     4) filter.

11. The method of claim 8, further comprising:

rendering a list or a table based on the first data source.

12. The method of claim 1 wherein the additional information includes an expression that is stored in the data source and wherein the expression is evaluated to produce a value when the additional information is rendered.

13. The method of claim 1 wherein the data binding tag includes a repeater element wherein data associated with the repeater element is rendered multiple times according to the repeater element'"'"'s lifecycle.

14. The method of claim 13 wherein the repeater'"'"'s lifecycle includes a plurality of states including an item state during which the repeater element determines, for each of the data associated with the repeater element, a user interface with which to render the data and permission to render the data in the user interface.

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

display a user interface, wherein the user interface is operable to

display information in a web page, wherein the information is stored in a data source on a business object,

collect additional information from a user, and store the additional information in the data source on the business object;

provide a data binding tag that defines

a rendering boundary within the web page for rendering the information, and

rules to be applied when the information is rendered,

wherein the data binding tag includes a plurality of attributes;

specify, by the data binding tag, a first action which includes reading or updating the information stored in the data source, wherein at least one of the attributes is associated with the first action;

specify, using a script, at least one attribute on the data binding tag to reference the data source associated with the first action; and

render each item in the first data source on the web page in the user interface with a markup language according to the boundary and the rules defined by the data binding tag and based at least partially on the first action, including evaluation of the script.

16. The machine readable medium of claim 15 wherein:

the data binding tag allows for the specification of JavaServer Page action elements.

17. The machine readable medium of claim 15 wherein:

the scripting language is based on the Javascript language.

18. The machine readable medium of claim 15 wherein:

the first data source identifies one of;

     1) an object field;

     2) an object property; and

     3) an Extensible Markup Language document element.

19. The machine readable medium of claim 18 wherein:

an object is a JavaBean.

20. The machine readable medium of claim 15 wherein:

the first data source is one of;

     1) an array;

     2) a list;

     3) a map.

21. The machine readable medium of claim 15 wherein:

the markup language can include at least one of;

Hypertext Markup Language (HTML), Dynamic HTML, Extensible HTML, and Extensible Markup Language.

22. The machine readable medium of claim 15 wherein:

the first action can have at least one child action.

23. The machine readable medium of claim 22 wherein:

the at least one child action can refer to the first data source with a context defined by the first action.

24. The machine readable medium of claim 22 wherein:

the at least one child action can perform at least one of the following actions on the first data source;

     1) set;

     2) get;

     3) sort; and

     4) filter.

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

render a list or a table based on the first data source.

26. The machine readable medium of claim 15 wherein the additional information includes an expression that is stored in the data source and wherein the expression is evaluated to produce a value when the additional information is rendered.

27. The machine readable medium of claim 15 wherein the data binding tag includes a repeater element wherein data associated with the repeater element is rendered multiple times according to the repeater element'"'"'s lifecycle.

28. The machine readable medium of claim 27 wherein the repeater'"'"'s lifecycle includes a plurality of states including an item state during which the repeater element determines, for each of the data associated with the repeater element, a user interface with which to render the data and permission to render the data in the user interface.

29. A system for dynamically binding a user interface to information, comprising:

a computer including a computer readable medium and processor operating thereon;

a user interface that is operable to

display information in a webpage, wherein the information is stored in a business object,

collect additional information from the user, and

store the additional information within the business object;

a plurality of data binding tags written in a first programming language stored on the computer readable medium wherein each data binding tag

defines a rendering boundary within a web page for rendering the information and rules to be applied when the information is rendered,

includes a lifecycle associated therewith,

includes a plurality of attributes, and

specifies an action to be performed on the business object wherein the action includes reading or updating information from the business object including the additional information;

an expression language that can be used to evaluate expressions on specified business objects, wherein each expression specifies a business object in which the expression is to be evaluated; and

a markup language that can be used to render the specified business objects on the web page in the user interface according to the render boundary and the rules defined by the data binding tag.

30. A system for dynamically binding a user interface to information stored in a data source, comprising:

a web page that includes a plurality of data binding tags, wherein the data binding tags bind information stored in a data source on a business object to the web page;

a user interface, wherein the user interface is operable to display the web page including the information that is stored in the data source on the business object,

receive additional information from a user through fields in the web page, and

store the additional information in the data source on the business object;

wherein when the web page is displayed, the plurality of data binding tags are processed, which includes rendering the information stored in the data source that is referenced by each of the data binding tags, according to

a rendering boundary defined by that data binding tag, and

rules that define when the information is rendered for that tag, based on a current state of that tag; and

wherein when the additional information is received from a user through a field in the web page, a data binding tag associated with that field is processed to perform an action specified by that data binding tag, wherein the action includes one or more of updating or reading from the data source referenced by the data binding tag.

31. The system of claim 30 wherein:

each data binding tag references the data source using a script.

32. The system of claim 30 wherein:

the data source identifies one of an object field, an object property, and an Extensible Markup Language document element.

33. The system of claim 30 wherein:

the data source is one of an array, a list and a map.

34. The system of claim 30 wherein:

the web page is rendered in one or more of Hypertext Markup Language (HTML), Dynamic HTML, Extensible HTML, and Extensible Markup Language.

35. The system of claim 30 wherein:

the action can include a hierarchy of actions.

36. The system of claim 35 wherein:

each action in the hierarchy of actions can refer to the data source with a context defined by that action.

37. The system of claim 35 wherein:

each action in the hierarchy of actions can include one or more of set, get, sort, and filter.

38. The system of claim 30 wherein:

a list or a table can be rendered in the web page based on the data source.

39. The framework of claim 30 wherein the additional information includes an expression that is stored in the data source and wherein the expression is evaluated to produce a value when the additional information is rendered.

40. The framework of claim 30 wherein each data binding tag can include a repeater element wherein data associated with the repeater element is rendered multiple times according to the repeater element'"'"'s lifecycle.

41. The framework of claim 40 wherein the repeater'"'"'s lifecycle includes a plurality of states including an item state during which the repeater element determines, for each of the data associated with the repeater element, a user interface with which to render the data and permission to render the data in the user interface.