Thinking more about this, it will be called on each property / collection initialized/updated if those actions are called inside a wrap.
In our case, those "projected entities" are generated from each value set to a property or added to a collection (imagine that the one-to-one, many-to-one or many-to-many relationship has in fact an attached "Relationship" entity where the user can further specify additional properties of that relationship; that's our case). So to be informed through events when a "Relationship" must be created/updated/deleted is just enough and we can maintain it through the @PostsXXX annotations just introduced. Thanks, Oscar El 11/05/2014, a las 21:28, GESCONSULTOR <[email protected]> escribió: > For ach property / collection value I mean. > > I was planning to use his feature to create a complete projection of one > model entities in another domain (with "related" entities) > > Disculpa que sea breve. > Enviado desde mi móvil > >> El 11/05/2014, a las 19:50, Dan Haywood <[email protected]> >> escribió: >> >> Hi Oscar, >> >> OK, so ISIS-550 [1] and ISIS-769 [2] are both committed in master. I've >> marked them as resolved, but please re-open if you encounter any issues. >> >> Cheers >> Dan >> >> [1] https://issues.apache.org/jira/browse/ISIS-550 >> [2] https://issues.apache.org/jira/browse/ISIS-769
