On Tuesday, October 1, 2002, at 10:18 AM, Jason van Zyl wrote: >> .... You could create the layer dynamically at runtime. The >> excalibur-configuration attributes are metadata that the merger uses >> to >> know whether or not to merge those elements from the base and layer, >> or >> or include both. > > If it wouldn't be too much to ask do you think you could give me a > snippet of code?
To create the layer dynamically? I don't have any code to do that, but it is just a standard Configuration object :) For usage of the merger, see: http://cvs.apache.org/viewcvs.cgi/jakarta-avalon-phoenix/src/java/org/ apache/avalon/phoenix/components/configuration/ FileSystemPersistentConfigurationRepository.java?rev=1.10&content- type=text/vnd.viewcvs-markup It is used in the createMergedConfiguration() function. Phoenix uses it in tandem with the ConfigurationSplitter. Given the output of ConfigurationMerger.merge() and the "base" used, it will compute the layer as a Configuration object. -pete -- peter royal -> [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
