brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From neykov <>
Subject [GitHub] brooklyn-docs pull request #132: Using Bundle-SymbolicName in Catalog
Date Mon, 12 Dec 2016 16:19:05 GMT
Github user neykov commented on a diff in the pull request:
    --- Diff: guide/ops/catalog/ ---
    @@ -161,6 +167,30 @@ The following optional catalog metadata is supported:
       whenever a bundle is reloaded in a Brooklyn server,
       and if entities have been deployed against that version, their behavior may change
in subtle or potentially incompatible ways.
       To avoid this situation, it is highly recommended to use OSGi version stamps as part
of the URL.
    +- To refer a resource from a JAR file added by brooklyn.libraries 
    +  you should include OSGi Bundle-SymbolicName in the classpath.
    +  Example:
    +~~~ yaml
    +  brooklyn.libraries:
    +  - url: http://some.server.or.other/path/my.jar
    +    name: myJar-BundleSymbolicName
    +    version: 1.0
    +  items:
    +  - classpath://
    +  - id: use-from-my-catalog
    +    version: "1.0.0"
    +    itemType: entity
    +    iconUrl: classpath://myJar-BundleSymbolicName:org/apache/brooklyn/MyEntity/icon.png
    +    item:
    +      type: myJar-BundleSymbolicName:org.apache.brooklyn.MyEntity
    +      brooklyn.config:
    +        some.config: "some value"
    +        templates.install:
    +          classpath://myJar-BundleSymbolicName:org/apache/brooklyn/MyEntity/config.xml:
    --- End diff --
    We should try to fix cases where the prefix is needed. Does the example work without the
prefixes? If not can you file a bug against Brooklyn.

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