System and method for pervasive software platform-based model driven architecture transaction aware application generator

• US 9,424,007 B2
• Filed: 02/25/2015
• Issued: 08/23/2016
• Est. Priority Date: 06/02/2011
• Status: Active Grant

• Current Assignee: Open Invention Network LLC
• Original Assignee: Open Invention Network LLC
• Inventors: DeAnna, Robert, Peterson, Robert W., Wheeler, Thomas T., Ye, Qin
• Primary Examiner(s): TECKLU, ISAAC TUKU
• Application Number:
  US14/631,268
• Publication Number:
  US 20150169302A1
• Time in Patent Office: 545 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/70 Software maintenance or management
• CPC Class Codes: G06F 9/466 Transaction processing
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

In developing applications for a plurality of node types, a meta-data definition of the application can be captured into an application definition module. The meta-data definition can describe the application for the plurality of node types. A code generation module can then automatically generate the application code for the plurality of node types, including transaction aware code. The code can be compiled per node type and the packaging necessary to deploy the application to the plurality of node types can also be automatically generated.

Claims

1. A method, comprising:

capturing a meta-data definition of an application into an application definition module, the meta-data definition describing at least a plurality of node types, the meta-data definition further comprising whether a class of the application is transaction aware;

compiling a code per node type for the plurality of node types in a code generation module; and

wherein capturing the meta-data definition comprises capturing a definition of peer-to-peer messaging including network type and protocol preference; and

wherein generating the code comprises generating the code that enables the application to communicate peer-to-peer in accordance with the captured network type and protocol preference.

2. The method of claim 1 wherein capturing the meta-data definition comprises capturing whether a class of the application is shareable.

3. The method of claim 2 wherein generating the code comprises generating shareable code that enables the class to be shared to peers and peer-groups.

4. The method of claim 1 wherein capturing the meta-data definition comprises capturing a messaging type between node types.

5. The method of claim 1 wherein generating the code per node type for the plurality of node types in the code generation module comprises transaction aware code that enables the application to participate in two phase commit transactions.

6. The method of claim 1 comprising capturing a definition of peer-to-group messaging including network type and protocol preference.

7. The method of claim 1 wherein capturing the meta-data definition comprises describing an Application Object Model and describing it through an Object Model Repository.

8. The method of claim 1 wherein capturing the meta-data definition comprises capturing an object model of the application and capturing meta-data for the object model.

9. The method of claim 1 wherein capturing the meta-data definition comprises capturing whether the application is persistable.

10. The method of claim 1 wherein capturing the meta-data definition comprises capturing whether the application is location-aware.

11. The method of claim 1 wherein capturing the meta-data definition comprises capturing whether the application is mobile.

12. A system comprising at least one processor programmed to execute:

an application object model definition module that provides an interface to receive inputs from a user that define an object model for an application;

a code generator module that generates application code for an object model of the application; and

an application node connectivity module that allows the user to define peer-to-peer messaging including network type and protocol preference;

wherein the code generation module is configured to generate application code that enables the application to communicate peer-to-peer in accordance with the captured network type and protocol preference.

13. The system of claim 12 wherein the application node connectivity module allows the user to define node types to participate in the application, wherein the code generator module generates application code for the object model for each of the node types.

14. The system of claim 12, wherein the application object model definition module that provides the interface to receive inputs from the user define the object model for the application comprising whether a class of the application is transaction aware and whether the application is persistable.

15. The system of claim 12 comprising one or more class or executable libraries per node type, wherein the code generator module generates the application code for a node type with reference to the respective one of the class or executable libraries.

16. The system of claim 12 wherein the application object model definition module is configured to capture meta-data of an application comprising whether a class of the application is shareable.

17. The system of claim 16 wherein the code generator module generates shareable code that enables a shareable class to be shared to peers and peer-groups.

18. The system of claim 16 wherein the meta-data comprises at least one indicator that indicates whether the application is mobile.

19. A non-transitory computer readable medium comprising instructions, that when read by a processor, perform:

capturing a meta-data definition of an application into an application definition module, the meta-data definition describing at least a plurality of node types, the meta-data definition further comprising whether a class of the application is transaction aware;

compiling a code per node type for the plurality of node types in a code generation module; and

wherein capturing the meta-data definition comprises capturing a definition of peer-to-peer messaging including network type and protocol preference; and

wherein generating the code comprises generating the code that enables the application to communicate peer-to-peer in accordance with the captured network type and protocol preference.

20. The non-transitory computer readable medium of claim 19, wherein capturing the meta-data definition comprises capturing whether a class of the application is shareable.