Github user ahgittin commented on the issue:
https://github.com/apache/brooklyn-server/pull/671
Mark https://issues.apache.org/jira/browse/BROOKLYN-498 resolved when this
is merged.
@aledsage you've looked more closely at the synch behaviour than anyone
else so I'd value your thoughts. As noted at the Jira issue we could drop the
guarantee about add/remove event notification -- that would make for a simpler
synch model -- but thinking about it having a primary synch object (the
attributes map's values) feels like a good solution. A tidy might be to
introduce a synch object at the `AbstractEntity` level and have everything
synch on it -- aspire never to have nested/multiple synchronization. But that
could be an iteration on top of this PR.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
