On Jul 18, 2012, at 4:00 PM, Paul Merlin wrote: >> what I would like to have is custom fallback mechanism for config entities. >> Current one is looking up for<service_id>.properties and I would like to >> have them in one yaml file. >> How can I change this implementation ? > The simplest way I see would be to implement a very small > EntityStore backed by a single yaml file, or easier, a single > json file. It would not be usable as a true EntityStore but > would do the job for Configuration entities. > > Note that .properties files are only used to declare defaults > and that Configuration is meant to be writable by Applications > so for full support you would have to implement a R/W > EntityStore. > > Such EntityStore would use the FileConfiguration library to > locate the used file. > > Could be a handy extension to the SDK (entitystore-jsonfile?). >
I was looking at existing FileEntityStoreService which is JSON format. But it wants it's own configuration ( another config config module ? ). So I thought that recursion needs to be stopped. Now I see it has to be (Yaml)EntityStore. thanks, -Tibor _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
