After the rework of CachingPC (and others) to be more consistent in their design, I'm not sure the move to Inheritance from Composition is warranted now.
Historically we moved from inheritance designs to composition for many bits of pico in order to hide internal implementation more effectively from users ..
Paul Hammant added a comment - 23/Oct/05 06:38 AM After the rework of CachingPC (and others) to be more consistent in their design, I'm not sure the move to Inheritance from Composition is warranted now.
Historically we moved from inheritance designs to composition for many bits of pico in order to hide internal implementation more effectively from users ..
The argumentation is no different as before. If you have registered components with ThreadLocalCA, EJBClientCA, PoolingCA, HotSwappingCA, ... the wrapper changes or breaks theri functionality.
Joerg Schaible added a comment - 24/Oct/05 02:20 AM The argumentation is no different as before. If you have registered components with ThreadLocalCA, EJBClientCA, PoolingCA, HotSwappingCA, ... the wrapper changes or breaks theri functionality.
New Feature
Open
Major
Inheritance over composition for CachingPicoContainer etc (to debate)
Historically we moved from inheritance designs to composition for many bits of pico in order to hide internal implementation more effectively from users ..