Hi Paul, On Jul 18, 2012, at 10:07 AM, Paul Merlin wrote:
> Gang, > > I often put Configuration entities in a dedicated module/layer > in order to store them in a distinct EntityStore or simply because > configuration is an important aspect of an application and having > a configuration module/layer make sense to me. > > First, what do you think about that? > I have all config entities in one config module as it is good to see all configurations in one place in JMX console. But I also think that Qi4j is kind of forcing me to do so because of their persistence. > It's actually difficult to write reusable Assemblies that contain > Configuration entities. I ended up using two Assemblers for an > assembly: one for all composites except Configuration entities and > another one with Configuration entities only. > > What would you think about using this "pattern" accross the whole > SDK? This could help the SDK, examples and documentation to be more > consistent. > I see that some assemblers use builder pattern and there is withConfigAssembly(ModuleAssembly) method to handle this. ( i.e. SchedulerAssembler ) > > Like any convention question, it needs feedback. 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 ? Should something like this works ? configModule.transients( Configuration.class).withMixins( MyYamlConfigImpl.class); thanks, Tibor _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
