Method for building component-software for execution in a standards-compliant programming environment
First Claim
1. A Method for processing an XML-based programming language and executing an application built from multiple executable components written in that XML- based programming language, wherein for sustaining the execution at run-time, requiring a programming platform supporting at least the following standard specifications:
- a) the standard ECMAScript Language Specification as a means of executing instructions and providing volatile memory space;
b) the standard DOM Level 2 Traversal and Range Specification and the DOM Level 2 Core Specification as a means of programmatically accessing and manipulating parsed XML resources; and
c) the standard XSL Transformations as a means for transforming XML resources;
said processing comprises in run-time the following steps;
pre-storing in one or more repositories said multiple executable components of the application;
loading and initializing a set of runtime system libraries from said one or more repositories, including the loading of environment description and resources for said application, and framing the application;
upon necessity by the execution path of said running application, dynamically loading one or more of said pre-stored executable components from said one or more repositories;
transforming each of said loaded executable components from said XML-based programming language into multiple literals of the ECMAScript programming language by applying dedicated transformation rules;
binding and loading each of said transformed components'"'"' literals into an ECMAScript engine in order to make said components and said runtime system libraries programmatically available one to another;
monitoring the execution of each component in order to detect potential defects, potential performance bottlenecks, and said necessity to load additional components;
wherein said XML-based programming language is at least capable of describing the following main entities;
a package that contains the package name, version, debug flag, programming platform compatibility rules and package dependency rules of a predetermined and fixed set of entities and their resources;
a class that contains the class name, version, inherited class and supported interfaces of a predetermined and fixed set of field definitions and operation implementations;
an interface that contains the interface name, version, inherited interface, and a predetermined and fixed set of constant and operation definitions;
an environment that contains the environment name, version, startup class, startup parameters, debug flag and site root of said application, and a startup function.
0 Assignments
0 Petitions
Accused Products
Abstract
Richer programming platforms mean easier application development. In order to achieve richer programming platforms, cooperation between lots of developers is necessary. The optimal situation is when developers can freely use each other'"'"'s software components, without central management. Traditional programming platforms (COM, XP-COM, Java2 and .NET) almost reached this point, excluding situations when components compatible with different programming platforms must be integrated into the same application. An additional problem of the traditional programming platforms is their dependency on some non-standard runtime support. In a Web-application scenario, it cannot be assumed that support for every traditional programming platform would be available on any client machine. Therefore, the need for a system and a method for building, deploying and running component-software in a standards-compliant programming environment.
139 Citations
18 Claims
-
1. A Method for processing an XML-based programming language and executing an application built from multiple executable components written in that XML- based programming language, wherein for sustaining the execution at run-time, requiring a programming platform supporting at least the following standard specifications:
-
a) the standard ECMAScript Language Specification as a means of executing instructions and providing volatile memory space; b) the standard DOM Level 2 Traversal and Range Specification and the DOM Level 2 Core Specification as a means of programmatically accessing and manipulating parsed XML resources; and c) the standard XSL Transformations as a means for transforming XML resources;
said processing comprises in run-time the following steps;pre-storing in one or more repositories said multiple executable components of the application; loading and initializing a set of runtime system libraries from said one or more repositories, including the loading of environment description and resources for said application, and framing the application; upon necessity by the execution path of said running application, dynamically loading one or more of said pre-stored executable components from said one or more repositories; transforming each of said loaded executable components from said XML-based programming language into multiple literals of the ECMAScript programming language by applying dedicated transformation rules; binding and loading each of said transformed components'"'"' literals into an ECMAScript engine in order to make said components and said runtime system libraries programmatically available one to another; monitoring the execution of each component in order to detect potential defects, potential performance bottlenecks, and said necessity to load additional components; wherein said XML-based programming language is at least capable of describing the following main entities; a package that contains the package name, version, debug flag, programming platform compatibility rules and package dependency rules of a predetermined and fixed set of entities and their resources; a class that contains the class name, version, inherited class and supported interfaces of a predetermined and fixed set of field definitions and operation implementations; an interface that contains the interface name, version, inherited interface, and a predetermined and fixed set of constant and operation definitions; an environment that contains the environment name, version, startup class, startup parameters, debug flag and site root of said application, and a startup function. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18)
-
Specification