[
https://issues.apache.org/jira/browse/BROOKLYN-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15532311#comment-15532311
]
Francesco Chicchiriccò commented on BROOKLYN-353:
-------------------------------------------------
It is not only matter of transforming an input XML: we need also to notify (by
invoking a remote REST service) when the deployment is finished + implement
other operations.
{quote}
override BrooklynRestApi with your own version adding the new API, placing the
new class in patches folder
{quote}
Do you have any directions to do this? At the moment we are barely cloning your
repository, adding our own classes, building and running.
Is there any way we can make a Maven project which actually *depends* on
Brooklyn, instead? Some sort of WAR overaly, in practice...
{quote}
Brooklyn is in the process of moving to Karaf (OSGi) which makes it easier to
plug in your own REST APIs.
{quote}
Wise move.
Thanks for your support.
> 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ò
>
> At the [CHOReVOLUTION|http://www.chorevolution.eu] project we are using
> Apache 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 Brooklyn
> codebase - which does not look particularly fancy.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
