Chen
Subject: Re: Invoking an API from an API plugin
I thought about this approach, but all of the commands have private
members/parameters and do not have setters.
Chris
On Jul 15, 2013, at 11:50 PM, Alex Huang alex.hu...@citrix.com
wrote:
Chris,
You should be able to just
Yes, that is unfortunate design. The service interface was not supposed to
do that.
CC Min and Alex to see if they have a quick workaround.
It would also help to know what exactly you are trying to achieve.
On 7/15/13 11:12 PM, SuichII, Christopher chris.su...@netapp.com wrote:
It looks like the
Subject: Re: Invoking an API from an API plugin
Yes, that is unfortunate design. The service interface was not supposed to do
that.
CC Min and Alex to see if they have a quick workaround.
It would also help to know what exactly you are trying to achieve.
On 7/15/13 11:12 PM, SuichII
class. It does not require the handler.
--Alex
-Original Message-
From: Chiradeep Vittal
Sent: Monday, July 15, 2013 7:36 PM
To: dev@cloudstack.apache.org
Cc: Min Chen; Alex Huang
Subject: Re: Invoking an API from an API plugin
Yes, that is unfortunate design. The service
APIs should call the service interface directly and not call other APIs.
On 7/12/13 1:40 AM, SuichII, Christopher chris.su...@netapp.com wrote:
Er, I should have mentioned that it is not as easy as simply invoking one
API command from another since all the CS API commands have private
Er, I should have mentioned that it is not as easy as simply invoking one API
command from another since all the CS API commands have private @paramenter
members. Because of this, I cannot simply instantiate a command, populate it
with the parameters and call execute() on it.
-Chris
On Jul
