|
[
Permalink
| « Hide
]
Max Rydahl Andersen added a comment - 14/Nov/05 02:16 AM
definitly not minor and you should be able to do this with a paramaterzied compositeusertype
Just to echo Vjeran, component inheritance similar to entity inheritance would be good, though the one I'm particularly interested in is 'Table per class hierarchy' with a discriminator column. This issue should get a higher priority as it's essential for good model design with proper distinction between Entity and Value Object.
It's definitely not minor. In the absence of this feature changes have to be made to the domain model to workaround the problem.
I think it would be very easy to implement it at least for the "table per class hierarchy" strategy. Others don't necessarily have to be supported. I'm trying to implement the Role Object Pattern for domain objects. I would need component inheritance for the role objects. Treating them as entities is not possible, because they appear to be the same object as their core object - they have the same identity. Adding more than 1 role object to the core object results in a NonUniqueObjectException. I have to change back my domain model to the Extension Object Pattern where the extension/role objects are not identical to their core object.
I agree with Ilya. "table per class hierarchy" would suffice initially. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||