Error messages for incorrect trace file
If the trace does not follow the expected syntax, the generated ParTraP monitor returns an error message
For example, when evaluating a property on the following file (which does not follow the JSON syntax),
we get the following message, which does not clearly refer to the trace file (and moreover which finally provides an evaluation for the monitor.
> Unexpected character (s) at position 0.
> at org.json.simple.parser.Yylex.yylex(Yylex.java:610)
> at org.json.simple.parser.JSONParser.nextToken(JSONParser.java:269)
> at org.json.simple.parser.JSONParser.parse(JSONParser.java:118)
> at org.json.simple.parser.JSONParser.parse(JSONParser.java:92)
> at partrap.util.Convertjsonlist.convert(Convertjsonlist.java:26)
> at ScanetteProperties.PasDeCaisse4.execute_on_tree(PasDeCaisse4.java:183)
> at ScanetteProperties.PasDeCaisse4.main(PasDeCaisse4.java:153)
> 10:35:29.724 [INFO] *********** Evaluating property : 'PasDeCaisse4'**********
> ----- Trace file : 'traceIncorrecte.json' :
> after composite :
> resultspath : C:/Users/ledru/workspaces/EclipsePhotonPartrap/ScanetteProperties/results/ScanetteProperties/PasDeCaisse4/PasDeCaisse4_traceIncorrecte.txt
> 10:35:29.797 [INFO] Final verdict for trace : traceIncorrecte.json is : true
> PasDeCaisse4: absence_of connexion c where c.obj == caisse4;
> The property 'PasDeCaisse4' is executed on trace 'C:/Users/ledru/Documents/ProjetsEnCours/Philae/scanette/traces/traceIncorrecte.json'
> The property 'PasDeCaisse4' is true Scope from 1 to 0 with the environment null
> No event c of type 'connexion' and satisfying the condition 'c.obj == caisse4' is found