[
https://issues.apache.org/jira/browse/BROOKLYN-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15532312#comment-15532312
]
Richard Downer commented on BROOKLYN-353:
-----------------------------------------
Francesco,
Another alternative is one I've used successfully on a project - create a new
web app which does the XML->YAML translation and the callback, so it's
effectively a translation layer between Brooklyn and your external apps. Then
it's possible to create a Brooklyn derivation that inserts your webapp into
Brooklyn's own webapp container. That way you have a single process and a
single web server; your app is on the same port but with a different path. And
it can all be done without modifying Brooklyn's code.
The trick is to use your own Main entry class, which overrides some key
Brooklyn classes - then you get the ability to control how BrooklynLauncher is
used, and insert a reference to your own WAR file. I can provide some more
information if you think this is a path you might take.
> 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)
