Nice to have
If one enters an erroneous TLScript expression in the model-based search, then one receives duplicate, mixed-language error messages (if the application language is German). This is not desirable.
In general, the problem appears for every application language except English. When parsing an invalid TLScript expression, a tl:ParseException is thrown. The ParseException is then handled in ExprFormat#handleParseException and wrapped into a tl:ConfigurationException. ConfigurationException is a tl:I18NException, i.e. it can be internationalized. The tl:ResKey error of the ConfigurationException is parameterized in the resources and is filled with the English language error message of the ParseException.
As a result, the user will see a mixed English and German error message on the interface with German as the application language.
If the TLScript expression is found to be invalid when parsing, this warning is displayed:
Open the model based search and enter in expert mode e.g.
and display the results. The warning message already described above should appear.