Stephen wrote: > I hate this subject because I keep changing my mind! Isn't that a good thing?
<snip reason="agree" /> > If you make the assumption that any entry *must* fall into one of the > following three categories, then I think its possible: > > 1. a standard context entry > 2. a registered service type > 3. a custom context type (i.e. declared in meta-data) > > Umm, interesting thing is that this would only require one small > addition to the meta-info model, namely the addition of the version > attribute on a context entry. Legacy A4 support could be provided by > provided my mapping the generic context as the provider to both > serviceable and contextualizable. >From my perspective (being, or trying to be, mainly a component author) it is fairly irrelevant whether it is in the Contextualizable or Serviceable contract, as long as; 1. It is a single lookup. 2. If the container doesn't provide it by default, I can provide an implementation. And your suggestions above seems to fulfill this very well, the rest is implementation details ;o). Cheers Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
