Re: [picocontainer-dev] Jason van Zyl's need for Plexus
Paul Hammant <[email protected]>
| Newsgroups | gmane.comp.java.picocontainer.devel |
|---|---|
| Message-ID | <[email protected]> |
On Nov 19, 2007, at 7:45 AM, peter royal wrote:
> On Nov 19, 2007, at 1:19 AM, Jörg Schaible wrote:
>> Is it really the intend to generate such kind of a "namespace" for
>> the key?
>
> yes
>
>> In that case it would be equivalent to:
>>
>> mpc.addComponent(Apple.class.getName() + ":one"), new AppleImpl(1));
>
> absolutely
actually, its similar to, but not the same....
Type + Annotation-Hint <> TypeName + Annotation-Hint
... to those developers who take pride in being anal ;-)
I'm committed a new version to show that this is not about by-
instance use of PicoContainer, its a bout by-impl
Utter type-safety is what Jason needs for something the size of
Maven, and he's going to be routinely juggling different impls of the
same type during each run.
>
>> ... just like to understand the use case before we're going to add
>> a new handling for special type of keys (apart from Class types).
>
> i don't think there's anything new/special required, it was more of
> an illustration for jason on how it could be done.
>
> (the plexus model is similar to the old Avalon/Excalibur one where
> you depend on either a class type, or a class type + "role hint".
> the latter being what paul's trying to illustrate..)
>
>
Yup, I'm going direct to the DI use of the same concepts, trying to
make a testcase close to Jason's real examples.
Jason, can you link to a component in your Svn that uses binding
annotations already ?
- Paul
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email