cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Nalley <>
Subject Re: CloudStack API Development
Date Fri, 28 Jun 2013 19:07:08 GMT
Do you mind writing up the process on the wiki or in a blog post (or both?)


On Fri, Jun 28, 2013 at 2:56 PM, SuichII, Christopher
<> wrote:
> So a little update on the hot-deployable API front:
> It works…I think. I've been able to package my code into a jar deploy it to a pre-comipiled
CloudStack. All I had to do was:
> -Compile the client
> -Add a bean for my PluggableService to applicationContext.xml
> -Add my command permissions to the
> -Drop my jar and dependency jars into /WEB-INF/lib/
> So, to anyone curious, the plugins look more firefox-y than we though. =)
> If anyone sees a potential problem with this please let me know. I'll update the list
if I come across anything else interesting in my investigation.
> -Chris
> On Jun 28, 2013, at 12:43 AM, Prasanna Santhanam <> wrote:
>> On Thu, Jun 27, 2013 at 07:36:58PM +0000, SuichII, Christopher wrote:
>>> I've got some questions related to this topic?
>>> We're planning on developing an API plugin, but not submitting the
>>> source to CloudStack. Rather, we would like to generate a jar file
>>> and deploy that to the CloudStack API plugin directory. Has anyone
>>> done this?
>>> Ian, your blog post and notes were extremely helpful, so thanks for
>>> that! Do you have any idea how to contribute an API without having
>>> to add your plugin as a maven dependency at compile time? It seems
>>> like, in order for us to do this, there needs to be a way to
>>> register an API plugin to an existing CloudStack deployment without
>>> re-compiling.
>> It could work, but not without a recompile. Plugins here aren't quite
>> firefox plugins (yet) :)
>> --
>> Prasanna.,
>> ------------------------
>> Powered by

View raw message