polygene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Niclas Hedhman <nic...@hedhman.org>
Subject Re: Configuration initialization
Date Sun, 12 Jul 2015 09:53:12 GMT
And to make this more "integrated", I am introducing


since otherwise people will be confused that both a entity and a value
needs to be declared.

(Actually, this speaks even more in favor of proposal to

The assembly will take care of duplicating the declared types as both
entities and values, so there won't be a ConfigurationInstance type, at
least not in 2.1.

Any thoughts?

On Sun, Jul 12, 2015 at 12:04 PM, Niclas Hedhman <niclas@hedhman.org> wrote:

> We all should know that Configuration Composite is an Entity, read from an
> EntityStore and runtime modifiable just like any Entity.
> We also know that if it is not found in the Entity Store, the value is
> read from a properties file, named after the identity of the Service
> Composite the configuration belongs to.
> I am now adding that in addition to Properties files, the file can be read
> via ValueSerialization instead. I am also adding that YAML is a format we
> intend to support (I really like that format for Config data).
> But currently there is no YAML ValueSerialization extension available. If
> someone feels itchy to help out; Creating a ValueSerialization extension
> for YAML, with the help of SnakeYaml or YamlBeans.
> Since the code is virtually the same inside the Configuration, I will rely
> on this will get done sooner or later, and my tests are only covering JSON
> and XML for now.
> Hopefully done today.
> Cheers
> --
> Niclas Hedhman, Software Developer
> http://zest.apache.org - New Energy for Java

Niclas Hedhman, Software Developer
http://zest.apache.org - New Energy for Java

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message