I wanted that code to be available; but it is not universally clear to me where it fits into the scheme of things; should system properties take priority over ApplicationDefaults or vice-versa ... or should they only be used during development, but not in product? So the class is there and its easy to contribute it to hivemind.SymbolSources (I'll update the Javadoc for the class to show how) but I don't think its appropriate for there to be a contribution for it.
-- Howard M. Lewis Ship Creator, Tapestry: Java Web Components http://jakarta.apache.org/tapestry http://jakarta.apache.org/commons/sandbox/hivemind/ http://javatapestry.blogspot.com > -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Knut Wannheden > Sent: Tuesday, September 30, 2003 6:51 AM > To: [EMAIL PROTECTED] > Subject: [HiveMind] SystemPropertiesSymbolSource > > > Hi, > > I noticed that HiveMind comes with a SymbolSource > configuration implementation for reading system properties. > However, it doesn't seem like HiveMind contributes this to > the SymbolSource configuration point, nor is there a > corresponding service. I think this makes sense, but the > documentation for the SymbolSource configuration should state > what implementations are already contributed by default and > what others are available in HiveMind. > > --knut > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
