Smart props - DONE » History » Revision 2
Revision 1 (Henning Blohm, 07.12.2013 11:41) → Revision 2/14 (Henning Blohm, 07.12.2013 18:12)
h1. Smart Props The goal of this concept is to provide facilities to simplify sharing of component configuration while still being able to query resolved component configuration efficiently and with minimal resource usage. h2. Design Draft What we aim for is an extended _properties_ format that allows declarative inclusion of other component's configuration and the use of some expression language style substitution of vaiables. In other words, we strive for the use of a template processing language. To extend this further, component declarations may indicate their template style via some "Shebang":http://de.wikipedia.org/wiki/Shebang, the default being *java.util.Properties*. For example: <pre> #!com.zfabrik.components/velocityConfig # #!velocity com.zfabrik.component.type=com.zfabrik.java #parse('mymodule/spring_template') java.privateReferences=,\ ${java_private_references},\ somotherref </pre> h2. Configuration Resolution Constraints Resolution of component configuration has certain practical bootstrapping limits due to when it is expected to happen (and what capabilities are available at that time). For example, the velocity engine may not depend on components that use velocity-based configuration formulation. Even more so, a repository that uses velocity-formulated component configurations may not be added to the system before the capability is known. But a repository providing the capability may make use of it.