Ignore:
Timestamp:
03/08/12 09:21:51 (13 years ago)
Author:
sherbold
Message:
  • JFC pre-processors (commands preprocessDirJFC, preprocessJFC) now generate UTF-8 XML files instead of UTF-16.
  • de.ugoe.cs.eventbench.jfc.JFCLogParser adapted to read UTF-8 XML files instead of UTF-16.
  • parseDirJFC and parseJFC commands now both pre-compute all JFC event target equalities and furthermore compare all loaded events to a dummy event before the precomputation to make sure the events are known by de.ugoe.cs.eventbench.jfc.data.JFCTargetComparator.
File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/EventBenchConsole/src/de/ugoe/cs/eventbench/jfc/commands/CMDpreprocessJFC.java

    r309 r392  
    1717/** 
    1818 * <p> 
    19  * Command to pre-process files written by EventBench's JFCMonitor. The only task 
    20  * of the pre-processing is checking if the session was closed properly, i.e., 
    21  * if the XML file ends with a {@code </sessions>} tag. If this is not the case, 
    22  * the tag will be appended to the file. 
     19 * Command to pre-process files written by EventBench's JFCMonitor. The only 
     20 * task of the pre-processing is checking if the session was closed properly, 
     21 * i.e., if the XML file ends with a {@code </sessions>} tag. If this is not the 
     22 * case, the tag will be appended to the file. 
    2323 * </p> 
    2424 *  
     
    7070                try { 
    7171                        FileOutputStream fos = new FileOutputStream(target); 
    72                         writer = new OutputStreamWriter(fos, "UTF-16"); 
     72                        writer = new OutputStreamWriter(fos, "UTF-8"); 
    7373                } catch (IOException e) { 
    7474                        Console.printerrln(e.getMessage()); 
Note: See TracChangeset for help on using the changeset viewer.