Hi Geoff Thanks for your answers. Yes, I was wondering about the use of brooklyn.configs outside of their scope. My problem is that even after reading and studying the examples, knowing that one can simply override an attribute value without brooklyn config, made it unclear for me what exactly the purpose or functionality of brooklyn.config was and how it differed from simple overriding of inherited values. Maybe the documentation could be improved so that brooklyn.config is given an explicit section rather than being an incidental part of several examples and a few comments provided. It would be helpful to understand what its scope is within a catalog item (where can it be declared and used) and what its intended scope is when composing an application where you set values. Btw is there a way to get the runtime ID of an app or an entity and pass it to the VanillaJava app in a system property. Not the "client1" id, but the small uuid that gets generated for those guys.
About not defining run.dir at all, I'm not so sure, without it would mean that my classpath definitions would need to be absolute paths and secondly, the system needs to find its log and config folders when it's launched. So I'd need to add some shell commands to create those and populate the config dir -- but where? When there's no rundir - where exactly is home for the app? I didn't notice another variable that would specify home. But anyway your comments have given me some good ideas and confidence that I'm not far off. I've solved the pid file problem already by having all apps look for the existence of the file regardless of who created it. Once the file is gone, all apps call their shutdown hooks. Many thanks! Peter On Thu, Mar 14, 2019 at 5:18 PM Geoff Macartney <[email protected]> wrote: > Hi again Peter, > > As is often the way, looking at the email I just sent I suddenly realised > what the problem with the pid file is - the catalog item is defining the > run.dir as the home directory. Just leave out the definition of run.dir in > the catalog item’s config. Then each entity gets its own run dir with its > own pid.txt and you don’t need to do anything special to configure the run > dir per-entity. > > I knew something felt wrong! That’s what it was. > > Cheers > Geoff >
