Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (nike.apache.org: domain of Chris.Suich@netapp.com
 designates 216.240.18.77 as permitted sender)
From: "SuichII, Christopher" <Chris.Suich@netapp.com>
To: "<dev@cloudstack.apache.org>" <dev@cloudstack.apache.org>
Subject: Re: CloudStack API Development
Thread-Topic: CloudStack API Development
Thread-Index: 
 AQHOcnSGO4htWaAmSEe7Ve2xU0gdCplIjsQAgAAB4gCAAAT6gIAAAoUAgAADi4CAAAMqAIAANSsAgAC7xACAAE87gIAAAj+AgAAXWgCAAHMxgIAAmMcAgADuUoA=
Date: Fri, 28 Jun 2013 18:56:52 +0000
Message-ID: <7DF64A69-5A86-4672-8068-9AD6A2F822AE@netapp.com>
References: 
 <CAEJ3w4UgJG+N-QXo-cvcUo6ohHh0Wg+h53wwh-sQxN52HfmgSg@mail.gmail.com>
 <20130626154308.GB8380@cloud-2.local>
 <CAEJ3w4UAsJU5WYpZMXd+f3p-GMMcPJgqCpoeujUsQBje5=M5HA@mail.gmail.com>
 <CAEJ3w4UyFH6EK05V+ssJftNCouT065d9+m3t9yZ8R37NLoKm_g@mail.gmail.com>
 <622F0CC9-1D70-400D-BC73-CB13F9CF4FAB@gmail.com>
 <CAEJ3w4UZf-j=6v--ngjCX64JCvoSRRfYD6v3tZQ+0RafDM6FQw@mail.gmail.com>
 <CAEJ3w4U4gH36iojaQ5pw2=7G2Ooh5DLDLEEvt-954gQ9wZpwgw@mail.gmail.com>
 <20130627112105.GA16620@cloud-2.local>
 <CAEJ3w4XFtiTZBXuZr+VQSdmzj+9wkrxv3ZZk1gTQ+0=JXOH5Xw@mail.gmail.com>
 <C495D7E4-A468-4E4E-8502-E3041125B74B@netapp.com>
 <20130628044346.GB1643@cloud-2.local>
In-Reply-To: <20130628044346.GB1643@cloud-2.local>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <1DAEAC2AA388FE48B1D9D3F4EA3547C3@hq.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

So a little update on the hot-deployable API front:

It works=85I 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 commands.properties
-Drop my jar and dependency jars into /WEB-INF/lib/

So, to anyone curious, the plugins look more firefox-y than we though. =3D)

If anyone sees a potential problem with this please let me know. I'll updat=
e the list if I come across anything else interesting in my investigation.

-Chris

On Jun 28, 2013, at 12:43 AM, Prasanna Santhanam <tsp@apache.org> wrote:

> On Thu, Jun 27, 2013 at 07:36:58PM +0000, SuichII, Christopher wrote:
>> I've got some questions related to this topic?
>>=20
>> 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?
>>=20
>> 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.
>>=20
>=20
> It could work, but not without a recompile. Plugins here aren't quite
> firefox plugins (yet) :)
>=20
> --=20
> Prasanna.,
>=20
> ------------------------
> Powered by BigRock.com
>=20