> -----Original Message----- > From: Samuel Ferrer [mailto:[EMAIL PROTECTED] > Sent: 24 November 2004 15:23 > To: [EMAIL PROTECTED] > Subject: Re: context > > > Thank you very much ... > > I wander ... that mapping is a very simple class like a Hashtable isn't > ... no need for anything else?
The actual implementation backing the context object is a lot more than a map. In effect it is a map of content entry models. Each model knows how to resolve a request for the entry it represents. For example some content models are simply looking-up to standard content values while others represent complex constructed values that are bound to specific semantic rules declared within a component directive (e.g. volatile entries, constructed values, etc.). > How does the container publish the properties ... via a documentation > obtained some how ... ex like is done in web services? The principal is that the component declares what it requires. Based on this information (key, type, .. ) the container is responsible for resolving the requirements (or possibly choosing another component). Cheers, Steve. > > Regards > Sam > > >From: J Aaron Farr <[EMAIL PROTECTED]> > >Reply-To: "Avalon framework users" <[EMAIL PROTECTED]> > >To: Avalon framework users <[EMAIL PROTECTED]> > >Subject: Re: context > >Date: Wed, 24 Nov 2004 08:58:43 -0500 > > > >Samuel Ferrer wrote: > > > >>I think, and guys correct me if I am wrong, the context is the container > >>in which a component is running. > > > >One of the original Avalon Framework lifecyles was "Contextualize" [1]. > >During this phase, the component would be passed a "Context" object > >(org.apache.avalon.framework.context.Context) by the container. The > >context object would contain a map of values that would help the > component > >know about the container environment such a container home directory. > You > >can think of the Avalon context as similar to a ServletContext for > >servlets, only an Avalon context is read only. Only the container can > set > >the context values. > > > >However, part of the trouble with the Contextualize lifecycle was that > the > >framework did not specify any standard context values. As such, each > >Avalon container had a different set of similar context values [2]. > > > >So, in the end, you're about right when you say "the context is the > >container in which a component is running" but it might be better to say, > >"the context is a map of information about the container environment in > >which the component is running." > > > >Also, if you're just getting into Avalon, please be aware the project is > >splitting. You might also be interested in looking at the documentation > at > >Apache Excalibur (http://excalibur.apache.org) or Codehaus Loom > >(http://loom.codehaus.org) in addition to that over at DPML. > > > >jaaron > > > >[1] http://avalon.apache.org/framework/principals/lifecycle.html > >[2] http://wiki.apache.org/avalon/AvalonContextSurvey > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > _________________________________________________________________ > Express yourself instantly with MSN Messenger! Download today it's FREE! > http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
