Github user aledsage commented on the issue:

    https://github.com/apache/brooklyn-server/pull/279
  
    See https://issues.apache.org/jira/browse/BROOKLYN-349 for a description of 
the underlying problem.
    
    Also see https://github.com/apache/brooklyn-server/pull/341 for an 
alternative fix and a test for that fix. In PR #341 the resolution is deferred 
until the value is actually requested. This was a bit more fiddly to implement, 
but more because it highlighted a problem where the `DslComponent`'s task lost 
the context of the entity that called it.
    
    We'll only want one of this PR or #341 to be merged, I think. @grkvlt 
@ahgittin @neykov I'm keen to hear your thoughts on it.


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to