Alexis Agahi wrote:
On Wednesday 17 September 2003 11:58, Jim Alateras wrote:
Stephen,
Is it possible to set up merlin so that I can use a configuration file
per component. So if I am using 10 blocks I would have 10 conf files,
assuming each block required some form of configuration. I have used
Phoenix to achieve this in the past
you can have one "default" conf per component that can be provided with the component impl class.
see http://avalon.apache.org/sandbox/merlin/starting/tutorial/config/defaults.html
the config of HelloComponent in HelloComponent.xconfig file
Hope this could help
That should solve the problem.
However, I've been thinking about this since Jim posted the initial question and while we have a rather complete configuration management model for "components" - we don't have a similar structure for providing default configurations for composite components.
Warning - the following is rather Merlin specific and addresses things deep inside the internals.
The James application in Merlin is a composite component. It has a block definition and a corresponding example configuration that contains the named target configurations for the underlying components. But .. there is nothing is Merlin today that enables the association of that example configuration as a default relative to james as a component.
I'm thinking about a policy where a default is implied using the following pattern:
<block-base-url>/<block-definition-name>.<type>
E.g.: target/classes/BLOCK-INF/block.xml would break down to a <block-base-url> of "target/classes/BLOCK-INF/". A default block configuration could be derived by looking for a <block-defintion-name>.config and applying this automatically. This would also need to be complemented by an ability to override a default configuration at the <include/> element under the <container/> element to enable declaration of a specific default composite configuration. This would also allow us to package default configurations in .bar files and have these automatically installed into our local repositories.
Cheers, Steve.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
