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

5. FRAMEWORK EVALUATION 5.2. Operational Validation
#
=
[
]
!
Listing 5.5: MySQL Metadata
The file was re-converted to its original syntax. diff showed that the differences between
the original and generated files resume to a few absent spaces from the first to the second. This
happens since the parser ignores the space characters outside strings. As MySQL ignores the
spaces in configuration files, the file functionality is maintained.
5.2.2 Apache-like Configuration Files
This test consisted on configuring the Apache HTTP server. The Apache configuration file
(Listing 5.6) implements parameters with a single value (line 1), parameters with multiple val-
ues (lines 3-4), blocks (lines 6-8), nested blocks (10-14) and comments (line 16). The complete
configuration file is in Annex B.2. The file containing the code generated by the tool for this con-
figuration file is found at http://www-asc.di.fct.unl.pt/˜jml/SmART/blox.xml.
The tool produced the following XML for the parameter with a single value (Listing 5.7),
parameter with multiple values (Listing 5.8), block (Listing 5.9), nested (Listing 5.10) and com-
ment (Listing 5.11):
The Metadata generated by the tool is represented on Figure 5.12.
The file was re-converted to its original syntax. diff showed that the differences between
the original and generated files are some absent new lines and tabulations. Once again, this is
due to the parser which ignores some new lines and tabulations. However, this does not affect
in any way the functionality of the new file, so the result is valid.
5.2.3 XML-like Configuration Files
This test consisted on configuring the Eclipse workbench. The Eclipse workbench configura-
tion (Listing 5.13) file is originally on XML format and implements empty elements/blocks
(line 1), elements with attributes/blocks containing parameters (line 3-4), nested blocks (lines
56