brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sam Corbett <>
Subject Re: Catalogue ID of a vanilla software process
Date Fri, 29 Apr 2016 16:36:58 GMT
A while ago I posted the question below to the incubator mailing list. I
wanted to get an entity to use runtime files from a resource in one of its
libraries but found that Brooklyn was unable to resolve it.

I recently had a chance to discuss the problem in more detail with Svet and
learned the solution.

Here's an example catalogue entry from a test in Brooklyn with the solution
in bold:

  id: vanilla-software-resource-test
  version: 1.0
    - type: org.apache.brooklyn.entity.stock.BasicApplication
      - type: *java:*
          launch.command: true
          checkRunning.command: true
          # Contained in brooklyn-test-osgi-entities.jar.

classpath://org/apache/brooklyn/test/osgi/resources/message.txt: message.txt

  - classpath://brooklyn/osgi/brooklyn-test-osgi-entities.jar

In case the formatting is lost the key point is the "java:" at the front of
the VanillaSoftwareProcess type. Without this Brooklyn is unable to resolve


On 16 November 2015 at 19:21, Sam Corbett <>

> Hi Alex/Svet,
> Per our conversations on IRC today about VanillaSoftwareProcesses
> referencing resources in bundles, I pushed a couple of test cases to
> Each test adds the same blueprint, for a VanillaSoftwareProcess that
> references a resource in a bundle, to its catalogue then makes a deployment
> of that item to localhost. You should find that
> camp/VanillaSoftwareProcessYamlTest passes but
> rest-server/VanillaSoftwareProcessTest fails. (Make sure to rebuild
> utils/rt-osgi.) The former instantiates an assembly template directly (via
> AbstractYamlTest), the latter does the important bits with the rest api.
> Stick a breakpoint in AbstractSoftwareProcessDriver#copyRuntimeResources
> and you'll see that the catalogue item ID of the entity in the camp test is
> vanilla-software-resource-test:1.0 but via the rest test is
> Sam

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message