Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@brooklyn.apache.org
Date: Thu, 29 Sep 2016 11:10:20 +0000 (UTC)
From: "Svetoslav Neykov (JIRA)" <jira@apache.org>
To: dev@brooklyn.apache.org
Message-ID: <JIRA.13008469.1475138573000.696567.1475147420911@Atlassian.JIRA>
In-Reply-To: <JIRA.13008469.1475138573000@Atlassian.JIRA>
References: <JIRA.13008469.1475138573000@Atlassian.JIRA> <JIRA.13008469.1475138573943@arcas>
Subject: [jira] [Commented] (BROOKLYN-353) Best-practice for adding
 endpoints to the REST interface?
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Thu, 29 Sep 2016 11:10:22 -0000


    [ https://issues.apache.org/jira/browse/BROOKLYN-353?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D15=
532486#comment-15532486 ]=20

Svetoslav Neykov commented on BROOKLYN-353:
-------------------------------------------

> Do you have any directions to do this?
If you can make the war file approach outlined below by [~rdowner] and [~an=
dreaturli] work then you'll be better off going this way. Note that the res=
t resources are not contained in the war file so you can't add to them. Sti=
ll you can create your own servlets which process the request and have acce=
ss to Brooklyn's internals.

Just in case though - to override the BrooklynRestApi file:
  * create a normal java maven project
  * add a dependency on brooklyn-rest-resources
  * create a new java class "org.apache.brooklyn.rest.BrooklynRestApi", cop=
ying & pasting the content of the original one
  * add your classes
  * build the project and put the jar in the patches folder

> Is there any way we can make a Maven project which actually depends on Br=
ooklyn, instead?=20
Yes, the clocker project is a good example of how to do it - https://github=
.com/brooklyncentral/clocker.
The steps are to:
  * create a java project which contains your classes.
  * create a maven project which generates a brooklyn distribution (using a=
ssembly maven plugin) with your changes in (depends on the above one).=20

These two are combined in a single project in https://github.com/brooklynce=
ntral/clocker/tree/master/dist.

The project also has an example of how to generate patches in https://githu=
b.com/brooklyncentral/clocker/tree/master/patches.

Also you can come to our IRC channel #brooklyncentral on Freenode to ask an=
y questions.


> Best-practice for adding endpoints to the REST interface?
> ---------------------------------------------------------
>
>                 Key: BROOKLYN-353
>                 URL: https://issues.apache.org/jira/browse/BROOKLYN-353
>             Project: Brooklyn
>          Issue Type: Question
>    Affects Versions: 0.9.0
>            Reporter: Francesco Chicchiricc=C3=B2
>
> At the [CHOReVOLUTION|http://www.chorevolution.eu] project we are using A=
pache Brooklyn to manage the whole deployment.
> As we need to add some endpoints to the REST interface, is there any best=
 practice around? At the moment we are just adding our classes to the Brook=
lyn codebase - which does not look particularly fancy.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)