brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From neykov <...@git.apache.org>
Subject [GitHub] brooklyn-server issue #520: Limit parallelism of start/stop steps on Softwar...
Date Thu, 19 Jan 2017 12:55:31 GMT
Github user neykov commented on the issue:

    https://github.com/apache/brooklyn-server/pull/520
  
    @sjcorbett It's generalizing `DslDeferredFunctionCall.resolve` to be reused in the newly
added code.
    
    When using DSL the actual value we want to resolve could be wrapped in several layers
of Suppliers. `ValueResolver` will resolve recursively until it hits a non-supplier. That's
not desirable in some situations - we are interested in the intermediate values as well. What
the above method did was to resolve iteratively until it hit a certain condition (the value
is of a specific type or is non-resolvable).
    
    I needed the same behaviour for the latches changes so I abstracted it in the `ValueResolverIterator`.
It will resolve the value one step at a time, returning each step of the iteration or `absent`
if there's a resolve error.
    
    I'll add some of this as a javadoc.


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

Mime
View raw message