Timeline for OOP Design: relationship between entity classes
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 16, 2012 at 15:43 | comment | added | neontapir | In the Composite pattern, you have a container that can act as one of its members. In this case, you have a VersionedCompound that contains a set of Versions, but also acts like a Compound. It's the job of the VersionedCompound class to decide which version's details to return when its Compound methods are called. I think the examples at the link in my answer demonstrate how to implement this. | |
| Nov 16, 2012 at 7:14 | comment | added | beginner_ | Can you elaborate further? I don't see why the Composite pattern applies or how I should implement? As far as I understood a Version would be an implementation of compound too? | |
| Nov 15, 2012 at 18:20 | history | answered | neontapir | CC BY-SA 3.0 |