You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by "Sam Corbett (JIRA)" <ji...@apache.org> on 2014/10/15 17:35:33 UTC
[jira] [Commented] (BROOKLYN-58) Mechanism for entities to be
automatically imported into the catalog
[ https://issues.apache.org/jira/browse/BROOKLYN-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14172477#comment-14172477 ]
Sam Corbett commented on BROOKLYN-58:
-------------------------------------
One addition to the "Brooklyn can load your catalog.xml file" points above:
* If the file contains an empty classpath element ({{<classpath/>}}) Brooklyn will scan the local classpath.
> Mechanism for entities to be automatically imported into the catalog
> --------------------------------------------------------------------
>
> Key: BROOKLYN-58
> URL: https://issues.apache.org/jira/browse/BROOKLYN-58
> Project: Brooklyn
> Issue Type: Sub-task
> Affects Versions: 0.7.0-M1
> Reporter: Richard Downer
> Fix For: 0.7.0
>
>
> Devise a mechanism that allows catalog entries (including - and preferably - utilising YAML blueprints) to be defined in source code and automatically importing into the catalog.
> Potential mechanisms include the ServiceLoader mechanism, annotation processing, doclets, etc. A runtime mechanism may be preferable as this would also collect catalog entries that the user has added to the dropins directory.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)