Peter Donald wrote:
Hello Peter.On Tue, 19 Nov 2002 14:48, Stephen McConnell wrote:And whats this got to do with the price of fish on Sundays?Peter Donald wrote:Pete:On Tue, 19 Nov 2002 13:47, Adam Rossi wrote:what was the typical avalon way of initializing component runtime values? The lazy way, or the context method that you described, or something different?The context was the way Avalon was designed to provide the component with runtime values. However some people would "blend" the runtime values in with the configuration/parameters objects. Think of it in a similar way to how ant operates. Consider an input xml fragment <config> <param key="name" value="some name"/> <param key="time" value="${now}"/> </config> What people would do is expand the ${now} variable into the "now" runtime variable. So the component would end up being passed <config> <param key="name" value="some name"/> <param key="time" value="14:03 Oct 20th 2002"/> </config> as part of configuration. This is one thing that a lot of people have requested we add in and there is current work underway to enable just that but until such infrstructure gets into place I would recomend you use the Context for runtime values.
The ability to declare context creation criteria in XML has been
available for a least 6 months.
You mentioned interest that people have expressed in the ability to expand runtime variable and expression of parameters in XML. Both these points are addressed in the context management capabilities I referenced in my reply. Your reply implied that solutions to these requirements were not available. I thought it would be of interest to you and others to know that these capabilities have been around for quite a while now, are operation, validated, and available. That seems appropriate given that this thread is touching on the managemnt of context.
I don't believe I said anything about this technique.
Which is why I responded. :-)
I don't think it is particularly useful as you are just moving user supplied configuration from configuration/parameters to context.Information supplied under a configuration is basically a hierachical structured graph of elements holding named String value in attributes. This is very different to context where the information supplied is a set of keyed Object instances. Context directives provide a mechanism within which you can declare requests for object creation and import context values from a container. This is not moving configuration information to context - this is about structured context management (a seperate concern).
Hope that helps.
Cheers, Steve.
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:[EMAIL PROTECTED]
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
