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

5. FRAMEWORK EVALUATION 5.2. Operational Validation
Listing 5.9: Apache block in XML
%c%c%c%c%c
%m.start%a.name%m.end
%n
%e%m.equal%e
MIMEMagicFile
/usr/local/apache/conf/magic
%n
%m.start%a.name%m.end
6-8) and comments (line 10). The complete configuration file is in Annex B.3. The file contain-
ing the code generated by the tool for this configuration file is found at http://www-asc.
di.fct.unl.pt/˜jml/SmART/xml.xml.
The tool produced the following XML for the empty block (Listing 5.14), block containing
parameters (Listing 5.15), nested blocks (Listing 5.16) and comments (Listing 5.17):
The Metadata generated by the tool is represented on Listing 5.18.
Then, the file was re-converted to its original syntax. diff showed that the differences be-
tween the original and generated files are some extra new lines in the generated file. This is due
to the original file having a dual criteria for new lines. In some places, an XML tag is followed
by a new line, where in other places they are not.
Still, the tool is able to recognize the whole file, and it produces a file which is completely
functional and well defined.
5.2.4 Parsing the Generated XML
In order to make sure that the XML file generated by the tool was indeed valid, an experiment
was carried: parsing the file generated by the tool. Beforehand, the tool should be able to parse
the generated XML file since it is able to parse files resemblant to XML.
First, OGC (Original to Generic syntax Converter) was called to parse a configuration file.
From this parse resulted the file xml1. Then, OGC was called again to parse xml1 into xml2.
Then, GOC (Generic to Original syntax Converter) was called to print xml2 into xml3, and
finally GOC was called again to print xml3 into the final file. This is depicted in Figure 5.1.
58