Hey,
As yet another consequence of getting ready to deploy a Qi4j-app I'm
reviving the PreferencesEntityStore, as I need a place to persistently
store service configurations.
This ES uses the Preferences API to store ConfigurationComposites using
the following rules:
1) All state will be stored under a node directly under root with the
same name as the application. If you need version info in there you'll
have to put that in the application name itself.
2) Under that node each ConfigurationComposite will have a Preferences
node with the name=identity of the service. This will give you incentive
to have "nice names" for the services, as they will show up here.
3) There will be three subnodes for each configuration, as in the JSON
serialization: one for properties, one for associations, and one for
manyassocs.
4) Properties will be serialized using JSON, but as single values rather
than arrays or objects. If you have a property that normalled would be
serialized as "foo=345" only the "345" part will actually be set as a
preference value with "foo" as name.
5) Associations will be set with association name as property name and
reference as value
6) ManyAssociations will be set with association name as property name
and list of associated entities as a comma-separated list.
That's about it. Makes sense?
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
