Re: [SUMMARY] Context Concensus
Stephen McConnell <[email protected]>
| Newsgroups | gmane.comp.jakarta.avalon.apps.devel,gmane.comp.jakarta.avalon.devel |
|---|---|
| Message-ID | <[email protected]> |
Nicola Ken Barozzi wrote: > > > Paul Hammant wrote: > >> Darrell. >> >> Non-committers opinions noted. >> >>> Now, nothing stops Phoenix from having a BlockContext implementation >>> that just does: return this; >> >> >> Except that change the usage pattern. >> >>> when asked for that key. And nothing *prevents* a component from >>> directly casting, except that the component is then <i>tightly tied >>> to Phoenix</i> because this is <i>not defined in the Framework</i> >>> contracts. >> >> >> Sorry to be pedantic. No that component is tied to BlockContext >> which is part of Phoenix, but ships in a client api jar. There has >> been discussion before about how trivial to implement for a container >> this is. We even voted it should be the case for Merlin. Nobody made >> the change though. Too much respoect for Stephen, his resistance to >> that resultion, and not enogh sub-project karma. > > > Please show me the thread of that vote and the resolution, I would > like to remember how it went. http://marc.theaimsgroup.com/?t=103036203900001&r=1&w=2 Cheers, Steve. -- Stephen J. McConnell OSM SARL digital products for a global economy mailto:[email protected] http://www.osm.net