And Hi again,
=:o)

> -----Original Message-----
> From: Peter Donald [mailto:[EMAIL PROTECTED]]
> Sent: Friday, January 11, 2002 11:08 PM
> 
> 
> On Sat, 12 Jan 2002 02:04, Paulo Gaspar wrote:
> > > What would be the difference between an Avalon4 Context and an Avalon5
> > > ComponentManager ?
> >
> > Let me answer you with a question:
> >   What is the difference between an Avalon 4 Context and an Avalon 4
> >   ComponentManager?
> >
> >
> > The only difference between and Avalon 4 ComponentManager and an
> > Avalon 5 ComponentManager is the way you index components - i.e.,
> > the format of the lookup key.
> 
> Well it comes down to what is intended to be pulled out from the manager. 
> A4CM is intended to be used to pull out services while A4Context/A5CM is 
> intended to pull out data relevent to specific 
> environment/context/whatever. 

Nops. I often pull very life components, like DB connections or SQL queries
(we like to put SQL query templates in XML). But I also get strings and 
static lists of records.

 
> In A4CM the string is required to indicate a ROle/interface while in 
> A4Context the key is an object. (In hindsight a free form string may have 
> been better).

I thought so at first but I find it very practical to do things like this:

  IConverter cvt = ctx.get(IConverter.class);

This gets the type conversion "service" from my context. See? I use the 
context as a ServiceManager!
=;o)

I still found no problems with this approach.

 
> A4CM = Service directory + specified key format
> A4Context = Data directory + unspecified object format

Well, at least we agree that a Context is a data directory... although 
it can be a Directory service too.
=:o)


> -- 
> Cheers,
> 
> Pete
> 
> -------------------------
>   All things considered, 
>  insanity may be the only 
>   reasonable alternative.
> -------------------------

Just my thoughts the other day messing up with my framework...


Have fun,
Paulo Gaspar


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to