RE: [Avalon4:PROPOSAL] Context Consensus (version 2)
"Leo Sutic" <[email protected]>
| Newsgroups | gmane.comp.jakarta.avalon.apps.devel,gmane.comp.jakarta.avalon.devel |
|---|---|
| Message-ID | <001901c2a291$2e1b64a0$0801a8c0@Lagrange> |
> From: Stephen McConnell [mailto:[email protected]] > > In regards to future canonical key names, it is the intent > > that the values placed in the context are runtime values that > > can only be provided by the container. The Context should > > not be used to retrieve configuration values or services > > that can be provided by peer components. > > > > I recognize your concern, but I think it is problamatic. > > I have cases where I'm constructing components that end up in > context. Its does not happen very often That was my intent with the new text - basically saying that "this is what we recommend in general, but as always there are times when you have to do something else." Can you think of a better way of saying it, if you agree with the sentence above? /LS