Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.2-RC1
-
Fix Version/s: 2.3
-
Component/s: PicoContainer (Java)
-
Labels:None
-
Number of attachments :
Description
Takes over from PICO-212
Activity

Field | Original Value | New Value |
---|---|---|
Description |
Takes over from |

Affects Version/s | 1.2-RC1 [ 11979 ] | |
Component/s | PicoContainer (Java) [ 10191 ] |

Fix Version/s | 2.3 [ 14303 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Resolution | Fixed [ 1 ] |
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 ..