Interpreting semantic application code

• US 8,843,942 B2
• Filed: 09/29/2008
• Issued: 09/23/2014
• Est. Priority Date: 09/28/2007
• Status: Active Grant

• Current Assignee: Xcerion AB
• Original Assignee: Xcerion AB
• Inventors: Arthursson, Daniel, Bristav, Marcus
• Primary Examiner(s): Ho, Andy
• Application Number:
  US12/240,841
• Publication Number:
  US 20090172702A1
• Time in Patent Office: 2,185 Days
• Field of Search: 719/318, 719/320
• US Class Current: 719/318
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 9/455 Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
• CPC Class Codes: G06F 9/45504 Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
• CPC Class Codes: G06F 9/45529 Embedded in an application, e.g. JavaScript in a Web browser
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

Generally described, the present invention is directed to a network operating system that provides more effective ways of leveraging the connectivity of computer networks. In one embodiment, an XML virtual machine is implemented that accepts high-level application code written in an XML programming language as input. Functionality is provided to interpret or translate the application code written in an XML programming language into code that is suitable for execution across computer platforms. Moreover, the XML virtual machine supports the Model View Controller (MVC) design paradigm that facilitates true data abstraction from applications to a common data model. Multi-instance applications, with each instance potentially supporting multiple views, may be created and executed.

Claims

1. A method implemented in instructions executed by a computer processor of initiating execution of an application'"'"'s process code, the method comprising:

identifying a data type of a document associated with the application being launched; and

in response to determining that the document contains the application'"'"'s process code;

instantiating a process object having an execute method for executing at least one process step, wherein one or more operations associated with the process step are defined within the document, and wherein at least one process step includes an operation that, upon execution, directs a flow of execution to another process step;

causing the process object to be associated with an application instance; and

activating an execute method in the process object and providing the process object the corresponding application instance and the process step to execute the operations associated with the process step.

2. The method as recited in claim 1, wherein the application'"'"'s process code is described in a process XML document adhering to a first schema, the process XML document having at least one operation element to open a UI XML document that adheres to a second schema.

3. The method as recited in claim 1, wherein identifying a data type of a document associated with an application being launched includes using a data type recognizer to apply criteria associated with a plurality of data types to structural data in the document.

4. The method as recited in claim 3, wherein the data type recognizer is configured to cause a different set of actions to be performed when opening a process XML document depending on whether an application package or standalone application is being launched.

5. The method as recited in claim 1, wherein instantiating a process object includes:

identifying and registering a trigger defined in a trigger element of a process XML document; and

in response to a user interface component experiencing a trigger event, executing one or more operations associated with a process step specified in the trigger element.

6. The method as recited in claim 1, wherein the instantiated process object allows a second object to register as a listener that is notified in response to process logic of an executing application being modified.

7. The method as recited in claim 1, wherein the application'"'"'s process code is described in an XML document and wherein activating an execute method of the process object includes evaluating an expression that references the XML document.

8. A method implemented in instructions executed by a computer processor of executing an application'"'"'s process code, the method comprising:

instantiating a process object based on a process XML document, wherein the process XML document adheres to a process XML schema, and wherein the process XML document includes;

a trigger element having one or more attributes for identifying process code to execute in response to a user interface component experiencing a trigger event; and

a plurality of process step elements, wherein at least one process step element of the plurality of process step elements includes at least one operation element having one or more attributes identifying an operation handler to execute and an associated expression, and wherein at least one process step element of the plurality of process step elements includes an operation element for directing a flow of execution to another process step element; and

in response to the user interface component experiencing a trigger event with attributes matching the trigger element, causing logic represented in at least one process step element to be executed.

9. The method as recited in claim 8, wherein the trigger element includes view and component attributes for identifying the application view and component associated with the trigger.

10. The method as recited in claim 8, wherein the trigger element includes event and step attributes specifying the event type and process step element to execute in response to the trigger being activated.

11. The method as recited in claim 8, wherein the operation element includes a component element having one or more attributes identifying a user interface component and an associated XPath expression.

12. The method as recited in claim 11, wherein causing logic represented in the at least one operation element to be executed includes creating an XBind that references data in a data model, wherein the XBind includes an identification of a resource, a base path, and a selection.

13. The method as recited in claim 8, wherein executing the logic represented in the at least one operation element includes opening a UI XML document identified in an expression and causing an application view represented in the UI XML document to be visually rendered on a computer display.

14. The method as recited in claim 8, wherein the process XML document is generated using a meta-editor in which constraints of a process XML schema are applied to graphical input provided by a user.

15. A system that connects a controller layer of an application to a data model and view layers of the application, the system comprising at least one computing device, wherein the at least one computing device includes at least one processor and is configured to provide:

an expression engine configured to provide declarative access to the model layer from process logic of the application without having an object in the controller layer interact directly with an object in the model layer, wherein the process logic of the application is defined in a process XML document that includes a plurality of process step elements, wherein each process step element includes at least one operation element, and wherein at least one operation element of at least one process step element of the process XML document is configured to cause a flow of execution to be directed to another process step element;

an event manager operative to allow the process logic of the application to register a listener for a trigger that originates from an object within the view layer of the application; and

a process component configured to;

cause expressions that reference the data model layer to be evaluated by the expression engine relative to the appropriate application instance;

register one or more triggers with the event manager; and

receive notice from the event manager when an object within the view layer of the application experiences a trigger.

16. The system as recited in claim 15, wherein to cause expressions referencing the data model layer to be evaluated by the expression engine relative to the appropriate application instance includes establishing a relationship hierarchy between an instance object and at least one object associated with the controller layer and at least one object associated with the view layer.

17. The system as recited in claim 15, wherein to cause expressions referencing the data model layer to be evaluated by the expression engine relative to the appropriate application instance includes configuring an instance object to hold the expression engine.

18. The system as recited in claim 15, wherein receiving notice of the trigger includes causing the object within the view layer of the application to identify an application instance that experienced the trigger.