Properties files are the simplest thing to understand. If you can get away with using it, that's what I'd do. Otherwise, you're (1) asking for trouble if the format is wrong, (2) requiring more dependencies on libs to parse JSON, and (3) requiring your users to learn yet something else (ok, not difficult, I admit, but still much more complicated than simple properties files).
However, if properties files aren't powerful enough, then sure, JSON is is good. Cheers, Dave On Mon, 2007-05-07 at 07:35 +0200, Gavin Bong (JIRA) wrote: > Soliciting comments about config file for managedService(s) > ----------------------------------------------------------- > > Key: RADMAN-11 > URL: http://issues.ops4j.org/jira/browse/RADMAN-11 > Project: Pax RadMan > Issue Type: Task > Components: BOOTSTRAP > Environment: OSGi > Reporter: Gavin Bong > Assignee: Gavin Bong > Attachments: jsonconfig.JPG > > The persistent store for the configuration properties of "bootstrap" is a > text file. > The format of the file can be as simple as a properties file, XML or > something else. > I propose a JSON file, & a sample is attached. Comments? Should I do the > simplest thing & revert to the ubiquitous java property file ? > _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
