Emilian>The reason being that I expect getPropDefault to already return a valid value or *my* default which I also know it's valid.
+1 Emilian>A solution would be to validate the whole configuration file at start up. There always might be "runtime validations", so we can't rely on "validate everything at startup time". JMeter has lots of features and lots of options. Should it warn user if some unused feature is misconfigured? Alternative (additional) option is to define properties via some class-interface like entities. That is tie validator to the property, and not to the call site. Note: "string -> whatever" conversion might need to use original string value in order to make error message clear. Do you think error messages should be localizable? Do you think error messages should refer to the relevant documentation sections and/or provide corrective actions? PS. Here's a relevant quote: https://twitter.com/mezzoblue/status/878336246996647938 Vladimir
