Farr, Aaron wrote:
-----Original Message----- From: Stephen McConnell [mailto:[EMAIL PROTECTED]
And now for the contradiction - I don't think we should do this. As I described to Vinay - I think we should hold off until we get more experience with the basic meta-info model.
Thoughts?
I agree about holding off for right now.
<snip/>
So unless there's an easy way to edit or override meta-info (perhaps JMX?)
then I'm currently of the opinion that some of it should be left in
configuration files. If anyone has some better ideas on this, I'd love to
hear them.
Just a note - meta-info is immutable. What is actually happening inside Merlin is that a deployment model is constructed based on meta-info descriptors in accordance with meta-data directives. The configuration info that Merlin provides at the type (meta-info) level is pure immutable default-configuration values. When you override a component configuration your actually overriding the model definition of a configuration which was constructed using defaults + directives. If you write out the type at any time you get the original type – no modification.
As far as JMX is concerned - that's all about model manipulation (which is a much more interesting subject).
Cheers, Steve.
jaaron
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
Sent via James running under Merlin as an NT service. http://avalon.apache.org/sandbox/merlin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
