Skip to main content
Jump to: navigation, search

Difference between revisions of "VIATRA2/Model based development of AJAX user interfaces"

(The implementation)
(The implementation)
Line 13: Line 13:
 
As the client side of the AJAX application is an interactive web page, its metamodel consists of two parts: the <tt>HTML</tt> metamodel describes the structure of the web page by defining HTML elements and attributes, while the <tt>JavaScript</tt> metamodel defines the variables and script functions of the web page. On the Fig. 1 you can see a part of the HTML metamodel describing the FORM elements.  
 
As the client side of the AJAX application is an interactive web page, its metamodel consists of two parts: the <tt>HTML</tt> metamodel describes the structure of the web page by defining HTML elements and attributes, while the <tt>JavaScript</tt> metamodel defines the variables and script functions of the web page. On the Fig. 1 you can see a part of the HTML metamodel describing the FORM elements.  
  
[[Image:formelements.pdf | frame | center | Fig. 1: part of the HTML metamodel]]
+
[[Image:formelements.png | frame | center | Fig. 1: part of the HTML metamodel]]
  
 
On the server side, an application stub is generated, which provides a communication layer between the user interfaces and the business logic of the application. This stub runs on the Java platform, which means that the server-side of the PSM is a Java application model, described by the <tt>Java</tt> metamodel. This metamodel consists of the elements and the syntactical rules of the language. The Fig. 2 shows its elements representing the structure of a Java application.
 
On the server side, an application stub is generated, which provides a communication layer between the user interfaces and the business logic of the application. This stub runs on the Java platform, which means that the server-side of the PSM is a Java application model, described by the <tt>Java</tt> metamodel. This metamodel consists of the elements and the syntactical rules of the language. The Fig. 2 shows its elements representing the structure of a Java application.

Revision as of 15:31, 30 June 2008

Description of the example

The model-driven development is a new direction in information technology. The Object Management Group (OMG) has a proposal for this idea, called the Model-Driven Architecture (MDA). It suggests that the development of softwares should be done by platform independent models (PIM) which have to be transformed to platform specific models (PSM) and finally, we should generate the code of the application by these platform dependent models.

At the same time, other new trend is that enterprise applications are more and more often designed for web-based user interface because of its wide accessibility. Compared to fat client applications, it presents new challenges like the limited set of widgets and the slow response of server-side event handling. In general, we resolve this problem with the use of JavaScript-based client-side event handling, which is executed in the local browser. Among these solutions, the most popular is AJAX (Asynchronous JavaScript And XML) which communicates with the server via XML-based messages.

In the VIATRA2 framework, we implemented a development technique which provides the automatic code generation of AJAX applications' user interfaces by the use of a platform independent model, which is able to describe native and web-based user interfaces, too. After preparing the platform dependent metamodel of the AJAX environment, we implemented the transformations creating the platform specific models from the platform independent ones. Finally, we also worked out the code generating transformations which iterate through these platform specific models.

The implementation

The user interfaces' platform independent models (UiPIM) are the input models of the development technique. These models can be created by the domain specific editor of the framework (ViatraDSM). In the present case, the platform specific models (PSM) are the instances of the web metamodels, located under the web entity in the model space.

As the client side of the AJAX application is an interactive web page, its metamodel consists of two parts: the HTML metamodel describes the structure of the web page by defining HTML elements and attributes, while the JavaScript metamodel defines the variables and script functions of the web page. On the Fig. 1 you can see a part of the HTML metamodel describing the FORM elements.

Fig. 1: part of the HTML metamodel

On the server side, an application stub is generated, which provides a communication layer between the user interfaces and the business logic of the application. This stub runs on the Java platform, which means that the server-side of the PSM is a Java application model, described by the Java metamodel. This metamodel consists of the elements and the syntactical rules of the language. The Fig. 2 shows its elements representing the structure of a Java application.

File:Javaapp.pdf
Fig. 2: part of the Java metamodel

Following the idea of the model-driven development, the first transformations, called ajaxPSMPages and ajaxPSMApp, iterate through the PIM and create the platform specific ones (i.e. the PSM of the web page and the application stub). The Fig. 3 shows the rule transforming the platform independent selectionList into the select model element, which represents the SELECT tag of the HTML specification.

Fig. 3: ajaxPSMPages: the rule creating the select model element


The code of the HTML pages and the Java application is generated from these platform specific models. A rule of the ajaxCODEPages transformation, which prints the SELECT tag, can be seen on the Fig. 4.

Fig. 4: ajaxCODEPages: the rule printing the SELECT tag

The attached source code

TODO

Back to the top