brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From geomacy <>
Subject [GitHub] brooklyn-server issue #155: [WIP] Add DSL support for calling effectors in Y...
Date Wed, 22 Jun 2016 17:14:33 GMT
Github user geomacy commented on the issue:
    I have pulled this and was doing some tests around it.  I noticed that given the test
    - type: org.apache.brooklyn.core.test.entity.TestEntity
      id: entity1
        test.confName: $brooklyn:component("entity1").effector("myEffector")
    and a test that does a getConfig, which should evaluate the DSL and invoke the effector:
    the expectation is that the call history on the test entity should contain one call to
“myEffector”.  In fact it contains two, because the config item is evaluated during  validation
in construction of the entity, in a task kicked of from stack trace
    "main@1" prio=5 tid=0x1 nid=NA runnable
      java.lang.Thread.State: RUNNABLE
    at org.apache.brooklyn.util.core.task.ValueResolver.getMaybeInternal(
    at org.apache.brooklyn.util.core.task.ValueResolver.getMaybe(
    at org.apache.brooklyn.util.core.task.ValueResolver.get(
    at org.apache.brooklyn.core.objs.AbstractConfigurationSupportInternal.getNonBlocking(
    at org.apache.brooklyn.core.config.ConfigConstraints.validateAll(
    at org.apache.brooklyn.core.config.ConfigConstraints.getViolations(
    at org.apache.brooklyn.core.config.ConfigConstraints.assertValid(
    at org.apache.brooklyn.core.objs.proxy.InternalEntityFactory.validateDescendantConfig(
    at org.apache.brooklyn.core.objs.proxy.InternalEntityFactory.initEntityAndDescendants(
    at org.apache.brooklyn.core.objs.proxy.InternalEntityFactory.createEntity(
    at org.apache.brooklyn.core.mgmt.internal.LocalEntityManager.createEntity(
    I've been looking at updating the ValueResolver to be a bit smarter about this but need
to do a bit more testing on it before doing a 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 or file a JIRA ticket
with INFRA.

View raw message