System and method for structuring distributed applications

• US 20050240863A1
• Filed: 02/17/2004
• Published: 10/27/2005
• Est. Priority Date: 02/25/2003
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Howes, Jason, Dew, Douglas, O'Neil, Edward, Olander, Daryl B., Cook, Thomas A., Giridhar, Sathyanarayana, Feit, Richard
• Granted Patent: US 7,774,697 B2
• Time in Patent Office: Days
• US Class Current: 715/229
• CPC Class Codes: G06F 8/20 Software design

Abstract

A system and method for accepting a communication, comprising providing the communication to a controller, associating a model with said communication, determining a state of the model based on said communication, providing a view based on the state of the model, and wherein the view is a page in a page group.

Claims

1. A system for a distributed application wherein said framework is capable of accepting a communication, comprising:

a controller operable to accept the communication and provide the communication to a model;

the model operable to perform processing of the request and to determine a page to be rendered;

the page operable to provide a response based on the request; and

wherein the page belongs to a page group.

2. The system of claim 1 wherein:

the page can be the target of an action method; and

wherein the page can raise an action method.

3. The system of claim 2 wherein:

an action method can implement code that can results in website navigation, passing data, and/or invoking back-end business logic.

4. The system of claim 1 wherein:

a page group can control page flow between pages and other page groups.

5. The system of claim 1 wherein:

a page group can include application logic that is separate from a logic related to rendering a graphical user interface.

6. The system of claim 1 wherein:

the page group can be nested within another page group.

7. The system of claim 1 wherein:

the page group maintains the state of the pages in the group.

8. The system of claim 1 wherein:

the page group is a set of functionally related pages.

9. The system of claim 1, further comprising:

a global page group to provide fallback action methods for the page.

10. The system of claim 1 wherein:

the page can be bound to a form; and

wherein the form encapsulates data that was posted to the page group by a web browser or other client.

19. The system of claim 11, further comprising:

a global page group to provide fallback action methods for the page.

11. A system for a distributed application wherein said framework is capable of accepting a communication, comprising:

a controller operable to accept the communication and provide the communication to a model;

the model operable to perform processing of the request and to determine a page to be rendered;

the page operable to provide a response based on the request;

wherein the page can be the target of an action method; and

wherein the page can raise an action method.

12. The system of claim 11 wherein:

an action method can implement code that can results in website navigation, passing data, and/or invoking back-end business logic.

13. The system of claim 11 wherein:

wherein the page belongs to a page group.

14. The system of claim 13 wherein:

a page group can control page flow between pages and other page groups.

15. The system of claim 13 wherein:

a page group can include application logic that is separate from a logic related to rendering a graphical user interface.

16. The system of claim 13 wherein:

the page group can be nested within another page group.

17. The system of claim 13 wherein:

the page group maintains the state of the pages in the group.

18. The system of claim 13 wherein:

the page group is a set of functionally related pages.

20. The system of claim 11 wherein:

the page can be bound to a form; and

wherein the form encapsulates data that was posted to the page group by a web browser or other client.

21. A method for accepting a communication, comprising:

providing the communication to a controller;

associating a model with said communication;

determining a state of the model based on said communication;

providing a view based on the state of the model; and

wherein the view is a page in a page group.

22. The method of claim 21 wherein:

the page can be the target of an action method; and

wherein the page can raise an action method.

23. The method of claim 22 wherein:

an action method can implement code that can results in website navigation, passing data, and/or invoking back-end business logic.

24. The method of claim 21 wherein:

a page group can control page flow between pages and other page groups.

25. The method of claim 21 wherein:

a page group can include application logic that is separate from a logic related to rendering a graphical user interface.

26. The method of claim 21 wherein:

the page group can be nested within another page group.

27. The method of claim 21 wherein:

the page group maintains the state of the pages in the group.

28. The method of claim 21 wherein:

the page group is a set of functionally related pages.

29. The method of claim 21, further comprising:

a global page group to provide fallback action methods for the page.

30. The method of claim 21 wherein:

the page can be bound to a form; and

wherein the form encapsulates data that was posted to the page group by a web browser or other client.

31. A method for accepting a communication, comprising:

providing the communication to a controller;

associating a model with said communication;

determining a state of the model based on said communication;

providing a view based on the state of the model;

wherein the view is a page in a page group;

wherein the page can be the target of an action method; and

wherein the page can raise an action method.

32. The method of claim 31 wherein:

an action method can implement code that can results in website navigation, passing data, and/or invoking back-end business logic.

33. The method of claim 31 wherein:

a page group can control page flow between pages and other page groups.

34. The method of claim 31 wherein:

a page group can include application logic that is separate from a logic related to rendering a graphical user interface.

35. The method of claim 31 wherein:

the page group can be nested within another page group.

36. The method of claim 31 wherein:

the page group maintains the state of the pages in the group.

37. The method of claim 31 wherein:

the page group is a set of functionally related pages.

38. The method of claim 31, further comprising:

a global page group to provide fallback action methods for the page.

39. The method of claim 31 wherein:

the page can be bound to a form; and

wherein the form encapsulates data that was posted to the page group by a web browser or other client.

40. A system comprising:

a means for providing a communication to a controller;

a means for associating a model with said communication;

a means for determining a state of the model based on said communication;

a means for providing a view based on the state of the model; and

wherein the view is a page in a page group.

41. A computer data signal embodied in a transmission medium, comprising:

a code segment including instructions to provide a communication to a controller;

a code segment including instructions to associate a model with said communication;

a code segment including instructions to determine a state of the model based on said communication;

a code segment including instructions to provide a view based on the state of the model; and

wherein the view is a page in a page group.

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

provide a communication to a controller;

associate a model with said communication;

determine a state of the model based on said communication;

provide a view based on the state of the model; and

wherein the view is a page in a page group.

43. The machine readable medium of claim 42 wherein:

the page can be the target of an action method; and

wherein the page can raise an action method.

44. The machine readable medium of claim 43 wherein:

an action method can implement code that can results in website navigation, passing data, and/or invoking back-end business logic.

45. The machine readable medium of claim 42 wherein:

a page group can control page flow between pages and other page groups.

46. The machine readable medium of claim 42 wherein:

a page group can include application logic that is separate from a logic related to rendering a graphical user interface.

47. The machine readable medium of claim 42 wherein:

the page group can be nested within another page group.

48. The machine readable medium of claim 42 wherein:

the page group maintains the state of the-pages in the group.

49. The machine readable medium of claim 42 wherein:

the page group is a set of functionally related pages.

50. The machine readable medium of claim 42, further comprising:

a global page group to provide fallback action methods for the page.

51. The machine readable medium of claim 42 wherein:

the page can be bound to a form; and

wherein the form encapsulates data that was posted to the page group by a web browser or other client.