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

More documents

Recommendations

Info

3. AN APPLICATION RECONFIGURATION FRAMEWORK 3.3. Original to Generic syntax Converter Presentation Layer User Interface Logical Layer Configuration File Parser Storage Layer Parser Repository Grammar Compiler Tentative Grammar Repository Presentation Layer Code Generator Figure 3.2: Components overview Logical Layer Storage Layer Component Description Configuration File Parser The Configuration File Parser recognizes the diversity of configuration files and parses them in order to change their structure to an application-independent one; Code Generator The Code Generator reads the parsed output from the Configuration File Parser and generates the generic syntax of the file; Grammar Compiler The Grammar Compiler is the component which generates new parsers from grammars. Table 3.2: Logic Layer Components Component Description Parser Repository The Parser Repository is a parser database which holds all the functional parsers generated to the date; Tentative Grammar Repository The Tentative Grammar Repository stores the grammars built by the user on the process of creating a new parser for a configuration file language. Table 3.3: Data Layer Components 26
3. AN APPLICATION RECONFIGURATION FRAMEWORK 3.3. Original to Generic syntax Converter Listing 3.1: User Interface proposed interface interface UI { void processFiles(String[] fileNames); void submitGrammar(); byte[] getTentativeGrammar(); void approveParser(); boolean importParser(); void haltSession(); void recoverSession(); } described. The interfaces that every component should implement are also presented, in a Java-like syntax. Enforcing every component to implement an interface not only allows any component to be completely remade without having any effect on other components, it also aids the integration process of SmART with other tools. User Interface The User Interface (UI, Listing 3.1) is the tool’s front-end, through which the user interacts with the tool. It is invoked by the user and receives an array of configuration file locations at boot time, although it only processes one at a time. For each file, UI summons the Configuration File Parser to make an attempt at parsing a configuration file with the parsers in the Parser Repository. Two outcomes are possible: either a parser manages to recognize the totality of a file or none does. The first case is the ideal case, where at least one of the parsers in the Parser Repository manages to fully recognize the configuration file. In this situation, UI displays the representa- tion of the generic syntax, as returned by the Configuration File Parser, to let the user validate the generated structure. At this point, the configuration file in generic syntax is stored in memory, so UI must save it to a file to let file modification take place. The second case, where the configuration file was not completely parsed by any available parser, requires user intervention. If the file could not be totally recognized by any parser, another parser which recognizes this new language must be generated. For this endeavour, UI provides the user with a friendly interface which allows him to define a new grammar that recognizes the configuration file language. The user must also be allowed to build a new grammar from an existing one. This is useful in the case where a parser managed to parse a configuration file almost entirely. In this case, the new parser might be ready just by tuning an existing one, instead of having to build it from scratch. As soon as a grammar is defined, the user triggers its compilation with the Grammar Compiler’s submitGrammar call. Any grammar compilation errors should be displayed to the user. To ease parser generation, the user must have access to the previously tested grammars. This allows for the rollback of changes in grammars in an easy way. To accomplish this, every time the user submits a new grammar, UI sends it to the Tentative Grammar 27
Page 1: Universidade Nova de Lisboa Faculda
Page 5: To my family and friends, who suppo
Page 9: Sumário Entre os sectores de tecno
Page 12 and 13: CONTENTS 3.5 Modifying the Configur
Page 15: List of Figures 2.1 Virtual applian
Page 19 and 20: List of Listings 1.1 Apache configu
Page 21 and 22: 1 Introduction This dissertation pr
Page 23 and 24: 1. INTRODUCTION 1.2. Problem Descri
Page 29: 1. INTRODUCTION 1.5. Document Organ
Page 32 and 33: 2. STATE OF THE ART AND RELATED WOR
Page 41 and 42: 3 An application reconfiguration fr
Page 43 and 44: 3. AN APPLICATION RECONFIGURATION F
Page 45: 3. AN APPLICATION RECONFIGURATION F
Page 55: 3. AN APPLICATION RECONFIGURATION F
Page 58 and 59: 4. AN IMPLEMENTATION 4.2. Parser Ge
Page 60 and 61: 4. AN IMPLEMENTATION 4.4. Data Stru
Page 62 and 63: 4. AN IMPLEMENTATION 4.4. Data Stru
Page 64 and 65: 4. AN IMPLEMENTATION 4.5. Original
Page 66 and 67: 4. AN IMPLEMENTATION 4.6. Generatio
Page 68 and 69: 4. AN IMPLEMENTATION 4.7. Generic t
Page 71 and 72: 5 Framework Evaluation Chapter 3 pr
Page 73 and 74: 5. FRAMEWORK EVALUATION 5.2. Operat
Page 83 and 84: 5. FRAMEWORK EVALUATION 5.3. Perfor
Page 85: 5. FRAMEWORK EVALUATION 5.3. Perfor
Page 88 and 89: 6. INTEGRATION WITH VIRTU 6.2. VIRT
Page 94 and 95: 6. INTEGRATION WITH VIRTU 6.4. SmAR
Page 96 and 97:
6. INTEGRATION WITH VIRTU 6.4. SmAR
Page 98 and 99:
6. INTEGRATION WITH VIRTU 6.5. Summ
Page 100 and 101:
7. CONCLUSION AND FUTURE WORK 7.1.
Page 103 and 104:
A.1 OGC sequence diagram A Appendix
Page 105 and 106:
B.1 MySQL Configuration file # # Th
Page 107 and 108:
B. APPENDIX - EVALUATION B.1. MySQL
Page 109 and 110:
B. APPENDIX - EVALUATION B.2. Apach
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
B. APPENDIX - EVALUATION B.3. Eclip
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
B. APPENDIX - EVALUATION B.4. Perfo
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Bibliography [Ama09] Amazon. Amazon
Page 181:
BIBLIOGRAPHY [Sol09a] Evolve Space
show all

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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?