Dissertaç ˜ao de Mestrado Mestrado em Engenharia Informática Jo ...

6. INTEGRATION WITH VIRTU 6.5. Summary
grammars with the corresponding parsers and discards the rest. Besides that, the Tentative
Grammar Repository will now interact with the Eclipse Views and the Web Front-
Ends.
SmART User Interface
The User Interface will be integrated in the Presentation Layer with the Eclipse
Views Front-End and the Web Front-End, so as to provide a way for the administrator
to perform the tasks of creating the Publication Files, when new Building Blocks
are added to VIRTU, and building new grammars when parsers capable of recognizing the
configuration files of the Building Blocks do not exist in the database.
6.4.2 SmART Generic to Original syntax Converter
As for Printer and PrinterMain, they will form an autonomous process in the boot sector
of each virtual machine, which transforms a Publication File on a configuration file, if
that Publication File modification flag is set.
6.4.3 Parser Generator
Much like in SmART, the Parser Generator component will be considered as third-party
software, therefore, this component will reside as an external package in the third-party soft-
ware repository. It is accessed solely by the Grammar Compiler.
6.5 Summary
At the time of elaboration of this dissertation, the integration of SmART with VIRTU was only
commencing. This chapter presents the result of project meetings where we analysed ways in
which both tools can be merged, from the point of view of the VIRTU tool. The taken approxi-
mation consists on joining the SmART components with the existing VIRTU ones.
By merging the prototype of a framework on a bigger tool whose development is well un-
der way, the adaptation of some prototype components should be expected. This is the case of
the SmART Parser Repository, which will be tranformed from a simple list of parsers into
a set of relations in the VIRTU Configuration Database. This adaptation is not straight-
forward though, as with most of the available parser generators, the produced parsers will
consist on a set of Java classes. The classes that compose the parser can be stored in the data-
base without any hassle, nevertheless, they cannot be executed from there. Three alternatives
for the execution of the parser classes were identified: to copy the classes locally to a temporary
folder and execute them; to copy the classes to memory and run them from there; to execute
a database method which allows the parser classes to be ran from the database. After the
project meeting, another solution for this problem was identified, which consists on gathering
the parser classes in a .JAR container [Mic09d] and storing the packages in the database. In this
77