> This sounds like a pretty trivial convenience class. In general, we try to > stay away from classes like this (since it is already easy enough to do what > you describe using PropertiesSerializer itself). yes, I agree.
> Also, as you pointed out, Pivot tends to emphasize the use of JSON over > properties files, so the existence of such a class would be inconsistent. I can modify the test code to use JSON, no problem, I'd only wanted to avoid insert some "strange" code here. And I agree that in this way we could also show the Pivot-way to do these things also here ... > I'm not sure how a Locale would apply here. As far as I know, normal > properties files (as opposed to resource bundle properties files) are > locale-independent. For example Struts uses properties in this way (but they have implemented this behavior). But as seen over we can live without this. So now I'll modify the two base test classes here, dropping the OnTomcat version (currently only the Basic for this exist), and put inside the json config file the details for running the test (keeping inside the file also the block to go to a local instance of Tomcat). In this way the problem is that to change the test run will be needed to change the config file and rerun tests, but i think that could be an acceptable solution at the moment, Ok ? Or I have to pass the config file name to use ... Bye
