]
Andre Dietisheim commented on JBIDE-7484:
-----------------------------------------
talked to mfojtik on #deltacloud and got the confirmation that instance actions report the
available actions.
We also discussed that the resource state (available actions) is not reliable since 2 or
more clients can modiy them concurrently. We agreed upon that the deltacloud server throws
an 405 if a non-available action is requested.
DeltaCloudClient: remove instance methods (#startInstance,
#stopInstance, etc.) in order to remove code duplication
-------------------------------------------------------------------------------------------------------------------
Key: JBIDE-7484
URL:
https://jira.jboss.org/browse/JBIDE-7484
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
The DeltaCloudClient currently has duplicate implementations of instance related
functionalities (start, stop, destroy, reboot). I'll remove the deprecated methods:
Mail with Jeff Johnson on the 29th of Oct:
>> I discovered another possible duplication:
>>
>> DeltaCloudClient#performInstanceAction allows you to perfom START, STOP,
>> REBOOT, DESTROY (Instance#Action)
>>
>> On the other hand most of these actions also have their own method in
>> DeltaCloudClient:
>>
>> startInstance
>> shutdownInstance (=STOP)
>> rebootInstance
>> destroyInstance
>>
>> Is there any reason for this duplication? Which one would you remove
>> (the performaAction or the individual methods)?
>>
>> Thanks!
>> André
>I would remove the individual methods. Remember that I copied and hacked an ancient
version of this code so some methods that Martin thought
> might be useful were never used. I didn't go about pruning them.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: