On Tue, 19 Nov 2002 14:48, Stephen McConnell wrote:
> Peter Donald wrote:
> >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.
>
> Pete:
>
> The ability to declare context creation criteria in XML has been
> available for a least 6 months.
And whats this got to do with the price of fish on Sundays?
I don't believe I said anything about this technique. I don't think it is
particularly useful as you are just moving user supplied configuration from
configuration/parameters to context.
--
Cheers,
Peter Donald
*------------------------------------------------------*
| Despite your efforts to be a romantic hero, you will |
| gradually evolve into a postmodern plot device. |
*------------------------------------------------------*
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
