System and method for pervasive software platform-based model driven architecture transaction aware application generator
First Claim
Patent Images
1. A method for creating pervasive applications executable by a plurality of node types, the method comprising:
- capturing a meta-data definition of an application into an application definition module, the meta-data definition describing at least the plurality of node types, the meta-data definition further comprising whether a class of the application is transaction aware;
automatically generating the code per node type for the plurality of node types in a code generation module, comprising transaction aware code that enables the application to participate in two phase commit transactions;
compiling the code per node type; and
generating the packaging necessary to deploy the application to the plurality of node types;
wherein capturing the meta-data comprises capturing whether the application is persistable wherein capturing 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.
4 Assignments
0 Petitions
Accused Products
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.
32 Citations
17 Claims
-
1. A method for creating pervasive applications executable by a plurality of node types, the method comprising:
-
capturing a meta-data definition of an application into an application definition module, the meta-data definition describing at least the plurality of node types, the meta-data definition further comprising whether a class of the application is transaction aware; automatically generating the code per node type for the plurality of node types in a code generation module, comprising transaction aware code that enables the application to participate in two phase commit transactions; compiling the code per node type; and generating the packaging necessary to deploy the application to the plurality of node types; wherein capturing the meta-data comprises capturing whether the application is persistable wherein capturing 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. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. A system for generating applications comprising a processor operatively coupled to at least one memory, the 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 comprising whether a class of the application is transaction aware and whether the application is persistable; and a code generator module that generates the application code for an object model of an application defined through the application object model definition module comprising transaction aware code that enables the application to participate in two phase commit transactions and code that creates the application as persistable an application node connectivity module that captures a meta-data definition of an application, wherein capturing meta-data definition comprises capturing a definition of peer-to-peer messaging including network type and protocol preference, and wherein generating the application code comprises generating the application code that enables the application to communicate peer-to-peer in accordance with the captured network type and protocol preference. - View Dependent Claims (11, 12, 13, 14, 15)
-
-
16. A pervasive computing platform comprising:
- a processor and memory;
a device API Abstraction layer configured to operate as an interface between one or more applications operating on a device and an operating platform of the device, the device API abstraction layer comprising a universal set of APIs, the universal set of APIs comprising a transaction API that provides an abstraction of a universal set of transaction engines and defines the application as persistable wherein the transaction API (Application Programming Interface) captures a meta-data definition of an application, wherein capturing meta-data definition comprises capturing a definition of peer-to-peer messaging including network type and protocol preference, and wherein generating the application code comprises generating the application code that enables the application to communicate peer-to-peer in accordance with the captured network type and protocol preference. - View Dependent Claims (17)
- a processor and memory;
Specification