[
https://issues.apache.org/jira/browse/BROOKLYN-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15446891#comment-15446891
]
Aled Sage commented on BROOKLYN-342:
------------------------------------
This problem, I believe, was introduced while fixing another problem. The aim
of that fix was to improve the handling of default display name for entities in
the catalog. Previously, if an entity in the catalog did not have an explicit
display name then it got the name from the item’s metadata. This was fine in
simple use-cases, but bad if using sub-types or if entities wanted to declare
their own defaultDisplayName. Now if a default display name is defined in a
catalog item sub-type or in an app blueprint at deploy time, that default
display name will be used.
Relevant changes that introduced the problem are (probably?) in
https://github.com/apache/brooklyn-server/pull/201.
> 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)
