brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aled Sage (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BROOKLYN-342) defaultDisplayName wrongly inherited by child entities in hierarchy
Date Mon, 29 Aug 2016 19:58:20 GMT

    [ https://issues.apache.org/jira/browse/BROOKLYN-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15446893#comment-15446893
] 

Aled Sage commented on BROOKLYN-342:
------------------------------------

Valentin fixed this issue in https://github.com/apache/brooklyn-server/pull/309. Marking as
resolved.

> defaultDisplayName wrongly inherited by child entities in hierarchy
> -------------------------------------------------------------------
>
>                 Key: BROOKLYN-342
>                 URL: https://issues.apache.org/jira/browse/BROOKLYN-342
>             Project: Brooklyn
>          Issue Type: Bug
>            Reporter: Aled Sage
>             Fix For: 0.10.0
>
>
> In Brooklyn 0.10.0-SNAPSHOT, the {{defaultDisplayName}} was being inherited. This meant
that if it was specified on an app, then that name would be used by all child entities as
well.
> For example, add this to the catalog:
> {noformat}
> brooklyn.catalog:
>   version: 0.0.1
>   items:
>   - id: app-with-default-name
>     itemType: template
>     item:
>       services:
>       - type: org.apache.brooklyn.entity.stock.BasicApplication
>         brooklyn.config:
>           defaultDisplayName: myDefaultName
> {noformat}
> And deploy this app:
> {noformat}
> services:
> - type: app-with-default-name
>   brooklyn.children:
>   - type: org.apache.brooklyn.entity.stock.BasicEntity
> {noformat}
> Both the top-level app and the child BasicEntity would have the name "myDefaultName".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message