David Leangen <[EMAIL PROTECTED]> wrote:
> However, if properties files aren't powerful enough, then sure, JSON is
> is good.
And unfortunately, it is difficult to model an array using a properties file
(altho I used to get away with it using some dot notation). ;) But looking
at the json example it will probably be better to describe the "resource"
property as an array or collection, like so (warning: this has not been
tested) --
{ "osgiApp: "
{
"manager: " { ... },
[
"resource: " { ... },
"resource: " { ... }
]
}
}
Then you can query the resource property as a JSONArray or List after
converting the JSON object to a bean.
-- rick
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
