[
http://issues.ops4j.org/browse/QI-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11860#action_11860
]
Rickard Öberg commented on QI-150:
----------------------------------
Current suggestion:
Add @Aggregated annotation on associations (both 1-1 and 1-n) where the
referenced entity/entities are Aggregated.
This should result in:
* When Entity with @Aggregated associations is remove()d, then calculate set of
aggregated Entities from that entity, and remove() them too. Ensure that this
is done through UnitOfWork, so that Lifecycle.remove() is called on aggregated
Entities. Repeat this recursively for remove()d aggregated Entities.
* When an Entity is added to an association, then check if that Entity is
already aggregated by some other entity. If so, then check that the original
aggregating Entity and the new one has the same Aggregate root.
* If the Entity is added to an @Aggregated association, then set the aggregate
of the referenced Entity to that of the Entity for the association.
> Aggregates
> ----------
>
> Key: QI-150
> URL: http://issues.ops4j.org/browse/QI-150
> Project: Qi4j
> Issue Type: New Feature
> Components: API, Core Runtime
> Reporter: Niclas Hedhman
> Assignee: Rickard Öberg
> Fix For: 1.0
>
>
> DDD defines Aggregates as a very central concept, and I think we need to sort
> this out in Qi4j before hitting a 1.0 release.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
