[picocontainer-dev] "Tandem charge" refactoring
Konstantin Priblouda <kpriblouda-/[email protected]>
| Newsgroups | gmane.comp.java.picocontainer.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi all,
It is ready to be reviewed. 8 failing unit tests
arise from differences in creation of default
parameters
( trunk version does automatic parameter name lookup,
refactoring does not )
Yet another difference due to subtle change in
by-class
lookup mode.
What has changed:
I tried to clean up relationships between various
components and achieve better separation of concerns -
so there are more specialised "Parameters" with more
logic inside.
Parameters itself are kind of split in 2 sub-entities
( hence "tandem charge" ) "lookup" - performs
lookup of suitable component adapters ( ByKey,
ByClass,
ByKeyClass ) and "extract" - performs extraction of
actual components from component adapter ( scalar
instance, with conversion or collection creation )
Thus component resolution is plugable, and also
extendable without changing core (for what it can be
good)
There is also possibility of aggregation - for example
current default behaviour is achieved by
"see if by key ios resolvable, if not go for by class"
- it would be pipece of cake to add checking for
formal parameter name - see
AbstractInjector.createDefaultParameters )
Comments are welcome,
regards,
----[ Konstantin Pribluda http://www.pribluda.de ]----------------
JTec quality components: http://www.pribluda.de/projects/
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email